Skip to main content

Review Zap Triggers and Templates

R
Written by Roderick Sang

As described in the introduction to our Zapier integration, Zapier allows for the creation of automated connections, called Zaps. Zaps consist of a trigger and one or more actions; the trigger automatically initiates the action(s) through Zapier. Zaps can be set up in minutes with no coding.

Important: In edition to the existing Zap templates listed below, you can always custom-build your own Zaps – on your own or using Zapier’s AI-powered Zap builder – using the triggers identified below to prompt an action involving any of the 6,000+ web services connected to Zapier.

Zap Triggers

At present, Give Lively’s Zapier integration includes three triggers:

  • new donations

  • updated donations

  • updated donation status

Every time this Give Lively data changes, it can be used to trigger an action involving any of the 6,000+ web services connected to Zapier. These actions can be configured to utilize your Give Lively donation data (see a list of Give Lively data fields).

Zap Templates

Zap templates are basically pre-set Zaps. Both the trigger and the action(s) are already identified, but the user’s specific account information is needed. Templates are the fastest way to set up Zaps.

Give Lively has set up the following approved templates:

CRMs & Marketing Automation Tools

Donation Alerts

Email Marketing Platforms

Project management & collaboration tools

Donation Data Spreadsheets

Accounting & Reporting Tools

Advertising & Conversion Tracking

  • Give Lively + Google Ads – record a new donation in Google Ads (to fine-tune your ads) when a new donation is made via Give Lively

  • Give Lively + LinkedIn Conversions: ‍prompt LinkedIn Conversions to mark/track or send a conversion event when a new donation is made via Give Lively

  • Give Lively + Facebook Conversions:

Understand Zapier’s JSON Endpoints

Our integration with Zapier is powered by two JSON endpoints that are enabled when a Zapier API key is created in our platform. The endpoints detailed below exist only to power Give Lively's Zapier integration. They aren’t a public API, and we don’t support connecting to them directly, such as with custom code.

JSON Endpoint 1

  • Responds with a 200 status and { success: true } if the credentials are valid.

  • Responds with 404 otherwise.

JSON Endpoint 2

  • Responds with a JSON array of all donations received on the platform if the credentials are valid.

  • Responds with 404 otherwise.

  • Records are sorted in reverse chronological order of when they were most recently modified.

  • This endpoint takes an optional URL parameter ?start_time_ms=TIME. If specified, then results are limited to donations that have been created/updated since the specified time represented as milliseconds from midnight January 1, 1970.

Did this answer your question?