Triggers & Actions
Module: Automations • 8:43
Overview
Triggers and actions are the two building blocks of every workflow. A trigger is how a contact enters the automation (for example, a form being submitted), and actions are what happens to that contact next (adding a tag, creating an opportunity, sending an email, or branching down a conditional path). This lesson walks through the full trigger and action menus so you understand everything that's possible inside the workflow builder.
Step-by-Step Instructions
Create a workflow and add a trigger
Go to Automations, create a new workflow from scratch, AI, or a template, and rename it. Click Add New Trigger to open the trigger sidebar — this is how the lead enters the workflow.
Pick the right trigger
Common triggers include contact created/changed, tag added, inbound webhook, customer reply, form submitted, survey submitted, appointment status, opportunity changed, and payments received (invoice signed, payment received, order submitted, contract signed). Form submitted and tag added are the most used.
Configure and save the trigger
Rename the trigger to the form or event name, select the specific form or resource, and hit Save Trigger. With autosave on, the trigger now appears at the top of the workflow. You can copy, delete, or view its stats, or click back in to edit.
Add your first actions
Click the plus button to add actions — what happens to the contact. The most-used actions are Add/Remove Tag (e.g. tag them 'submitted one-on-one application') and Create/Update Opportunity (e.g. add them to a New Lead pipeline). Always name the action so you can see what it does at a glance.
Use communication actions
Under Communications you can send emails and texts, internal Slack notifications, calls, voicemails, messenger, Instagram DMs, and internal notifications (a message to yourself that a new contact came in). Review requests and webhooks (sending data to Google Sheets or a third party) are also here.
Build if/else conditional branches
Under Internal, add an if/else to fork the journey. For example, 'has tag = active client' sends active clients down one path and inactive clients down another. Rename each branch so the logic is clear without clicking in.
Add wait steps
Wait steps hold a contact until a condition is met: a set period of time, a specific date and time, a recurring window, until the contact replies, until a user replies, or until the contact takes an action. For example, wait one day, then send a follow-up message.
Explore the full action menu
Beyond the basics you have events, splits, formatting, add/remove from workflows, AI agents, appointments, payments (invoices, estimates, contracts), affiliates, memberships (grant/revoke courses, issue certificates and badges), communities (grant/revoke access), AI actions (translate, summarize), and third-party app integrations.
Common Mistakes
- Forgetting to save changes before navigating away.
- Not testing the configuration after setting it up.
- Skipping the prerequisites mentioned in the overview.
OS University™