Triggers
Learn about Triggers in WaymakerOS.
Triggers define what starts an automation. Every automation has exactly one trigger.
Trigger types
Choose where the trigger comes from, then the event.
| Source | Events |
|---|---|
| Tables | Row Created, Row Updated, Row Deleted |
| Forms | Form Submitted |
| Taskboards | Task Created, Task Updated, Task Completed, Task Moved, Task Assigned |
| Journeys | Email Sent, Email Opened, Email Clicked, Email Bounced, Contact Unsubscribed |
| Shared Inboxes | Email Received, Email Replied, Email Assigned |
| Schedule | Runs on a schedule |
| Webhook | Runs when another service sends a request |
| Manual | Runs when you start it |
Not working yet: the event list also shows Field Changed, Form Confirmed, Due Date Approaching, Task Overdue, Contact Enrolled, Contact Completed Journey and Contact Dropped. Nothing sends these events yet, so an automation that uses one of them never runs.
Conditions
For Tables, Forms, Taskboards, Journeys and Shared Inboxes, pick the specific table, form, board, journey or inbox, then add Conditions to narrow when the automation runs (for example, only when a field changed to a value). Row Updated and Task Updated need at least one condition, so that not every change starts a run.
Example: When the "Contact Us" form is submitted, create a row in the Leads table and send a confirmation email.
Schedule
Enter the schedule as a cron expression: minute, hour, day of month, month, day of week. For example, 0 9 * * * runs every day at 9 AM.
Webhook
The trigger shows the automation's own webhook URL. Give this URL to the other service; each POST request to it starts a run, and the request body is available to your steps.
Trigger variables
Every trigger produces variables that subsequent actions can reference:
| Trigger Type | Available Variables |
|---|---|
| Forms | All form field values (e.g., {{name}}, {{email}}) |
| Tables, Taskboards, Journeys, Shared Inboxes | Details of the row, task, contact or email (e.g., {{task.name}}, {{task.status}}) |
| Schedule | Current timestamp |
| Webhook | Full request payload |
Use {{variable_name}} syntax in action configurations to reference trigger data.
Testing triggers
Click Test Run at the top of the automation to run it once with sample trigger data. The run appears in the Runs tab, so you can check each step before you activate the automation.
Next steps
- Actions — define what happens when triggered
- Automation Templates — common automation patterns
- Introduction to Automations — overview