Outcomes
Choose the correct trigger for a workflow.
Use Event Explorer to inspect recent payloads.
Create workflows from real module events.
Examples
Use these patterns while learning this chapter.
Example workflow
Closed-won deal handoff
Sales marks a HubSpot or CRM deal as Closed Won and operations needs the work package ready within minutes.
Conditions
- Deal amount is greater than 5000
- Customer email exists
- Deal owner exists
Actions
- Create project from deal name
- Create kickoff task list
- Create draft invoice
- Send welcome email after approval
- Notify Slack sales-ops channel
Safety checks
- Invoice creation requires approval
- Email preview is reviewed before launch
- Slack failure goes to retry path
Try it: Use Event Explorer to pick a real closed-won deal, run Sandbox, then confirm it would create one project, tasks, invoice, and notification.
Step 1
Select a trigger
Triggers listen for events emitted by CRM, billing, tickets, projects, HRM, calendar, messages, and connectors.
What to do
- Open the Trigger dropdown in Workflow setup.
- Select the event that matches the business moment.
- Read the event description before adding actions.
Check before continuing
- The trigger matches exactly one business moment.
- The event is emitted by the module or connector you expect.
Step 2
Inspect sample payloads
Payloads provide values like customer email, project ID, invoice amount, status, priority, and assignee.
What to do
- Open Event Explorer.
- Filter by module or event type.
- Click Create workflow from event to load its payload into the builder.
Check before continuing
- The payload includes required recipients or entity IDs.
- Missing values are handled with conditions or fallback actions.
Step 3
Name the event source
Sources make troubleshooting easier when events come from external systems like HubSpot, Stripe, Slack, or email.
What to do
- Check the source value in the preview payload.
- Use source conditions when a workflow should only run for one connector.
- Keep connector-specific workflows separate until the behavior is stable.
Check before continuing
- You can tell whether the event came from the app, a connector, or a manual test.
Pro tips
- Use Event Explorer to build from real data instead of guessing JSON paths.
- Create separate workflows for different high-value events before combining branches.
Avoid these mistakes
- Avoid broad triggers when a narrow event exists.
- Do not rely on optional fields unless you add an exists condition first.