Skip to main content

Automation Triggers and Conditions Reference Guide

This guide provides a complete reference of the available Automation Triggers and Conditions in Swivel.

Written by Boni Newberry

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

  • Triggers determine when an automation begins.

  • Each automation can have one trigger.

  • Triggers fall into two categories:

    • Lifecycle Triggers

    • Date-Based Triggers

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 contat 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.

📌 Note: Lifecycle automations will not trigger off of imports or bulk updates.

Date-Based Triggers

Date-based triggers run when a specific date stored within a record is reached.

📌 Note: Swivel checks for date-based automations every hour. Depending on when the automation criteria is met, the action may not run immediately.

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

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:

  • 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

🔍 Tip: Multiple conditions can be used within the same automation.

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

Tags

Runs based on whether selected tags are Included, Excluded, or Equal to the selected values

Lead Source

Runs based on whether selected lead sources are Included, Excluded, or Equal to the selected values

Postal State

Runs based on whether selected states are Included, Excluded, or Equal to the selected values

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

Use these conditions to filter automations based on product information.

Condition

Description

Product Institution/Carrier

Runs based on if a product is associated with or not associated with the selected institution(s)

Product

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

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

📌 Note: Appointment Status options are system-defined and cannot be customized.

🔍 Tip: Appointment Types are customizable. See Appointment Types to learn more.


Marketing Event Conditions

Use these conditions to filter automations related to marketing events and attendance.

Condition

Description

Marketing 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)

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 a product status (or product statuses) are Included, Excluded, or Equal to

📌 Note: Event Attendance Status and Attendance Outcome options are system-defined and cannot be customized.


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

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.

🔍 Tip: If users are added to or removed from a group, future automation runs automatically use the group's current membership. Deactivated users are automatically skipped.

Did this answer your question?