Automations

Put your busywork on autopilot. An automation watches for something to happen (a trigger), then runs a series of steps (actions) — like sending an email, tagging a lead, or creating a ticket. You build it visually by connecting blocks, no code needed.

Quick start

1. Go to Automations in the left menu.
2. Click New automation and name it.
3. Choose a trigger (what starts it).
4. Add actions (what happens next).
5. Turn the automation on.

How automations work

Every automation is built from blocks on a visual canvas:

• Trigger — the event that starts the automation. There's exactly one per automation, and it sits at the top.
• Actions — the things that happen, in order, after the trigger.
• Conditions — branch the flow so different leads take different paths.
• Control — pause the flow with delays or wait for something to happen.

You drag blocks from the left sidebar onto the canvas and connect them in the order you want.

Triggers (what starts an automation)

Pick one trigger to start your automation:

Trigger	Fires when…
Form Submitted	Someone submits one of your forms
Ticket Updated	A pipeline ticket is moved or updated
Payment Completed	A payment is successfully processed
Appointment Scheduled	Someone books one of your calendars
Trial Started	A free trial subscription begins
Subscription Renewed	A recurring payment succeeds
Subscription Cancelled	A subscription is cancelled

Many triggers let you narrow them down — for example, only when a specific form is submitted, or a payment for a specific product.

Actions (what happens)

Add one or more actions after your trigger:

Action	What it does
Send Email	Email the lead — using a saved template or a custom message
Add Tag	Add a tag to the lead
Remove Tag	Remove a tag from the lead
Create Ticket	Create a new ticket in a pipeline
Update Ticket	Move a pipeline ticket to a different stage
Send Notification	Notify your team (in-app)
Call Webhook	Send the lead's data to an external service via an HTTP request
Browser Agent	Open a page in an isolated browser and extract or act on it from a written task. Later steps can use {{browser.output}}. Run history shows the step trace and screenshots. Skipped until an admin turns the feature on.

In emails, notifications, and ticket titles you can insert variables like the lead's name ({{lead.firstName}}) so each message is personalized automatically.

Conditions (branching)

Use an If block to send leads down different paths based on their data — for example, one path for leads tagged "VIP" and another for everyone else. You define one or more branches, each with its own conditions, plus a default path for anyone who doesn't match.

Control (timing)

Control blocks manage when the next step runs:

• Wait / Delay — pause for a set amount of time (minutes, hours, or days) before continuing. Great for follow-ups, like "wait 2 days, then send a reminder."
• Wait for Event — pause until something specific happens (for example, an appointment actually starts), with a timeout so the flow continues even if the event never occurs.

Building and turning it on

1. Drag your trigger, actions, conditions, and control blocks onto the canvas.
2. Click any block to configure it in the side panel.
3. Connect the blocks in the order you want them to run.
4. When you're happy, set the automation's status to Active.

An automation only runs while it's active. You can switch it off any time to pause it without losing your work.

Monitoring runs

Every time an automation fires, it creates a run you can inspect:

1. Open an automation.
2. View its run history.
3. Click a run to see each step, in order, and whether it succeeded — including any that are still waiting on a delay.

This makes it easy to confirm your automation is working and to troubleshoot if a step didn't do what you expected.

Organizing automations

If you build a lot of automations, use folders to keep them organized. Create folders, move automations into them, and navigate with the breadcrumb trail. You can also duplicate an automation to reuse it as a starting point.

Tips

• Start simple: one trigger plus one or two actions, then expand.
• Add a delay before follow-up emails so you don't message people instantly.
• Use tags and conditions together to personalize who gets what.
• Check the run history after turning a new automation on to confirm it behaves as expected.
• Test with a real action (like submitting your own form) before relying on it.