Triggers

Follow

Triggers are a powerful feature of Donorfy which allow you to define custom behaviours when specific events happen, such as a new constituent being added, new volunteer application and so on.

What is a trigger?

A trigger = an automation. Easy to set up, a trigger comprises:

  1. a trigger type - a Donorfy event, such as “a new Transaction has been created”

  2. a condition - such as £500 or more

  3. one or more actions - such as “send and email the Chief Exec”; “enrol the donor in an automated sequence of emails” and so on

Watch the overview and tutorial on Triggers here.

Availability

Triggers are available to both Essential and Professional Plans as follows:

  • Essentials - a maximum of 3 Triggers
  • Professional - unlimited number of Triggers

Trigger Types and conditions

Triggers are "fired" when the trigger type event happens. However, you may only wish the actions to be performed if the trigger action (for example - RPI Added) was for a certain campaign. You can control that be adding a Condition to your trigger. Conditions are filters in corresponding Donorfy Lists.

You can add a delay to your trigger which means you can create a trigger to send a follow up response

 

mceclip1.png

 

mceclip0.png

This table shows all of the available trigger types, and the types of List whose filters can be used to provide further conditions for the trigger's action(s) to be performed.

Trigger Type

List Types for trigger conditions

Notes

Constituent Added

Constituent

These triggers are executed automatically, according to their conditions (if present)

 

Constituent Updated

Constituent Deleted

Activity Added

Constituent and Activity

Activity Updated

Activity Deleted

Transaction Added

Constituent and All Transactions (note: not Transaction Payment or Transaction Allocation)

Transaction Updated

Transaction Deleted

RPI Added

Constituent and Recurring Payment Instruction

RPI Updated

RPI Deleted

Scheduled

n/a

Scheduled triggers run on a user-defined schedule - Daily, Hourly, Every x minutes

Manual

n/a

Manual triggers require a user to click a button to initiate them, via Data Management | Triggers

Example of an RPI List with a filter. This example is ensuring that the trigger only fires if if the RPI was added today and the campaign in Spring 2022.

mceclip0.png

Trigger Actions

Actions are the tasks you want the trigger to perform. This table describes all the available actions. Please note that not all actions area available to all trigger types - see table below.

Action Description
Email User

Sends an email to one or more recipients. Recipients must be Donorfy users. The email is composed in the Action, and provides placeholders for data to be "merged" into the subject and body.

The email is sent via the Email Server Settings (see Settings | Configuration | Email Server Settings).

mceclip1.png

Email Constituent

Sends an email to the constituent that is the subject of the trigger. The email is composed in the Action, and provides placeholders for data to be "merged" into the subject and body.

The email is sent via the Email Server Settings (see Settings | Configuration | Email Server Settings).

mceclip0.png

Initiate Mailchimp automation

Initiates a Mailchimp automation campaign for the constituent related to the Trigger event. More information on setting up an automation campaign can be found in this article.

mceclip2.png

Optionally, selecting a purpose will check whether the constituent has allowed communication through that purpose before running the Action.

HTTP Post

NOTE: this action requires knowledge of APIs and coding.

Send an HTTP POST request to another service's API. You can optionally define custom headers to be sent with the HTTP payload. Please note these are not stored encrypted.

mceclip4.png

The payload can be different depending on the Trigger type. Currently, there is only one payload type.

Example of a standard payload

This HTTP body is sent from a Constituent added event.

{
"TriggerType": 6,
"EntityType": "Constituent",
"EntityId": "632c9e6f-bded-ea11-b5d9-501ac580925b",
"EntityNumber": 583,
"Timestamp": "2020-09-03T08:15:31.5659533+00:00"
}

The optional headers section is for custom data that you would like to add. This does not use any placeholders or data fields from within Donorfy - it is free text data only.

Execute a Stored Procedure

NOTE: This action is available only to customers with the Own Azure option.

Runs a Stored Procedure on your Microsoft Azure SQL database. For example, a valid value would be [dbo].[sp_whoisactive]

 

Trigger types and the available Actions

Certain actions are restricted to certain trigger types. This table shows which actions can be applied to triggers of the various types:

Trigger Type

Email User

Email Constituent

Initiate Mailchimp Automation

HTTP Post

Execute a Stored Procedure

Constituent Added

Constituent Updated

Constituent Deleted

Activity Added

Activity Updated

Activity Deleted

Transaction Added

Transaction Updated

Transaction Deleted

RPI Added

RPI Updated

RPI Deleted

Scheduled

Manual

 

For each action check or un-check the option to Only run if all previous actions are successful. If ticked it will result in the action being skipped if any of the steps above it in the trigger are unsuccessful or error.

Comments

0 comments
Please sign in to leave a comment.
Powered by Zendesk