Triggers are a powerful component in Donorfy which allows you to define custom behavior when specific events happen, such as a new constituent being added.
Triggers are available to both Essential and Professional Plans as follows:
Essentials - a maximum of 3 Triggers
Professional - unlimited number of Triggers
Triggers may require a Stored Procedure to be written - please contact Donorfy Support about what Trigger you require. A quote for the Stored Procedure to be written will then be provided.
Watch the overview and tutorial on Triggers here.
Creating a trigger
Triggers can be created by going to Data Management > Triggers.
Click on the + button to start creating your trigger.
You must supply a name and select the type of system event which will initiate the trigger.
Trigger type - Manual
This trigger type requires a user to press a button to initiate the trigger via Data Management > Triggers.
Trigger type - Scheduled
This trigger type is run on a user defined Schedule.
Trigger type - Constituent Added
This trigger is run when a constituent is added.
Trigger type - Constituent Updated
This trigger is run when a constituent is updated.
Trigger type - Constituent Deleted
This trigger is run when a constituent is deleted.
Trigger type - Activity Added
This trigger is run when an activity is added.
Trigger type - Activity Updated
This trigger is run when an activity is updated.
Trigger type - Activity Deleted
This trigger is run when an activity is deleted.
Trigger type - RPI Added
This trigger is run when an RPI is added.
Trigger type - RPI Updated
This trigger is run when an RPI is updated.
Trigger type - RPI Deleted
This trigger is run when an RPI is deleted.
Trigger type - Transaction Added
This trigger is run when a Transaction is added.
Trigger type - Transaction Updated
This trigger is run when a Transaction is updated.
Trigger type - Transaction Deleted
This trigger is run when a Transaction is deleted.
Conditions allow you to specify when 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 must be met for the Actions to run.
Condition type - Constituent in list
The constituent related to the event must exist in a list.
For example, if an Activity is created on a Constituent profile, the Constituent must exist in a list for the actions to run.
Condition type - RPI in list
The RPI in the event must exist in a list.
Condition type - Transaction in list
The Transaction in the event must exist in a list.
Actions can be re-ordered by dragging the panel up and down.
Actions must be given a name.
If enabled, the Only run if previous actions are successful option will result in the action being skipped if any of the steps above it in the trigger are unsuccessful or error.
Action type - Execute Stored Procedure
Requires Own Azure
The Execute stored procedure action will run a stored procedure on SQL server.
For example, a valid value would be [dbo].[sp_whoisactive]
Action type - HTTP POST
The HTTP POST action will send an HTTP POST request.
You can optionally define custom headers to be sent with the HTTP payload. Please note these are not stored encrypted.
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.
Action type - Initiate Mailchimp Automation
The Initiate Mailchimp Automation action will initiate a selected Mailchimp automation for the constituent related to the Trigger event.
Optionally, selecting a purpose will check whether the constituent has allowed communication through that purpose before running the Action.