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

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

Creates a mail merge to a Word document. This is especially useful for Thank You letters, event attendance or volunteer forms, etc. 

Once your template document is uploaded to the Trigger Action and the merge fields have been matched to the available placeholder fields in Donorfy, when a constituent matches the criteria set within the Conditions. 

There is an option to set the Acknowledged on Date, as today, for Transactions that are being thanked via this method.

Documents will be available to download under Data Management > Documents to print

Will set the Acknowledged on Date for Transactions to be today.

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.

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

NOTE: only the Constituent email address and name are sent to Mailchimp as part of the Trigger. Tags and Purposes that are mapped via your Mailchimp settings will be sent when you perform the Donorfy to Mailchimp sync from your List.

Initiates a Mailchimp Journey campaign for the constituent related to the Trigger event.

NOTE: The constituent will need to be existing within the Mailchimp Audience for this Trigger action to be successful. This can be done by delaying the Trigger send and ensuring a daily sync to Mailchimp of all new Constituents. 

Constituents can be enrolled in dotdigital programs (sometimes referred to as Supporter Journeys) using Donorfy Triggers. You can find out more about  this here: Enrolling a contact in a Dotdigital program

Transactional (or one-off) emails can be sent through dotdigital using Donorfy Triggers. There are many reasons why you might want to send a transactional email, including acknowledging form submissions and acknowledging donations. You can find out more about  this here: Using Triggers to send transactional email (Dotdigital)

NOTE: This Action requires good knowledge of APIs and coding. And is something we'd recommend a web developer does on your behalf.

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

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.

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]