A trigger, the conditions that narrow it, and the actions that follow. No code, and you can watch a rule run against real data before you ever switch it on.
Included from Pro upwards
Every event the product raises, grouped by where it happens: Work (a task, a project), Sales (a deal created, a stage changed, a deal won, a client created, a lead turning hot, a tag added), Money (an invoice created, an invoice paid), Capture (a form submitted, a survey completed, an appointment booked) and Documents (signed, declined, expired).
Pick a field from the trigger and the choices are the fields that event actually carries, so you cannot select one that will never be there. Then an operator: is, is not, contains, starts with, is one of, is more than.
Notify owners and admins, notify the lead’s own assigned owner, create a task, set the triggering record’s status, assign it to a teammate, email or text the lead, or enroll them in a drip sequence. Add several and they run in order.
Merge fields like {{first_name}}, {{company_name}} and {{amount}} are filled from the lead the message is going to, at the moment it is sent. A field that cannot be filled does not send a half-written message.
A webhook action POSTs the rule, the event, the entity and the trigger data to any URL you choose, so Zapier, Make, n8n or your own service can pick it up. Private and internal addresses are blocked.
Press Run test and the rule is simulated against your most recent matching event: whether it would fire, which conditions passed or failed, and exactly what each action would have done. Nothing is sent and nothing is changed.
A library covering forms, surveys, documents, tasks, projects, sales, clients and leads. Filter by module, load one into the builder, change it. Save your own as a template.
Each automation keeps its own run history, held against the automation rather than its name, so renaming one no longer loses everything it has done. The dashboard shows webhook calls used against the daily allowance, so a rule that goes quiet is never a mystery.
The part you would otherwise find out in week three. If one of these is central to how you work, raise it before you buy rather than after.
No. Every automation is built by choosing a trigger, optional conditions and actions from lists. The webhook action is the only place a URL is typed, and that is for pushing events out to something else.
Run test simulates it against your most recent matching event and shows which conditions passed, which failed, and what each action would have done. Nothing is sent and no data changes.
Yes, with the webhook action. It POSTs a JSON payload with the rule, the event, the entity and the trigger data. Private and internal addresses are refused, and delivery is capped by a daily allowance shown on the dashboard.
It is recorded in that automation’s own run history with what fired and how many actions ran, and the dashboard shows the limits that would stop one. A rule that stops working is visible rather than silent.
The full product documentation for this module is at /docs#automations.
Free for up to 5 seats, no card required. Every module is in the same workspace, so nothing needs connecting to anything.