Workflow Triggers Reference
Every workflow starts with exactly one trigger. The trigger determines when the workflow fires and what its subject is. The subject is the object that all subsequent steps operate on -- either an Event or a Form Response.
This page documents all nine triggers with their configuration fields, subject types, and practical examples.
Subject types
The subject type controls which actions and conditions are available in the workflow steps that follow the trigger.
| Subject | Available actions | When used |
|---|---|---|
| Event | All actions (Send Email, Send Notification, Send Webhook, Update Event Status, Update Event Field, Assign Event, Add Tag, Remove Tag) | Most triggers |
| Form Response | Communication actions only (Send Email, Send Notification) | Form triggers with Contact form type |
When a form trigger uses the Event or Detail form type, the subject is Event (because the system creates or links the event before the workflow fires). Only the Contact form type produces a Form Response subject.
Event triggers
Event created
Fires immediately when a new event is created in your workspace.
Configuration fields: None -- this trigger has no configurable options.
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| (none) | -- | -- | -- | -- |
Subject type: Event
Example: You want every new event to be automatically assigned to your operations lead and tagged with "needs-review". Create a workflow with the Event created trigger, then add an Assign Event action followed by an Add Tag action.
Event status changed
Fires when an event transitions from one status to another. You can narrow it to specific source statuses, target statuses, or both.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| From status | No | One or more event statuses (multi-select) | (empty -- any source status) | When set, the trigger only fires if the event was previously in one of these statuses. |
| To status | Yes | One or more event statuses (multi-select) | (empty) | The trigger fires when the event moves into one of these statuses. |
Subject type: Event
Example: You want to send a confirmation email when an event is set to "Confirmed". Set To status to "Confirmed" and leave From status empty. Then add a Send Email action with your confirmation template. If you only want this for events coming from "Pending", also set From status to "Pending".
Event field changed
Fires when one or more specific fields on the event are modified.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Fields | Yes | One or more event fields (multi-select) | (empty) | The fields to watch for changes. |
| Field matching | No | At least one field / All fields | At least one field | At least one field -- fires when at least one of the selected fields changes. All fields -- fires only when all selected fields change in the same update. |
Subject type: Event
Example: You track a "Budget" and a "Venue" field on your events. You want to notify the finance team whenever either field changes. Select both fields and set Field matching to At least one field. Then add a Send Notification action targeting the finance team member.
Form triggers
Form submitted
Fires when a form response is submitted for the first time. You can filter by form type.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Form type | No | Event, Contact, or Detail | (empty -- all form types) | Restricts the trigger to a specific form type. |
Subject type: Depends on the Form type value.
| Form type | Subject |
|---|---|
| Event | Event (the system creates the event before the workflow runs) |
| Detail | Event (form is linked to an existing event) |
| Contact | Form Response (standalone form, no event) |
| (empty) | Event (unless the actual form is a contact form) |
When the subject is Form Response, event-only actions (Update Event Status, Update Event Field, Assign Event, Add Tag, Remove Tag, Send Webhook) and event-only conditions are not available.
Example: You have a "Contact" form on your website. When someone submits it, you want to automatically send them a confirmation email. Set Form type to Contact and add a Send Email action.
Form response updated
Fires when an existing form response is modified after its initial submission. You can filter by form type, which fields changed, and how field matching works.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Form type | No | Event, Contact, or Detail | (empty -- all form types) | Restricts the trigger to a specific form type. |
| Changed fields | No | One or more fields (multi-select) | (empty -- any field change) | When set, the trigger only fires if at least one of the listed fields was changed. |
| Field matching | No | At least one field / All fields | At least one field | At least one field -- fires when at least one of the selected fields changes. All fields -- fires only when all selected fields change in the same update. |
Subject type: Same rules as Form submitted -- depends on Form type.
Example: You have a detail form attached to events. You want to be notified when the "Dietary Requirements" field is updated so you can adjust catering. Set Form type to Detail, add "Dietary Requirements" to Changed fields, and add a Send Notification action.
Time-based triggers
Time before event
Fires a specified amount of time before the event date. The system checks scheduled triggers periodically and executes them when the time arrives.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Offset | Yes | Integer, minimum 1 | (empty) | The number of time units before the event. |
| Unit | Yes | Minutes, Hours, Days, or Weeks | (empty) | The unit for the offset value. |
Subject type: Event
Example: You want to send a reminder email to your team 2 days before every event. Set Offset to 2 and Unit to Days. Then add a Send Email action with your reminder template.
Time after event
Fires a specified amount of time after the event date. Useful for follow-up actions.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Offset | Yes | Integer, minimum 1 | (empty) | The number of time units after the event. |
| Unit | Yes | Minutes, Hours, Days, or Weeks | (empty) | The unit for the offset value. |
Subject type: Event
Example: You want to automatically request feedback 1 week after each event ends. Set Offset to 1 and Unit to Weeks. Then add a Send Email action with your feedback request template.
No activity
Fires when no activity has occurred on the event for a specified number of days. "Activity" includes any update to the event, its forms, status changes, or assignments.
Configuration fields:
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| Days of inactivity | Yes | Integer, minimum 1 | (empty) | The number of days without any activity before the trigger fires. |
Subject type: Event
Example: You want to flag stale events that have had no updates for 14 days. Set Days of inactivity to 14, then add an Add Tag action with a "stale" tag and a Send Notification action to alert the assigned team member.
Manual trigger
Manual trigger
Does not fire automatically. You start the workflow by hand from the workflow detail page using the Trigger Now button. This lets you select a specific event and execute the workflow on demand.
Configuration fields: None -- this trigger has no configurable options.
| Field | Required | Values | Default | Effect |
|---|---|---|---|---|
| (none) | -- | -- | -- | -- |
Subject type: Event (you select the event when triggering manually)
Example: You have a complex event setup checklist that involves sending multiple emails, updating fields, and assigning tasks. Rather than running this automatically, you create a workflow with a Manual trigger so your team can execute it on demand for each event.
Trigger groups in the UI
When you choose a trigger in the editor, they are organized into four groups:
| Group | Triggers |
|---|---|
| Event | Event created, Event status changed, Event field changed |
| Forms | Form submitted, Form response updated |
| Time-based | Time before event, Time after event, No activity |
| Manual | Manual trigger |