| Trigger | When it fires |
|---|---|
submission.created |
A clean submission lands (post-spam-scan). |
submission.updated |
A submission's payload or tags change. |
submission.tagged |
A tag is added (manual or automated). |
submission.marked_spam |
A submission moves to spam. |
submission.starred |
A user stars a submission. |
manual |
"Run now" or API /run; with an object, also on records (see below). |
schedule.cron |
A schedule in trigger_config (frequency, time, weekday, timezone); with an object and a view, once for each record of the view. |
webhook.failed |
A webhook delivery exhausts retries. |
contact.created, contact.updated |
A contact is created, or a detail of one changes (workspace automations). |
contact.tag_added |
A contact receives a tag it did not have. Team plan and above. |
contact.tag_removed |
A contact loses a tag it had. Team plan and above. |
contact.list_added, contact.list_removed |
A contact is put on, or taken off, a static list. Team plan and above. |
contact.owner_changed |
A contact is assigned, reassigned or loses its owner. Team plan and above. |
contact.stage_changed |
A contact moves to another lifecycle stage. Team plan and above. |
contact.consent_changed |
A contact's marketing consent is granted or withdrawn. Team plan and above. |
task.due |
A follow-up task reaches its due time. Team plan and above. |
deal.created, deal.stage_changed, deal.won, deal.lost |
A deal is created, moves between stages, or closes. Team plan and above. |
company.merged |
Two CRM companies are merged. The run is about the company that stays; {{ trigger.merged_company_id }} is the id of the one folded into it. Team plan and above. |
company.deleted |
A CRM company is deleted. The company is gone when the run starts, so it carries the company's id only ({{ trigger.subject.id }}), never a name or domain, and the run is not cancelled for lacking it. Team plan and above. |
crm_record.created, crm_record.updated, crm_record.restored |
A record of a custom object is created, one of its values changes, or a deleted record comes back. Changes to the custom fields of a contact, company, deal or task announce crm_record.updated too. The event carries the object's key, the record id and the keys of the fields that changed, never their values ({{ trigger.changed }}). Team plan and above. |
crm_record.webhook |
JSON arrives at the automation's own address and creates or updates a record (see below). Team plan and above. |
crm_record.merged |
Two records of a custom object are merged. The run is about the record that stays; {{ trigger.merged_record_id }} is the id of the one folded into it. Team plan and above. |
crm_record.deleted |
A record of a custom object is deleted. The record is gone when the run starts, so it carries the record's id only and the run is not cancelled for lacking it. Team plan and above. |
crm_note.created, crm_note.updated, crm_note.deleted |
A note is added to a record of any object, edited or pinned, or deleted. The event carries the object's key, the record id and the note id, never the text. A deleted note is gone when the run starts, so that run carries its id only. Team plan and above. |
crm_task.created, crm_task.updated, crm_task.completed, crm_task.deleted |
A task is added to a record of any object, changed or reopened, finished, or deleted. The event carries the object's key, the record id and the task id. A deleted task is gone when the run starts. Tasks made on a contact's, company's or deal's own screens announce their own facts, not these. Team plan and above. |
integration.disconnected |
A connection lost its sign-in and needs to be reconnected. Announced at most once a day per connection. |
integration.degraded |
A healthy connection starts failing deliveries. Announced when it becomes degraded, at most once every six hours. |
integration.delivery_failing |
Deliveries through a connection have failed several times in a row (five by default). Announced once a day until one goes through. |
integration.token_expiring |
A connection's sign-in expires within the warning window. Carries days_left and expires_at; announced once per expiry date. |
company.created, company.updated |
A CRM company is created, or its name, domain, size or industry changes. Team plan and above. The run is about the company, so the contact actions (tag, list, stage, owner, note) have no contact to act on and stop with that message; use steps that need no contact. |
account.trial_started |
The workspace starts a trial through checkout. Team plan and above. |
account.trial_ending |
The workspace trial is three days, one day, or the last day from its end. Once per step. Team plan and above. |
account.plan_changed |
The workspace moves to another plan, including starting or ending a paid subscription. Carries from and to. Team plan and above. |
account.member_invited |
Someone is invited to the workspace. Team plan and above. |
account.member_removed |
A member leaves or is removed from the workspace. Team plan and above. |
signing.request_created |
A signing request is prepared as a draft. Plans with electronic signing. |
signing.request_sent |
A signing request is sent to its recipients. |
signing.recipient_verified |
A recipient confirms their email address with the code, the first time. |
signing.recipient_signed |
A recipient signs. Once per recipient. |
signing.request_completed |
Every signature is in and the final files are stored and verified. Once per request. |
signing.request_declined |
A recipient declines, which ends the request. |
signing.request_expired |
A request passes its deadline unsigned. |
signing.request_voided |
A request is voided before it is finished. |
signing.finalization_failed |
The signed files could not be prepared after the retries and a person has to look. |
signing.delivery_failed |
A signing email bounced, was suppressed or drew a complaint. |
The four integration.* triggers come with every plan and are offered to workspace automations and to automations on a form, survey or funnel. A workspace automation hears every connection of the workspace and can be narrowed with the "Only for this form, survey or funnel" pickers; an automation on a form, survey or funnel hears only the connections that asset owns. The events carry ids and plain facts (the provider, the connection id, the error class, a count, an expiry date), never a key, a token or an address. {{ trigger.provider }}, {{ trigger.subject.label }} and {{ trigger.subject.status }} are available to the steps. Payments (order.*) can be narrowed to one form or booking page the same way.
The contact, task and deal triggers belong to workspace automations. Their events carry ids and the facts of the change, never an email address or phone number; the automation reads the person when it runs. See Automations for contacts.
The account triggers belong to workspace automations too and are about the workspace itself. Like the contact triggers they carry ids and plain facts (plan names, a role, the trial reminder step) and never an email address: {{ trigger.subject.email }} is read from the invitation or the former member when the run starts. A run for account.member_invited stops if the invitation is accepted or cancelled before a delayed step runs, because the invitation no longer exists. Each fact starts one run per automation however often it is announced, the plan is checked when the automation is saved and again when the event happens, and the move that takes a workspace off the Team plan is still announced. A trial that starts with signup, before the workspace has any automation, has nothing to start.
The signing triggers belong to workspace automations on plans with electronic signing. Each event is versioned and carries ids and plain facts only: the request, its version, the response and revision it was made from, and for a recipient event the recipient's place in the order. It never carries a signature, the document, an email address or a name; {{ trigger.subject.title }} and the other facts of the request are read when the run starts. A fact starts one run per automation however often it is announced (per recipient for the recipient events). signing.request_completed is announced only after the final files are stored and verified, never when the last signature is merely recorded. Test and sample requests announce nothing. The plan is checked when the automation is saved and again when the event happens.
Triggers on records of the data model
These belong to workspace automations on the Team plan and above, and work for any object of the data model, built in or your own.
One object. Every crm_record.*, crm_note.* and crm_task.* trigger has an "Only for this object" setting (trigger_config.object, the object's key). Leave it empty to hear every object. The run is about the record, so steps read it as {{ trigger.subject.fields.stage }}, with the object key in {{ trigger.object }}.
Only when chosen fields change. On crm_record.updated, "Only when these fields change" (trigger_config.watch_fields, a list of field keys) starts a run only when at least one of them was set, changed or cleared; any other edit to the record starts nothing. Choose the object first. Changes to the built-in fields of contacts, companies and deals have their own triggers, so only their custom fields can be watched here.
By hand, on a record. Give the manual trigger an object and the automation is offered on that object's records: a Run automation button on the record, a Run automation action on the records page for the ticked records (up to 100 at a time), and an entry in the command menu (Cmd+K or Ctrl+K) for the open record or the ticked ones. One run starts per record, as the record's own run, and you can only run it on records you may read.
On a schedule, for each record of a view. Give a schedule.cron trigger an object, a view shared with the workspace and "Most records per run" (100 unless set, at most 500) and it starts one run per record the view's filters match when the schedule fires, instead of one run. The records are read with the permissions of the member who owns the automation. A record beyond the cap waits for the next firing, and a firing handled twice starts each run once.
From outside: crm_record.webhook. The automation gets an address of its own, shown in the builder once it is saved. Send it POST with a JSON object; the body is mapped onto the object's fields (field_map: field key on the left, the place in the body on the right, like contact.email) and the record is created, updated or both:
| Setting | Meaning |
|---|---|
object |
The object whose records are written. |
mode |
upsert (create, or update the record that matches), create, or update (never creates). Contacts, companies, deals and tasks can only be created. |
unique_field |
A unique field of the object; records are matched on it. |
field_map |
Which part of the body fills which field. A part the body lacks leaves the field alone; null clears it. |
address_version |
Raise it to retire the address and get a new one. |
The write is made with the permissions of the member who owns the automation, through the same rules as any other change (required and unique fields, plan limits, history), so it announces crm_record.created or crm_record.updated like a change made in the app. The automation then runs for that record; {{ trigger.body }} is the JSON that was sent and {{ trigger.created }} says whether the record is new. Send an Idempotency-Key header to make a retried delivery start the automation once. Answers: 201 created, 200 updated, 404 for an unknown or retired address, a switched-off automation or no match in update mode, 422 for a body without mapped fields or a value a field rejects, and 429 beyond 120 requests a minute per address. Anyone who has the address can add records, so treat it like a password.
Choosing a trigger
Use submission.created for the most common workflow: a clean row arrives and the team needs to notify someone, tag it, sync it, or classify it. Use the status and tag triggers when the workflow should react to triage work that happens after intake.
Manual triggers are useful for backfills and one-off tests. A manual run can be started from the dashboard or the API, and it creates the same run records as event-driven triggers.
Scheduled triggers use trigger_config.cron. Keep scheduled workflows idempotent because they are not tied to a single respondent action. For example, a scheduled digest should query the current state and send one report, not blindly repeat work for every historical submission.
Debugging triggers
If no run appears, confirm the automation is active, the trigger type matches the event, and the form or survey that emitted the event owns the automation. For quota-limited teams, the dispatcher can skip new runs after the monthly run limit is reached.
