---
updatedAt: 2026-10-09T22:30:00.000Z
---
# Automation Actions
Automations are built using a variety of actions that can be combined to create customized workflows tailored to your organization's needs. Automations are on the Standard, Professional, and Enterprise plans. Below is a list of available actions, along with descriptions and use cases for each.
No action changes a person's email, text, or call permission. To opt many people out at once, use the 'Opt Out of Communications' option in Bulk Update.
## Send Email
Automatically send personalized emails to supporters at specific points in your automation workflow. Emails can be customized with templates and dynamic fields to ensure each message is relevant and engaging.
**Use Case**: After a supporter signs up on your website, you can send them a welcome email introducing your organization and suggesting next steps they can take to get involved.
## Send Text
Send SMS messages directly to supporters' mobile phones. Text messages can be personalized with merge tags. To send a text later, put a Delay step before it.
**Use Case**: After a supporter RSVPs to an event, send them a text at once or after a Delay step. For reminders before each session, use the event's 'Automations' tab (see [Event Automations](/docs/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 tasks for team members to follow up with supporters. Tasks help your team stay organized and ensure that important follow-up actions are not missed.
The step sets the task notes, when the task is due, and which team member gets it.
**Use Case**: After a supporter makes a significant donation, automatically create a task for a team member to call and personally thank them.
## Assign Agent
Assign a supporter to a specific agent or team member who will be responsible for managing the relationship. This helps personalize communication and ensures continuity.
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.
**Use Case**: When a supporter expresses interest in volunteering, assign them to a volunteer coordinator who can guide them through the onboarding process.
**Use Case (Branch Captain)**: When a new supporter joins from a specific region, automatically assign them to their local Branch Captain for personalized outreach and onboarding.
## RSVP to Event
Automatically register supporters for events based on your selection criteria. This powerful action offers multiple assignment methods and safety features to ensure optimal event attendance while preventing conflicts.
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.
**Use Case**: When supporters complete a training program, automatically RSVP them to upcoming chapter meetings in their area using the "Nearest location" method, ensuring they stay engaged locally while preventing scheduling conflicts.
## Update Tags
Add or remove tags from a supporter's profile to segment your audience and tailor your communications. Tags help you organize supporters based on their interests, actions, or status.
**Use Case**: Automatically tag supporters based on their level of engagement, such as "Active Volunteer" or "High-Priority Donor," to personalize follow-ups and future outreach efforts.
## Update Custom Property
Update custom properties on a supporter's profile. Custom properties are fields you create to store specific information relevant to your organization.
For **multi-select (checkboxes) properties**, you can add the selected values to the current values or replace them.
For all other property types (text, number, date, single-select, etc.), the action sets the property to the specified value.
**Use Case**: After a supporter completes a training program, update their "Training Completed" custom property to "Yes" so you can track their progress.
**Use Case (multi-select)**: After a supporter attends a phonebank, add "Phonebanker" to their "Volunteer Skills" multi-select property without removing any other skills they've already been tagged with.
## 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
Automatically update a supporter's assessment status. Assessments are organization-defined categories that help you track supporter engagement levels or stages in your organizing pipeline.
**Use Case**: When a supporter attends their first event, automatically update their assessment from "New Contact" to "Engaged" to reflect their increased involvement.
**Use Case**: After a supporter completes a volunteer training, update their assessment to "Trained Volunteer" so your team knows they're ready for assignments.
## Webhook
Trigger a webhook to send data to an external system. Webhooks allow you to integrate Solidarity Tech with other platforms and services, enabling seamless data flow and extended functionality.
**Use Case**: When a supporter signs up, send their information to a third-party CRM or email marketing platform for further engagement.
### Passing Data in Webhooks
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.
#### Basic Example
```
https://your-api.com/endpoint?email={{ user.email }}&name={{ user.first-name }}
```
When executed for a supporter named "Jane Doe" with email "", this becomes:
```
https://your-api.com/endpoint?email=jane%40example.com&name=Jane
```
> 📘 **Note**: Special characters (spaces, @, etc.) are automatically URL-encoded for safe transmission.
### Available Variables
Use `{{ user.variable-name }}` to access supporter data. Some example variables:
| Variable | Description |
| ------------------------- | ------------- |
| `{{ user.first-name }}` | First name |
| `{{ user.email }}` | Email address |
| `{{ user.phone-number }}` | Phone number |
| `{{ chapter.name }}` | Chapter name |
A custom property uses its internal name with hyphens instead of underscores. For more tags, see [Merge Tags](/docs/merge-tags).
### Webhook Examples
#### Sending to Zapier
```
https://hooks.zapier.com/hooks/catch/12345/abcdef/?email={{ user.email }}&first_name={{ user.first-name }}&last_name={{ user.last-name }}&phone={{ user.phone-number }}
```
#### Sending to a Custom API
Put an API key in a custom header, not in the URL, because anyone who opens the step can see the URL.
```
https://api.yourservice.com/contacts/create?email={{ user.email }}&name={{ user.full-name }}&source=solidarity_tech&chapter={{ chapter.name }}
```
#### Passing Custom Properties
If you have a custom property called `member_type`:
```
https://your-api.com/sync?email={{ user.email }}&member_type={{ user.member-type }}
```
### HTTP Methods
The 'Method' menu offers GET, POST, and PATCH. Select the appropriate method based on your external service's requirements.