Automations
Automation Triggers and Conditions Reference Guide
This guide provides a complete reference of the available Automation Triggers and Conditions in Swivel.
Use this article when building or troubleshooting automations to understand which events can trigger an automation and which conditions can be used to further refine when it runs.
Automation Triggers
Section titled “Automation Triggers”-
Triggers determine when an automation begins.
-
Each automation can have one trigger.
-
Triggers fall into two categories:
- Lifecycle Triggers
- Date-Based Triggers
Lifecycle Triggers
Section titled “Lifecycle Triggers”Lifecycle triggers run when a user action or record update occurs within Swivel.
| Trigger | Description |
|---|---|
| Contact Created Only | Runs when a contact is first created |
| Contact Updated Only | Runs when a contact is updated • Select from the available fields that can be updated to trigger the automation |
| Contact Created or Updated | Runs when a contact is created or updated • Select from the available fields that can be updated to trigger the automation |
| Contact Note Created | Runs when a contact note is added to a contact. |
| Contact Opportunity Created | Runs when a new Opportunity is created for a contact. |
Date-Based Triggers
Section titled “Date-Based Triggers”Date-based triggers run when a specific date stored within a record is reached.
| Trigger | Description |
|---|---|
| Birthdate | Runs based on a contact’s birthday |
| Product Open Date | Runs based on a product’ open date |
| Product Issued Date | Runs based on a product’s issued date |
| Product Effective Date | Runs based on a product’s effective date |
| Appointment Date | Runs based on an appointment date |
| Event Attendance Date | Runs based on an event attendance date |
Automation Conditions
Section titled “Automation Conditions”Conditions are optional filters that control when an automation runs, and allow you to be more specific about which records should qualify after the trigger occurs.
Examples Include:
Section titled “Examples Include:”- Only contacts with an Active status
- Only contacts assigned to a specific state
- Only products from a specific carrier
- Only notes created by a specific user or group
Contact Conditions
Section titled “Contact Conditions”Use these conditions to filter automations based on contact information.
| Condition | Description |
|---|---|
| Contact Category | Runs based on whether selected categories are Included, Excluded, or Equal to the selected values |
| Contact Status | Runs based on whether selected statuses are Included, Excluded, or Equal to the selected values |
| Contact Tags | Runs based on whether selected tags are Included, Excluded, or Equal to the selected values |
| Contact Lead Source | Runs based on whether selected lead sources are Included, Excluded, or Equal to the selected values |
| Contact Servicing Agent | Runs based on the Assigned to on the Contact. *Please note, this is different than the Agent of Record displayed on the product. |
| Primary Address State | Runs based on whether selected states are Included, Excluded, or Equal to the selected values |
| Primary Address Zip code | Runs based on whether selected zip codes are Included, Excluded, or Equal to the selected values |
| Contact Age | Runs based on a specific contact age *Must be a whole number |
Product Conditions
Section titled “Product Conditions”Use these conditions to filter automations based on product information.
| Condition | Description |
|---|---|
| Product Institution | Runs based on if a product is associated with or not associated with the selected institution(s) |
| Product Offering | Runs based on whether selected products are Included, Excluded, or Equal to the selected values |
| Product Status | Runs based on whether selected product statuses are Included, Excluded, or Equal to the selected values |
Appointment Conditions
Section titled “Appointment Conditions”Use these conditions to filter automations related to appointments.
| Condition | Description |
|---|---|
| Appointment Status | Runs based on whether selected appointment statuses are Included, Excluded, or Equal to the selected values |
| Appointment Type | Runs based on whether selected appointment types are Included, Excluded, or Equal to the selected values |
Marketing Event Conditions
Section titled “Marketing Event Conditions”Use these conditions to filter automations related to marketing events and attendance.
| Condition | Description |
|---|---|
| Event Type | Select if you want the automation to run based on if a product is associated with or not associated with the selected institution(s) |
| Event Attendance Outcome | Select if you want the automation to run based on if a product (or products) are Included, Excluded, or Equal to |
| Event Attendance Status | Select if you want the automation to run based on if the contact’s event attendance status is Pending, Attended, Canceled, No Show, Rescheduled, or Waitlisted. |
| Event Attendance Registered | Select if you want the automation to run based on if registered Yes or No |
| Event Attendance Confirmed | Select if you want the automation to run based on if confirmed Yes or No |
Opportunity Conditions
Section titled “Opportunity Conditions”Use these conditions to filter automations related to opportunities.
| Condition | Description |
|---|---|
| Opportunity Sales Stage | Runs based on whether selected sales stages are Included, Excluded, or Equal to the selected values |
| Opportunity Tags | Runs based on whether selected opportunity tags are Included, Excluded, or Equal to the selected values |
Note Conditions
Section titled “Note Conditions”The Note Created By condition is available when using the Contact Note Created trigger.
Use this condition to control which users can trigger a note-based automation.
| Condition | Description |
|---|---|
| Note Create By | Includes: Runs only when the selected user(s) or members of the selected group create a note. Excludes: Runs for everyone except the selected user(s) or members of the selected group. |

