Why does an automation show up in my funnel without being linked to it?
Because its trigger uses something that belongs to this funnel. When an automation built in the automations editor fires on Contact Captured or Contact Created in this funnel (or on one of its pages), or on a purchase or subscription event for an offer used in the funnel, the builder shows that automation as a reference — even though it is not linked to any flow node.
Role: any user with access to the funnel in the workspace sees the references. See permissions.
Where references appear
- External automations listening to this card — right below the page card the trigger uses, a dashed block with that title appears, holding one line per automation: the status, the flow name, and a chevron. The active ones sit loose at the top, always in view; the rest go into a collapsed group per status (Drafts, Closed, Scheduled, Templates, Archived) with the count in the header — click the group to open its list.
- Trigger without a specific page — when the automation uses the whole funnel (without pointing to a page), it appears in the block of every page card in the funnel.
- Automations panel — the Editor flows section lists every reference of the funnel in one place, next to the linked automations, with what each one uses from the funnel ("uses this funnel", "uses this page", "uses this offer", "uses this product").
What a reference is — and is not
The reference is only a mirror: the flow keeps living in the automations editor, and the funnel stores no copy of it.
- You cannot edit the flow from the funnel — triggers, steps and connections cannot be changed here. The pencil at the end of the line opens the flow in the automations editor, where it lives; the rest of the line only opens and closes the summary.
- The More actions (⋮) menu offers the two things the funnel can ask for: Detach from this funnel, which removes only the references to this funnel, and Pause automation, which stops the whole flow. See how to remove an editor automation listening to the funnel.
- The automation is never deleted by the funnel: detaching removes the listening from here, pausing stops the flow, and in both cases it keeps existing in the automations editor.
- Each automation shows its status — Active, Draft, or Closed. Drafts and closed automations appear as references even while not running; only archived ones stay out. Because they sit inside the collapsed group for their own status, a card with dozens of references shows only what is live up front, and each group's count tells you how many there are per status without opening it.
- Clicking anywhere on the line expands the summary: the trigger as the first step, the first steps of the sequence (up to 6, plus "+N steps" when there are more), and the executions.
An offer from another card of the same product also counts: if the automation fires on a purchase of another offer of the same product used in the funnel, it appears with the "uses this product" mark.
The way back: from the flow to the funnel
In the automations editor, a trigger filtered by a funnel (for example, "If captured on the funnel") shows a View funnel button on the trigger card. It opens the funnel in the builder — and it works even while the automation is live, when the rest of the card is locked for editing.
When the automation belongs to another area
Some referenced automations were generated by another part of ClickMax — a pipeline's Automations Matrix, Scheduling, a Webinar, or another funnel. In those cases the item shows where it came from (for example, "From the Automations Matrix"). An automation linked to a flow node of this funnel never appears as a reference: it is already on the canvas as a node.