Outcomes
Add action nodes to the right branch.
Configure safe values using event variables.
Use connectors without exposing raw tokens to the browser.
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.
Example workflow
Payment failed recovery
Stripe reports a failed subscription payment and the tenant needs a polite retry sequence before suspension.
Conditions
- Invoice status equals unpaid
- Customer email exists
- Subscription plan is not free
Actions
- Notify billing admin
- Email customer with payment link
- Wait 3 days
- Check invoice status again
- Create follow-up task if still unpaid
Safety checks
- Tenant suspension is behind a human approval node
- Max one reminder email per day
- Dead letter if Stripe token refresh fails
Try it: Paste a sample payment_failed payload and verify the no-email branch catches missing customer email.
Step 1
Add an action node
Action nodes perform work through approved backend tools. The AI and UI never receive raw OAuth tokens.
What to do
- Select a branch path.
- Search the action library.
- Add actions like sendEmail, createTask, createInvoice, notifySlack, humanApproval, or dispatchWebhook.
Check before continuing
- The node shows Ready or a clear missing value warning.
- The action belongs to the correct branch.
Step 2
Use event variables
Variables render event data into action configuration, such as customer email, deal title, invoice ID, or project name.
What to do
- Use variables like {{data.customerEmail}} or {{data.projectId}} where appropriate.
- Use Preview to inspect the rendered config.
- Add Exists conditions for required variables.
Check before continuing
- Rendered email recipients and entity IDs look correct.
- Fallback text is present when optional fields are missing.
Step 3
Publish connector actions
Custom HTTP actions and signed webhooks let admins connect external systems while keeping authentication server-side.
What to do
- Create reusable connector actions in Automation Studio.
- Choose auth mode: API key, OAuth reference, bearer token, or signed webhook.
- Validate request and response schemas before enabling.
Check before continuing
- Secrets are saved server-side only.
- Webhook endpoints are signed and have retry limits.
Pro tips
- Keep node labels short so the canvas remains readable.
- Use human approval nodes before expensive or sensitive actions.
Avoid these mistakes
- Do not hardcode personal emails in reusable workflows.
- Do not call external webhooks without timeout and retry limits.