Actions
Actions are the operations your workflow performs on records. Each action node executes a specific task, from updating field values to sending notifications.
Action Types
| Action Type | Description |
|---|---|
| Update Field Value | Change a field on the record |
| Create Activity from Template | Schedule activities using templates |
| Create Note | Add a note to the record |
| Send Email (External) | Send email to customers using templates |
| Send Internal Email | Email team members |
| Send SMS Message | Text message via Twilio integration |
| Webhook / API Call | Call external systems |
Adding an Action
- Click the + button on any edge in your workflow
- Select Action
- Choose an action type from the dropdown
- Configure the action settings
- Click Save
The action node appears with an orange color and displays the action type.
Using Tokens
Tokens allow you to insert dynamic field values into text content. Many actions support tokens for personalization.
Inserting Tokens
- Place your cursor in a text field
- Right-click to open the context menu
- Select a field from the available tokens
- The token is inserted at your cursor position
When the workflow runs, each token is replaced with the actual value from the record.
Available Tokens
All fields on the record are available as tokens:
- System fields (Name, Created Date, etc.)
- Custom fields
- Related record fields (e.g., Contact Name on Project)
Example
If you insert the Contact Name token into a message, it will be replaced with the actual contact name (e.g., "John Smith") when the workflow executes.
Custom Labels
Give your action a descriptive name:
- Click on the action node
- Enter a Custom Label
- The label displays on the node in the canvas
Good labels:
- "Update to Pre-Production"
- "Welcome Email"
- "Notify Production Team"
Chaining Multiple Actions
You can chain multiple actions in sequence:
- Add first action after trigger
- Click + on the outgoing edge
- Add another action
- Repeat as needed
Actions execute in order from top to bottom.
Error Handling
When an action fails:
- The execution step is marked as failed
- The error message is logged
- Subsequent actions may still execute (depends on configuration)
- Check execution history for details
Common errors:
- Email template not found
- Invalid field value
- Webhook URL unreachable
- SMS delivery failed
Best Practices
Keep Actions Focused
- One operation per action
- Chain multiple simple actions
- Easier to debug and maintain
Test Before Publishing
- Create a test record
- Manually trigger the workflow
- Verify each action executes correctly
Use Meaningful Labels
- Describe what the action does
- Makes workflows easier to understand
- Helps with troubleshooting
Consider Timing
- Actions execute immediately unless delayed
- Add delays for time-sensitive sequences
- Consider recipient time zones for communications
Next Steps
- Update Field Value - Modify record fields
- Create Activity - Schedule tasks from templates
- Create Note - Add notes to records
- Send Email - Email customers
- Send Internal Email - Notify team members
- Send SMS - Text message notifications
- Webhook - Integrate with external systems