Automations
An automation (or flow) is a sequence of steps that fires from a trigger — a contact getting a tag, or a scheduled date — and then sends messages, waits and picks paths with no manual work.
Before you start
- You need edit access in the workspace.
- For automations that send messages, have at least one channel connected in Messaging.
How a flow works
Every flow starts from a trigger and runs a list of steps in order. Steps include sending a message, waiting, conditions, branching and actions on the contact. The flow keeps running while there are steps left, and stops when it reaches the end or when an exit trigger is met.
Automation types
Not every automation is born in the Automations area: other parts of the product also create flows and stay in charge of them. In the list, the Type filter splits these groups:
- Normal — automations created and edited in the Automations area itself.
- CRM-managed — created by the automation matrix of a pipeline stage; turn them on or off from the opportunities Kanban (automation mode).
- Funnel-managed — created inside a sales funnel and edited from it. Both the entry triggers and the flow's objective (its exit conditions) are configured on the funnel canvas: entry triggers come from the connections between cards, and the objective comes from the flow card itself. The automation editor shows them for reference only, with a notice and a shortcut to open the funnel.
- Schedule-managed — notifications configured on a schedule event type.
By default the list shows Normal and funnel automations. CRM-managed and schedule-managed ones stay hidden until you pick them in the Type filter — they are edited in the area that created them, and only show up here for reference.
Create with AI
Under Create automation, the modal now opens with a box above the fields: describe what the automation should do, in a sentence, such as:
Below the box there are clickable examples. Clicking one fills in the field so you can adjust it before sending — nothing is sent on the click. With the field already filled, the example is added as a new paragraph, without erasing what you wrote. The field takes up to 2,000 characters, and anything beyond that is cut at the end of the last word that fits.
Unlike the other areas, the description here is optional: Name and Project are still required, and submitting with an empty box creates the empty automation exactly as before. With a description, Clickmax creates the automation and opens the editor with Max already building the trigger and the steps — you watch the flow appear on the canvas.
Max picks the trigger from the available ones and builds the steps in the order you described. If a connected channel is missing for a messaging step, it leaves the step created and tells you what is missing instead of making it up. The automation arrives as a draft: review the steps and activate it yourself.
If the box does not appear, your access to Max may not be enabled.
In this section
- Create your first recovery automation — a guided flow to recover sales or re-engage inactive contacts.
- Which number the automation sends WhatsApp from — reply from the conversation number or pin a fixed one.
- Branch by what the contact wrote — split the flow by the Instagram comment or WhatsApp message.
- Control the pace of a mass send — how many contacts go out per cycle and how long to wait between cycles.
Related
- Messaging — connect the channels an automation sends through.
- Contacts — the tags and segments that act as triggers.
- Send a broadcast — a one-off send, without a flow.
If it didn't work
- The automation did not fire: check the trigger (a tag, a schedule) in Contacts; if the flow never published, see the error codes (Portuguese).
- The messages did not go out: check the channel in Messaging and the Meta limits (Portuguese).
- An error saving or publishing the flow: see the error codes (Portuguese).