Actions are the steps that execute when a workflow runs. This reference covers all available action types.
Household actions
Actions that work with clients and prospects.
Add tag
Adds a tag to the household.
| Setting | Description |
|---|
| Tag | Which tag to add |
Remove tag
Removes a tag from the household.
| Setting | Description |
|---|
| Tag | Which tag to remove |
Add note
Creates a note on the household.
| Setting | Description |
|---|
| Content | Note text (supports variables) |
Update household
Updates fields on the household.
| Setting | Description |
|---|
| Fields | Which fields to update and their new values |
Only works when the workflow’s trigger provides a prospect record.
Send email
Sends an email to household members.
| Setting | Description |
|---|
| To | Recipient (head of household, spouse/partner, or specific person) |
| Subject | Email subject (supports variables) |
| Body | Email content (supports variables and templates) |
| From | Sending user |
Send SMS
Sends a text message to household members. Requires a connected phone integration (RingCentral or MyRepChat).
| Setting | Description |
|---|
| Recipients | Head of household, spouse/partner, or both |
| Message | Message text (supports variables) |
| Phone integration | Which phone integration to send from |
| From phone number | Which phone number to send from (required for some integrations) |
SMS can only be sent to clients, not prospects. The recipient must have a phone number on file.
Add to sequence
Enrolls the household in an email sequence.
| Setting | Description |
|---|
| Sequence | Which sequence to enroll in |
Remove from sequence
Removes the household from an active sequence.
| Setting | Description |
|---|
| Sequence | Which sequence to remove from |
Start project
Creates a project for the household from a template.
| Setting | Description |
|---|
| Template | Which project template to use |
| Assigned to | Who to assign the project to |
Create opportunity
Creates an opportunity for the household.
| Setting | Description |
|---|
| Pipeline | Which pipeline to add to |
| Stage | Starting stage |
Find opportunity
Locates an existing opportunity for the household. The found opportunity can be used in later actions (e.g., move stage).
| Setting | Description |
|---|
| Pipeline | Optional: limit search to a specific pipeline |
If no opportunity is found, the workflow stops at this action.
Task actions
Actions for creating and managing tasks.
Create task
Creates a new task.
| Setting | Description |
|---|
| Title | Task title (supports variables) |
| Description | Task details (supports variables) |
| Due date | When the task is due |
| Assigned to | Who to assign the task to |
| Linked to | Household, meeting, or other record |
Update task
Updates an existing task’s fields.
| Setting | Description |
|---|
| Fields | Which fields to update and their new values |
Record actions
Actions that work across record types.
Adds a comment to a record.
| Setting | Description |
|---|
| Comment | Comment text (supports variables) |
Opportunity actions
Actions for pipeline management.
Move stage
Moves an opportunity to a different pipeline stage.
| Setting | Description |
|---|
| Stage | Target stage |
AI actions
AI-powered actions for intelligent automation.
Draft email
Uses AI to draft an email based on your instructions.
| Setting | Description |
|---|
| Prompt | Instructions for the AI |
| Context | What information to include |
Research
Uses AI to search and summarize information about a record.
| Setting | Description |
|---|
| Research query | What to research |
| Research subject | Which record type to research (client, prospect, meeting, task, etc.) |
Categorize
Uses AI to sort records into categories.
| Setting | Description |
|---|
| Categories | List of possible categories |
| Criteria | How to categorize |
Filter
Uses AI to decide if the workflow should continue based on contextual criteria.
| Setting | Description |
|---|
| Criteria | Conditions to evaluate |
| Setting | Description |
|---|
| Source | Email to parse |
Flow control
Actions that control workflow execution.
Branch
Splits the workflow into multiple paths based on conditions. Each branch has named conditions, and a default path runs if no conditions match.
| Setting | Description |
|---|
| Branch conditions | Named conditions for each path, evaluated in order |
| Default path | Path that runs if no conditions match (required) |
Loop
Repeats actions for a collection of items.
| Setting | Description |
|---|
| Collection | What to loop over |
Wait
Pauses workflow execution for a set duration.
| Setting | Description |
|---|
| Duration | How long to wait |
System actions
Actions for notifications and record lookup.
Internal notification
Sends an in-app notification to team members.
| Setting | Description |
|---|
| To | Who to notify |
| Message | Notification text (supports variables) |
Search record
Finds a specific record by query. Results can be used in later actions.
| Setting | Description |
|---|
| Record type | What type of record to search for |
| Query | Search query (supports variables) |
Confetti
Shows a celebration animation. Useful for milestone moments like closing deals or completing onboarding.
| Setting | Description |
|---|
| Message | Celebration text |
Using variables in actions
Most action fields support variables. Variables reference data from the trigger and earlier actions:
Task title: "Follow up with {{household.name}}"
Email body: "Hi {{person.first_name}}, ..."
Best practices
- Keep workflows focused — Each workflow should do one thing well
- Use descriptive text — Task titles and messages should be clear
- Test each action — Verify actions work as expected before publishing
- Consider dependencies — Some actions (like find opportunity) can stop a workflow if no record is found
Next steps
