When something happens, something happens.
No-code trigger → condition → action rules assign owners, create tasks, and update fields the instant a record is created — no engineering ticket required.
An automation rule pairs a trigger event — a contact, lead, or opportunity being created — with an optional set of conditions and a list of actions. When a matching record is created, every active rule for that trigger runs synchronously in the same transaction: conditions are evaluated against the new record's fields, and if they pass, the rule's actions apply immediately, atomically, before the create even finishes. Build a rule in the guided UI (pick a trigger, an optional field = value condition, and a follow-up task or field update) or reach the same engine through the API for arbitrary conditions and multiple chained actions.
Trigger, condition, action — the whole rule
A rule fires on one of three trigger events — contact.created, lead.created, or opportunity.created — and runs only if its conditions match the new record. No conditions means the rule always applies to that trigger.
- Conditions use the same field/operator/value filter syntax as saved views and campaign segments
- Rules are evaluated in creation order, and can be turned active/inactive without deleting them
- Every rule and its conditions/actions are editable after creation
Actions that do real work, not just notify
A rule's actions actually change the record or spin up follow-up work — they're not just alerts. Multiple actions on one rule apply in sequence, and later actions can act on fields an earlier action just set.
- assign — set the record's owner to a specific user
- assign_round_robin — rotate ownership across a pool of users automatically
- create_task — spin up a follow-up task with a title, due date, priority, and assignee (including "the record's owner")
- set_field — update any field on the record, like moving a stage
Runs the instant the record exists
Automations aren't a scheduled batch job — they run inside the same transaction that creates the contact, lead, or opportunity, so an assigned owner or a created follow-up task is already there the moment anyone looks at the new record.
No-code builder, full power via API
The in-app builder covers the common case fast — pick a trigger, an optional field-equals-value condition, and a task or field-update action. The same rules also accept the full filter and action syntax through the API, so more advanced conditions and multi-action chains are just as reachable.
- Auto-assign every inbound lead to a round-robin pool of reps
- Create a same-day follow-up task whenever a high-value opportunity is created
- Route contacts from a specific source straight into a qualifying stage
Automations — common questions
A contact, lead, or opportunity being created. Each rule picks one of those three trigger events.
No — the guided builder in the app covers trigger, condition, and common actions like creating a task or setting a field. No code and no ticket needed.
Yes — a rule can chain multiple actions (for example, assign an owner and create a follow-up task), and they apply in order on the same record.
Immediately — automations run synchronously inside the same transaction that creates the record, so the effects are already in place by the time anyone views it.
Yes — mark it inactive and it stops running on new records, but its definition and history stay intact for whenever you want to re-enable it.