For AI agents: the complete documentation index is available at https://docs.clickmax.io/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.io/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.io/en/features/automations/linked-automations-on-canvas.md.
  • English

      • Why is there a dashed card next to a step or the trigger of my automation?

      Because another automation in your workspace is linked to that point of the flow. The dashed card is a mirror of it, so you can see the whole chain without opening automations one by one:

      • Next to a step: another automation that starts when that step runs. For example, an Add tag step with the tag "VIP" shows the card Flow started by this tag for every automation whose trigger is Tag applied filtered by "VIP".
      • Next to the trigger: another automation that feeds yours. If yours starts with Tag applied "VIP", the card Flow that applies this tag appears for every automation with an Add tag "VIP" step.
      • Messages: the Send email step shows the automations that start when that email is opened, clicked, delivered or fails. On the other side, the Email opened trigger shows the automation that sends the email chosen as its origin.

      Role: anyone who can open the automation in the editor sees the cards. See permissions.

      Step in your automationCard next to the stepTrigger of the other automation
      Add tagFlow started by this tagTag applied with the same tag
      Remove tagFlow started when this tag is removedTag removed with the same tag
      Assign opportunity (move to a stage)Flow started when entering this stageOpportunity entered stage with the same stage, or Opportunity moved between stages to the same stage
      Update opportunity card with status WonFlow started when the opportunity is wonOpportunity won with no pipeline or stage filter
      Update opportunity card with status LostFlow started when the opportunity is lostOpportunity lost with no pipeline or stage filter
      Send emailFlow started when this email is clickedEmail link clicked with this step as origin
      Send emailFlow started when this email is openedEmail opened with this step as origin
      Send emailFlow started when this email is deliveredEmail delivered with this step as origin
      Send emailFlow started when this email failsEmail failed with this step as origin
      Send WhatsApp message, Send SMS, Send email, Send Telegram message or Send Instagram DMFlow started when a link in this message is clickedTracked link clicked with this step as origin
      Place a voice callFlow started by the result of this callVoice audio listened (%) with this step as origin
      HTTP request to the Webhook received URL of another automationFlow started by this webhookWebhook received of that automation

      The reverse path works for all of these cases: your trigger shows the automations that have the matching step (Flow that applies this tag, Flow that moves to this stage, Flow that marks as won, Flow that sends this email, Flow that sends this message, Flow that makes this call, Flow that calls this webhook, and so on).

      In message links, the other automation's trigger points to one specific step, not to a tag or stage. So the card only appears when the trigger's origin is an automation's send step. To pick that origin in the tracked link trigger, see How do I know who clicked the link I sent in an automation?.

      One card per automation, up to 3 per step, ordered with live automations first and, within each group, the most recently created first. If the step applies several tags, the cards for all of them stack below the step, to the right, linked by a dashed line. The trigger's cards sit to its left. With more than 3 automations, a N more automations card appears and opens the full list, in the same order; clicking an item in the list does the same as clicking a card. The open automation itself never appears as a card.

      The card reflects what is on the canvas right now: if you just picked the tag or the stage in the step and have not saved yet, the card already appears. Change it and the card changes with it.

      What the card shows

      • A thumbnail of its canvas, the same drawing as the automations list, with its status as a badge in the top-right corner of the thumbnail.
      • The automation's name.
      • Its status: Live, Draft or Paused. Drafts and paused automations appear even though they are not running, so you know they exist. Archived or deleted automations are left out.
      • Its runs: Total, Succeeded and Failed, the same numbers shown in a step's footer. Test runs do not count. When Total is higher than the sum, the difference is runs In progress or Canceled — see Why doesn't a step's General number match Successes plus Failures?.

      What you can and cannot do

      • Clicking the card opens a preview of the other automation in a side panel, without leaving yours. The panel shows its canvas in read-only mode, with the name and status at the top; the Open in editor button takes you there for real, and Esc, the X or a click outside close the panel. Inside an editor opened from the CRM or another area (read-only window), the card only informs and does not open anything.
      • The card is not a step: it cannot be dragged, connected, duplicated or deleted. It follows the step or the trigger when you move them.
      • It does not change the open automation: nothing is saved because of it, and the Organize blocks button ignores dashed cards.

      Card colors

      The color of the border and of the dashed line tells what is on the other end before you read the title: purple is another automation, blue is a pipeline, a schedule, a webinar, a members area or a course; green is a funnel, a page, an offer or a product; and orange is an Instagram post or a broadcast.

      The pipeline card

      When a step or the trigger points to a pipeline, a blue dashed card for the pipeline itself also appears, at the top of the column, before the automation cards:

      WhereCard
      Assign opportunity stepPipeline the card enters
      Remove opportunity stepPipeline the contact leaves, one per chosen pipeline
      Opportunity trigger filtered by a pipeline (for example, "entered the stage")Pipeline that starts this flow, to the left of the trigger

      The card shows the same summary as the Commercial → Pipelines list:

      • A board thumbnail, with one column per stage and up to 5 cards per column.
      • The name, the number of stages and the group, if any.
      • Open (open opportunities), Open value (their summed value) and Conversion (won over won plus lost; "—" when none was closed).
      • The initials of the people working on the pipeline, up to 3 and then +N, and the last activity.

      The Visit button opens the pipeline board. Inside an editor opened from the CRM or another area (read-only window), the button does not appear.

      A pipeline only becomes a card if you can see it in the pipelines list: a deleted pipeline, or one outside what your access shows, is left out. The numbers follow the same access rule as the list.

      The funnel card

      When the trigger is a checkout event filtered by offer (for example Pix generated or Purchase approved for a specific offer), a green dashed card, Funnel that sells this offer, appears to its left for each funnel that sells any of the chosen offers. It comes before the automation cards that feed the trigger.

      The card shows the same summary as the Marketing → Funnels list:

      • A thumbnail of the funnel graph, with its status as a badge in the top-right corner: Published, Draft, Unpublished changes or Disabled.
      • The name, the number of steps and how many of the trigger's offers the funnel sells.

      The Visit button opens the funnel editor. Inside the editor opened from the CRM or another area (read-only window), the button is not shown.

      A funnel sells an offer when it is the main offer or an order bump of a step, or the offer of the page linked to the step. The product filter does not become a card: it matches any offer of the product, including ones created later, so the funnel would be a guess. Deleted funnels and deleted steps are left out.

      The same green card appears when the trigger is a capture trigger (Contact Captured, Capture Form Submitted or New contact) filtered by funnel: the title becomes Funnel that captures these contacts, and instead of the offers the card says the funnel captures the trigger contacts. If the funnel also sells an offer of the same trigger, only one card appears, the offer one. A deleted funnel, or one from the old version of the funnel editor, does not become a card.

      If the capture trigger is also filtered by page, a green Page that captures contacts card appears above the funnel, with the page thumbnail, name and public address. The Open page button opens the live page in a new tab, not the editor; this also works inside the editor opened from the CRM or another area. A deleted page does not become a card.

      The Instagram post card

      When the trigger is Comment on Post or Reel with chosen posts, an orange dashed card appears to its left for each post, at the top of the column: Post that starts this flow or Reel that starts this flow. The card shows:

      • The creative's picture: the post image, or the reel cover.
      • The post caption, up to two lines.
      • The keywords the comment must contain, when the trigger filters by word (Contains, Exact text, Starts with or Keyword). Without that filter, the card says Any comment. Doesn't contain and Regex words are left out, because they are not words the contact types.

      Clicking the card opens the post on Instagram in a new tab, without leaving the editor; this also works inside the editor opened from the CRM or another area.

      Up to 3 posts become cards, in the order they were chosen; with more, the last card says how many selected posts were left out (+N selected posts). A trigger set to All posts does not become a card. A post deleted on Instagram, or from a disconnected account, does not either.

      Schedule, webinar, members area, broadcast and products

      The trigger also gets a card to its left when it is filtered by one of these resources:

      Trigger filtered byCardWhat it showsButton
      Schedule (scheduling triggers, such as Meeting Booked)Schedule that starts this flowthe month calendar, with stronger days where there are more appointments (cancelled ones don't count), the month total, the duration and whether the schedule is publicOpen public schedule opens the booking link in a new tab; a schedule without a public link shows View schedule, which opens the schedule screen
      WebinarWebinar that starts this flowthe cover (with no cover uploaded, the video thumbnail), the name, the next session and, outside drafts, the webinar numbers: Registrants, Leads, Conversion (who attended) and Registrations · 10dOpen room opens the public room in a new tab; View webinar opens the webinar in Clickmax
      Members areaMembers area of this flowthe cover and the nameOpen area opens the live area in a new tab
      Course (completion triggers)Course that starts this flowthe cover and the nameOpen course opens the course in the members area, in a new tab
      Broadcast (Tracked link clicked with a broadcast as origin)Broadcast that sends this linkthe name, the send date and the recipientsView broadcast opens the broadcast
      Offer (checkout triggers)Offer that starts this flowthe thumbnail, the product, the offer and the priceOpen checkout opens the checkout in a new tab
      Product from an external platform (Hotmart, Kiwify and others)Product that starts this flowthe platform, the name and the priceno button: the sale happens on the external platform, and Clickmax does not store its link

      Up to 3 cards per trigger; a deleted resource does not become a card. Buttons that open a public page also work inside the editor opened from the CRM or another area; the ones that open a Clickmax screen are not shown there.

      The WhatsApp triggers Button clicked and Link clicked without a broadcast origin get no origin card: the event only carries the number and the button, not which automation or broadcast sent the message.

      The "Update opportunity card" step on the canvas

      This step is created by the pipeline's automation matrix, not from the editor menu. When you open the automation, the card shows the fields it changes (Status, Value, Priority, Temperature, Loss reason), so you know what it does before looking at the dashed cards linked to it. A step with no field configured appears empty.

      If a card you expected is missing

      • In the other automation, check that the trigger is exactly the one in the table above and that it is filtered by the same tag or stage. A Tag applied trigger with no tag chosen listens to any tag and does not become a card.
      • Won and Lost only link to triggers with no pipeline or stage filter. The Update opportunity card step does not know which pipeline the opportunity is in, so a trigger filtered by a pipeline is not shown, to avoid suggesting a link that may not exist.
      • Opportunity left stage does not appear: moving to a stage does not say which stage the opportunity came from.
      • For email and tracked link triggers, check that the origin is your automation's send step. A trigger whose origin is a broadcast (sent from the Messaging area) listens to that broadcast, not to a step, and does not become a card. An automation started through Run is not a broadcast in this sense: the origin is still its send step.
      • In Voice audio listened (%), the editor offers a broadcast or any call as origin. The card only appears when the trigger points to the Place a voice call step, an origin the editor does not offer yet.
      • For webhooks, the card follows the saved URL of the HTTP request: after changing the URL, save the automation for the card to follow. The URL must hold the full webhook address, copied from the Webhook received trigger; a URL built with a variable does not become a card.
      • WhatsApp triggers (reply received, message received, button clicked, contact silent) do not become cards. They filter only by number, not by a message, and would link to every automation that sends from that number.
      • If the other automation was archived, it also leaves the canvas.