Skip to main content
A trigger is what starts a workflow. Every workflow begins with exactly one trigger, and the data the trigger carries (the submitted form, the webhook body, the meeting, the CRM record) is available to the steps that follow.
Add a trigger when you create or open a workflow in the Workflows app, then build the steps that run after it fires.

​
Form submission

Fires when someone submits a form you track with Default.
  • Connected Form: choose which tracked form starts the workflow. For example, pick your Request a demo form so every submission runs this workflow.
The submitted field values are available to later steps.

​
Incoming webhook

Fires when an external system sends a request to a webhook URL Default gives you.
  • Connected Webhook: choose an existing webhook to start this workflow, or create a new one.
The webhook’s request body is available to later steps.

​
Meeting status

Fires when a meeting changes status. The meeting’s details are available to later steps, including the meeting owner and any other hosts, which you can insert from the data picker and map into owner or recipient fields (for example, a CRM record’s owner or a Slack recipient).
Because each status is a fixed value rather than free text, later steps can branch on it. For example, add a branching step after the trigger to send Held meetings down one path and No show meetings down another.

​
Website intent signal

Fires when a visitor to your site is identified. In the trigger picker, this appears as two variants:
  • Account Signal: identifies the visitor’s company in real time, as the page loads.
  • People Signal: identifies the visitor (name, title, email) in batches, roughly every 30 minutes.
Opening the trigger’s configuration shows the underlying fields, including a Trigger type that can also be set to a third option, Batched company (Vector), to identify the visitor’s company in batches instead of in real time.

​
CRM record created

Fires when a record is created in a connected CRM. CRM triggers are available once Salesforce or HubSpot is connected to your workspace.

​
CRM record updated

Fires when a record is updated in a connected CRM. It uses the same fields as CRM record created above (CRM, Record, and an optional Condition), but runs when a matching record changes rather than when one is created.