All docs

Actions

What an automation can do.

Updated . 9 min read.

Action key Config Notes
send_email to, subject, body All values are templated - {{ submission.email }} works.
send_webhook url, headers?, include_submission? JSON POST.
tag_submission tag Adds to submission.tags.
set_submission_status status One of `received
mark_spam - Shorthand for status=spam.
update_field field, value Mutates submission.payload.
http_request method, url, headers?, body? Generic call.
ai_classify - Runs the same AI classifier as submission categorisation.
integration_driver provider, url, config? Invoke a Slack/Discord/Sheets driver without a Webhook row.
crm_add_tag tag Tags the contact the run is about; the tag is created if the workspace has none of that name. Team plan and above.
crm_remove_tag tag Takes a tag off the contact.
crm_set_owner owner? A workspace member's email address; empty clears the owner.
crm_set_stage stage? A lifecycle stage by name or key; empty clears the stage.
crm_create_task title, description?, due_in_days?, assignee? Creates a follow-up task. Not repeated by a retry.
crm_add_to_list list The name of an existing list.
crm_add_note body Adds a plain-text note. Not repeated by a retry.
crm_record_create object, values, save_as? Adds a record of any object, built-in or your own. values maps field keys to values; placeholders work. Not repeated by a retry.
crm_record_update target?, object?, record_id?, filter?, limit?, values, save_as? Changes fields of the record that started the run, a record by id, or up to 200 records a search finds.
crm_record_delete target?, object?, record_id?, filter?, limit? Deletes records. Queued like every delete; the records go to the trash and can be restored.
crm_record_find object, filter?, search?, sort_field?, limit?, mode?, on_empty?, save_as? Looks records up (at most 200) and keeps them for the steps after it.
crm_record_upsert object, match, values, save_as? Changes the record whose unique field match has the value, or adds one. Objects of your own only.
crm_record_link / crm_record_unlink target?, object?, record_id?, relation, related_ids Links or unlinks records through a relation field. Doing it twice changes nothing.
crm_record_add_note target?, object?, record_id?, body Writes a plain-text note on a record. Not repeated by a retry.
crm_record_create_task target?, object?, record_id?, title, description?, due_in_days?, assignee? Creates a task about a record. Not repeated by a retry.
crm_record_set_owner target?, object?, record_id?, field?, owner? Makes a member the owner of records through a member field (owner by default); empty clears it.
signing_create_draft template, recipient_name, recipient_email, title? Prepares a signing request as a draft from the response the run is about. Never sends. Prepared once per response, template and revision.
signing_request_review - Asks a person to review the draft. Tells the member who can send by email, once.
signing_send wait_for_approval_hours? Sends a draft a person approved, and nothing else. Refuses an unapproved draft or one that changed after it was approved. Not repeated by a retry.
signing_remind recipient? Reminds the recipients who are expected to sign now. Recipients who are not eligible are named in the output and skipped. Not repeated by a retry.
signing_void - Voids a request that is still outstanding. A completed request is never touched.
signing_route_completion connection_id Tells a connection of the workspace that a completed request is complete. Not repeated by a retry.

In the builder, the fields that name something that already exists are searchable pickers: the tag, list and stage of the crm_* actions, the workspace member who owns a contact or is assigned a task, the integration provider, the workflow a child-workflow step starts, the contact a crm_* step acts on instead of the one the run is about (found by their whole email address, or the start of their public or external id), and the form, survey, funnel or booking page a workspace trigger is narrowed to. Every lookup stays inside your workspace; a contact or an asset of another workspace is refused on save. Start typing to search your workspace; a picker stores the same name, email address or id the step has always read, so saved automations are unchanged. Where a step accepts a typed value or a {{ placeholder }}, the picker keeps it.

The crm_* actions work on a contact and are available in workspace automations on the Team plan and above. See Automations for contacts.

Record actions

The crm_record_* actions work on the records of your data model, built-in objects (contacts, companies, deals, tasks) and your own. They are available in workspace automations on the Team plan and above, and the plan is checked again each time a step runs.

Who a step acts as. A step runs as the member who built the automation, while they are still in the workspace, and otherwise as the workspace owner. It has exactly that member's permissions: the object's read, change and delete rights, field restrictions and row rules all apply, and a step the member may not perform fails with a message saying so. It is never retried and never skipped silently.

Which records. target is trigger (the record that started the run, the default), id (a record id, which can be a placeholder such as {{ vars.found.first.id }} or {{ loop.item.id }}) or search (the records a filter finds, at most limit, never more than 200). A filter is the same filter tree the records page uses; values in it can hold placeholders.

Placeholders. A run about a record offers its values as {{ trigger.record.<field key> }}, plus trigger.record.id, trigger.record.object and trigger.record.label; fields the owner may not read are left out. A step with save_as keeps its result under that name: {{ vars.<name>.record.id }} after a create, update or upsert, and {{ vars.found.first.name }}, {{ vars.found.count }} and vars.found.records after a find. Walk the list with a "for each" step whose items are vars.found.records; a loop handles at most 200 items by default, as many as a find returns, and a run may repeat its steps at most 400 times in all (a loop of 200 items with two steps uses all of them).

Test run. Testing an automation shows what each record step would do with the sample, reads the real data model (a search is run, fields are checked) and writes nothing.

Loops. A change a step makes announces itself, and an automation that listens to it starts. To keep automations from starting each other for ever, a run is not started when its automation is already in the chain that led to it, or when the chain is already three automations long. The refused start appears in the run history as a skipped run that says why.

Signing

The signing_* actions use the same sending rules as the dashboard, the API and the agent tools: the plan allowance, the sender checks, the send budget and the member permission all apply, and the member the automation acts as needs signing:send (or signing:void, documents:create) to use the matching action. A preview never prepares a request, invites anyone or sends a message.

The default flow is review before sending: signing_create_draft, then signing_request_review, then a person approves the draft in the request (or with POST /signing-requests/{id}/approve), then signing_send. An approval holds only for the version the person looked at. Editing the response afterwards never rewrites a request that exists; a correction is a linked replacement.

signing_route_completion posts the request's id, title, completion time, signer count and source reference to the chosen connection. It never sends the document, a signature or an address. Completion is a notice, not an approval: it never releases a payment, issues a refund or signs off a project, and the message says so. Failures are recorded on the step and the run, and a completed request is never changed by a failed notice.

Templating

String config values can reference submission data, for example {{ submission.email }} in an email recipient or body. Keep templates simple and prefer field names that already exist in the stored payload. If a field may be empty, add a condition step before the action so the run fails intentionally early instead of sending incomplete data.

Failure behavior

A step can also send its failure to a later step instead of ending the run; see sending a failure to another step. Action failures stop the run unless the step has continue_on_failure enabled or an error route. Use that flag only for optional side effects. For example, a Slack notification can often fail without blocking a later tag, but a failed CRM sync should usually remain visible so the run can be replayed after credentials are fixed.

External calls

send_webhook, http_request and integration_driver can each send through a connection of your workspace instead of a typed URL: set connection_id and the address and key are read from the connection when the step runs. A header typed into the step never replaces the connection's own credential. A connection that must be reconnected, was disconnected or was removed stops the step with a message saying so; a refused key asks for a reconnect and repeated server errors count toward the connection's health (and the integration.* triggers).

Use send_webhook when you want Formspring's standard JSON payload. Use http_request when you need a custom method, headers, or body shape. Use integration_driver when the destination is one of the built-in providers and you want the driver to format the payload for that service.

Data mutation

tag_submission, set_submission_status, mark_spam, and update_field change the submission record. Put those after any notification or sync step that depends on the original payload, and keep the run history in mind when you replay a failed run.