Automation Actions
Automations are built from actions that you combine into a workflow. Automations are on the Standard, Professional, and Enterprise plans.
To opt many people out at once, use the 'Opt Out of Communications' option in Bulk Update.
Send Email
Send a personalized email to supporters at a point in the workflow, for example a welcome email after someone signs up.
Send Text
Send a text message that you can personalize with merge tags. To send a text later, put a Delay step before it. For reminders before each event session, use the event's 'Automations' tab (see Event Automations).
Send Admin Notification Email
The 'Send admin notification email' action sends an email to the addresses in 'To', such as your team, not to the person.
Add Follow-Up Task
Create a task for a team member to follow up with the supporter. The step sets the task notes, when the task is due, and which team member gets it.
Assign Agent
Assign the supporter to a team member who manages the relationship. Use the 'Assigned to' field to pick one team member, split people among several team members, or assign the person's Branch Captain. Branches are on the Professional plan.
RSVP to Event
Register the supporter for an event. Use the 'Selection Method' to choose which session each person gets. The 'Safety Options' can skip sessions that overlap another RSVP or that are full.

Update Tags
Add or remove tags on the supporter's profile.
Update Custom Property
Set a custom property on the supporter's profile. For multi-select (checkboxes) properties, you can add the selected values to the current values or replace them. For all other property types, the action sets the property to the specified value.
Update Chapter
The 'Update chapter' action makes a chapter that you pick the person's primary chapter, or adds it as a secondary chapter.
Update Assessment
Update the supporter's assessment, for example from "New Contact" to "Engaged" after a first event.
Webhook
Send data to an external system, such as a third-party CRM. The 'Method' menu offers GET, POST, and PATCH.
Merge tags work in three places: the URL, the values of custom headers, and the values of 'Body' fields. When the step runs, each merge tag becomes the person's data. Special characters are URL-encoded automatically.
https://your-api.com/endpoint?email={{ user.email }}&name={{ user.first-name }}
A custom property uses its internal name with hyphens instead of underscores. For more tags, see Merge Tags.
Put an API key in a custom header, not in the URL, because anyone who opens the step can see the URL.
Updated 2 days ago
