Workflow Triggers¶
Triggers define the event that starts a workflow. When the trigger condition is met, the workflow activates and begins executing its actions.
Available Triggers¶
Record Triggers¶
| Trigger | Description |
|---|---|
| Record created | Fires when a new contact, company, deal, or ticket is created |
| Record updated | Fires when a specific field changes on a record |
| Deal stage changed | Fires when a deal moves to a specific pipeline stage |
| Deal closed won | Fires when a deal is marked as won |
| Deal closed lost | Fires when a deal is marked as lost |
Support Triggers¶
| Trigger | Description |
|---|---|
| Ticket created | Fires when a new ticket is created (with optional priority filter) |
| Ticket resolved | Fires when a ticket moves to the resolved stage |
| Task overdue | Fires when a task passes its due date |
Other Triggers¶
| Trigger | Description |
|---|---|
| Form submitted | Fires when a specific form receives a submission |
| Date-based | Fires X days before or after a date field value |
| Manual | Triggered manually by a user through chat or the UI |
Configuring a Trigger¶
Each trigger type has specific configuration options:
Record updated example:
- Entity type: Contact
- Field: Lifecycle stage
- Changed to: SQL
This trigger fires whenever a contact's lifecycle stage is changed to SQL.
Date-based example:
- Entity type: Deal
- Date field: Close date
- Offset: 7 days before
This trigger fires 7 days before a deal's expected close date.
You
Create a workflow that triggers when a deal moves to Proposal Sent
Outsprint AI
I've created a workflow with the trigger "Deal stage changed to Proposal Sent." Now let's add the actions.
Pro Tip
Be specific with trigger conditions to avoid unnecessary executions. For example, trigger on a specific stage change rather than any record update.