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/reference/automation-triggers.md.
  • English

      • Automation triggers

      A trigger is the event that starts an automation. Clickmax has triggers in two places:

      • Funnels — when you connect nodes on the canvas, the connection reacts to an event on the page or in the journey.
      • Automations (Message Flows) — the flow starts when the chosen event happens.

      This page lists every trigger available in both. The exact label shown in the picker may vary, and not every trigger is available in the interface today.

      Funnel triggers

      Chosen when connecting nodes on the funnel canvas.

      Routing or starting an automation

      Every funnel trigger moves the lead to the next step on the canvas. Only some of them can also start an automation: while setting up a flow's entry triggers, the rest appear disabled, with a note saying they move the lead between steps but do not start automations.

      Move the lead between steps, but do not start automations:

      • Page viewed
      • Page scroll
      • Time on page reached
      • Exit intent
      • Button clicked
      • Link clicked
      • Form submitted
      • Video interaction, Video started, Video paused, Video completed
      • Refund completed
      • Upsell declined, Downsell declined
      • Subscription renewed, Renewal failed
      • Trial converted into a paid subscription
      • Course started, Certificate issued
      • Affiliation requested, Affiliation approved, Affiliation rejected, Affiliate sale

      Among those that do start automations are "Contact captured", the sales and payment triggers, the subscription ones (including "Trial started") and the members area ones. Which of them show up depends on the card's page type: a checkout card offers the sales triggers, a capture card offers "Contact captured". The flow's entry trigger picker is the definitive list — it shows what is available for each funnel card and disables the rest with the reason.

      Behaviour on the page

      • Page viewed
      • Page scrolled
      • Time on page reached
      • Exit intent (tries to close the tab)

      Interaction with elements

      • Button clicked
      • Link clicked
      • Form submitted
      • Contact captured

      Video

      • Video interaction
      • Video started
      • Video paused
      • Video finished

      Sales and payments

      • Checkout viewed
      • Cart abandoned
      • Purchase confirmed
      • Purchase declined
      • Card declined
      • Pix generated
      • Pix expired
      • Boleto generated
      • Boleto expired
      • Refund requested
      • Refund completed
      • Chargeback recorded
      • Upsell accepted
      • Upsell declined
      • Downsell accepted
      • Downsell declined

      These triggers are scoped to the offer of the checkout they come from: "Purchase confirmed" wired to Product A's checkout does not fire when someone buys Product B. The offer comes from the page connected to the card, so the card needs a checkout page with a product set.

      When the card has no offer that can be identified, the trigger applies to any purchase in the account — including sales unrelated to that funnel. While setting up a flow's entry triggers, the panel shows each card's product and offer, and warns in amber when it cannot identify the offer. If you see that warning, set the product on the page card before publishing.

      Subscriptions

      • Subscription created
      • Subscription cancelled
      • Subscription renewed
      • Renewal failed
      • Subscription card updated
      • Trial started
      • Trial expired
      • Trial converted into a paid subscription

      Members area

      • Member accessed the area
      • Course started
      • Lesson completed
      • Module completed
      • Course completed
      • Certificate issued

      Affiliates

      • Affiliation requested
      • Affiliation approved
      • Affiliation rejected
      • Affiliate sale

      Quiz

      A quiz card offers Quiz completed, which takes the lead to the next funnel step when they finish the quiz.

      These three are in gradual rollout and may not show up in your account yet:

      • Lead captured in the quiz — when the lead leaves their details during the quiz
      • Segment by result — one path per quiz result
      • Abandoned after — when the lead abandons the quiz after a step

      Of these, only Lead captured in the quiz starts an automation; the others move the lead between steps inside the funnel. The automation it starts is limited to that quiz: a lead captured in another quiz or on a capture page does not trigger it.

      Contacts, tags and lists

      • Contact created
      • Contact updated
      • Tag applied
      • Tag removed
      • Joined a list
      • Left a list
      • Lead score changed
      • Contact field changed
      • Contact inactive

      Email

      • Email opened
      • Email link clicked
      • Email not opened
      • Unsubscribed
      • Replied to the email

      WhatsApp

      • Message received
      • Keyword received
      • Button clicked

      Instagram

      • Comment received
      • DM received
      • Lead form submitted

      SMS

      • SMS link clicked
      • SMS replied to

      Telegram

      • Message received
      • Command sent

      Call

      • Call answered
      • Call missed

      Manual start

      • Manual start — no event: who enters (a contact, a list, a tag or a segment) is chosen when you run the automation, now or on a scheduled date.

      System

      • Scheduled date and time
      • Delay after an event
      • Lead time before a date
      • Via API/webhook
      • Date-based (e.g. birthday)

      Automation triggers (Flows)

      Chosen in the Configure trigger step of an automation.

      Clickmax events

      Sales and checkout

      • Checkout viewed
      • Cart abandoned
      • Pix generated
      • Pix expired
      • Boleto generated
      • Boleto overdue
      • Card declined
      • Purchase paid
      • Payment attempt
      • Chargeback requested
      • Refund requested

      Subscriptions

      • Subscription created
      • Subscription cancelled
      • Subscription card changed
      • Trial period started
      • Trial period expired

      Card declined fires once per payment attempt in which the card was sent to the charge and refused — including when the refusal comes from the checkout processing itself. A purchase that never reaches the charge (required card missing, product out of stock, pending seller account, missing delivery address) is not a card refusal and does not enter the automation. If the buyer tries again with the same card, that is a new refusal and the automation fires again — keep that in mind when designing the recovery sequence.

      Subscription cancelled fires on any cancellation, no matter who cancelled it: the buyer, you or support, the automatic cancellation for missed payment after the tolerance period, and the cancellation that comes with a refund. A subscription that simply reached the end of its contracted duration (the plan's last charge) is not a cancellation and does not fire this trigger.

      Trial period started fires the moment the subscription enters the free trial, while no charge has been made yet. It is not the same as "Purchase paid": the charge only happens when the trial ends, and that is when "Purchase paid" fires. Use it to welcome the customer, onboard them, or warn them about the end of the trial. Like the other subscription triggers, it is limited to one offer or one product — pick the scope before publishing; the card in the editor shows the photo, name, and price of the chosen offer.

      Contacts

      • Contact created
      • Contact captured
      • Tag applied to the contact
      • Tag removed from the contact
      • Lead captured through a capture link
      • SMS link clicked — the same trigger, only for links sent by SMS.

      Webhooks and tracked links

      • Tracked link clicked — a click on a short link sent by message, from any channel. The drawer lists every use of the link (sends and automations of any channel). For email links that were not shortened, use "Which link? › Any link in the email". See how to start an automation when the contact clicks.

      Opportunities (pipeline)

      • Entered a lane — fires whenever an opportunity comes to be in the chosen stage: created directly in it (via the create-opportunity button, another automation, the API, or a contact import) or moved into it. Reordering cards inside the same stage does not fire it.
      • Exited a lane — fires when an opportunity is moved out of the chosen stage.
      • Opportunity won
      • Opportunity lost
      • Opportunity field changed

      Scheduling

      • Meeting scheduled
      • Meeting rescheduled
      • Meeting confirmed
      • Meeting completed
      • No-show
      • Meeting cancelled
      • Contact did not join the meeting — the host is in the Clickmax Meet room and the contact has not joined 10 minutes after the scheduled time.
      • Meeting report ready — once per Clickmax Meet meeting, with score, band, outcome and weakest stage filters.
      • Meeting outcome pending — the Clickmax Meet meeting ended and nobody recorded the outcome after 1, 2, 4, 8, 24 or 48 hours. See how to start an automation from a Clickmax Meet meeting.

      Members area

      • Member accessed the area
      • Course completed
      • Module completed
      • Lesson completed

      Some page and list triggers appear in the picker as coming soon and are not active yet.

      Messaging channels

      WhatsApp, Instagram and Telegram triggers need an account connected on that channel. Without one, the channel category in the trigger picker shows a notice with a Connect button that opens the channel connection in a new tab. When you return to the automation tab, the channel triggers are already unlocked.

      WhatsApp

      • Message received
      • Template button clicked
      • Reply received
      • Contact gone quiet
      • Service window (24h) opened
      • Window about to expire
      • Window expired
      • WhatsApp link clicked — a click on a link sent in a WhatsApp message.

      Instagram

      • DM received
      • Comment received
      • Live comment received
      • Ad click (click-to-DM)
      • Story reply received
      • Service window opened
      • Window about to expire
      • Window expired
      • Contact gone quiet
      • Instagram link clicked — a click on a link sent in an Instagram direct message.

      Telegram

      • Message received
      • Conversation started
      • Telegram link clicked — a click on a link sent in a Telegram message.

      Voice (IVR)

      • IVR call result

      Email

      • Email link clicked — the recommended trigger for nurture tracks. Fires on the first click of each link; clicks from known bots do not count. In the trigger you pick "Which link?": "Any link in the email" (provider tracking, also catches links that were not shortened; choose the send or send node and, optionally, the link) or "Tracked link" (short link, with the list of where it is used).
      • Email opened — weak signal: only opens identified as human count, so it does not fire for Apple Mail or iCloud users nor for most clients other than Gmail.
      • Email delivered
      • Email failed — a bounce or a spam complaint; you can filter by permanent or temporary bounce. The first failure counts: a temporary bounce that later becomes permanent does not fire again.
      • Contact confirmed subscription — fires when the person clicks Confirm subscription on the page opened from the confirmation email, once per email address. It does not ask for an origin. See how to ask for email subscription confirmation.

      All four require picking where the email came from: a broadcast or the send node of another automation — that is how you build a nurture track, with one automation sending and another reacting. Without that origin, the trigger would react to any email in the account, including the one the automation itself just sent; that is why the automation's own nodes are not listed.

      Conversations

      External platforms

      Fired by events from the platforms connected in Integrations.

      When you restrict one of these triggers to a product, the picker lists products with search by name and shows the product identifier on the platform as secondary text, below the name. That is what tells apart two products with similar or identical names — common in accounts selling for several experts. When the name is still the identifier itself (a product registered by hand, before the platform sends the real name), the secondary text is not shown.

      Hotmart

      • Purchase approved
      • Purchase cancelled
      • Purchase refunded
      • Chargeback
      • Purchase delayed
      • Purchase expired
      • Awaiting payment (Pix or boleto generated and not paid yet)
      • Cart abandoned
      • Subscription cancelled
      • Subscription switched
      • First access to the members area
      • Module completed

      Yampi

      • Order created
      • Order paid
      • Order cancelled
      • Order refunded
      • Payment declined
      • Cart abandoned

      Guru

      • Transaction approved
      • Awaiting payment
      • Under review
      • Rejected
      • Cancelled
      • Refunded
      • Chargeback
      • Blocked
      • Delayed
      • Expired
      • In recovery
      • Boleto printed
      • Test transaction
      • Cart abandoned
      • Subscription active
      • Subscription cancelled
      • Subscription expired
      • Subscription overdue
      • Subscription in trial

      Asaas

      • Payment received
      • Payment confirmed
      • Payment overdue
      • Payment refunded
      • Chargeback requested
      • Card declined
      • Subscription created
      • Subscription deleted
      • Subscription deactivated

      Hubla

      • Purchase approved
      • Refund
      • Payment failed
      • Invoice expired
      • Cart abandoned
      • Subscription created
      • Subscription cancelled

      Kirvano

      • Purchase approved
      • Purchase refused
      • Refund
      • Chargeback
      • Cart abandoned
      • Pix generated
      • Pix expired
      • Boleto generated
      • Boleto expired
      • Subscription created
      • Subscription renewed
      • Subscription cancelled
      • Subscription past due

      TMB

      • Sale approved
      • Sale cancelled
      • Awaiting payment
      • Awaiting signature
      • Documentation started
      • Document attached
      • Proof of address attached
      • Selfie attached
      • Proof of life
      • Instalment selection
      • Checkout token

      Manual start

      • Manual start — no event: you choose who enters — a contact, a list, a tag or a segment — when you run it. The trigger has no settings: publishing only puts the automation live, and each click on Run creates a run, immediate or scheduled for a date and time. See How do I run an automation for a contact, list, tag or segment?.

      The old Bulk send to list, tagged or segment triggers (immediate or scheduled) were converted into Manual start: the source that was on the trigger shows up pre-selected when you Run.

      If it didn't work

      • The trigger does not appear in the picker: it may be marked coming soon, or it may depend on a channel or integration you have not connected yet. See Integrations.
      • The automation does not fire: confirm the trigger is active and that the matching channel or platform is connected. See Questions.
      • Error when saving the automation: see error codes and messages.