Trigger Conditions

Conditions allow you to specify in what instance a Trigger should run.

For example, you may wish to initiate a Mailchimp automation when you receive a new donation, but only if that donation is over X amount.

 

Conditions are optional, and all of the conditions set must be met for the Actions to run.

 

mceclip0.png

 

Each Trigger type will have its own associated conditions. 

The Constituent in List condition is available to all Trigger Types.

 

Constituent in list

The constituent related to the event Constituent must either exist, or not exist in a list

mceclip1.png

For example, if an Activity is created on a Constituent profile, the Constituent must exist in a list for the actions to run.

 

Associated conditions will be available as below:

 

Conditions by Trigger Type

  • Recurring Payment Instruction 
    RPI in list - Recurring Payment Instruction must either exist, or not exist in a list
    Constituent in List
  • Transactions
    Transaction in list - The Transaction must either exist, or not exist in a list
    Constituent in List
  • Activities
    Activity in list - The Activity must either exist, or not exist in a list
    Constituent in List

 

 

Have more questions? Submit a request

Comments

Powered by Zendesk