Zapier + donations and payments
Zapier is not an integration— it is simply a connection between two systems with Zapier as the midpoint. If you want something specific to pull in from the source system to Levitate, it will need to be explicitly added through a Zap.
Now, we offer a connection between Levitate, Zapier, and certain payment platforms used by NonProfit clients to collect donations.
Never used Zapier before? Take a minute to read our rundown on how it works.
Zapier is able to push payment or donation info collected on PayPal, Stripe, Give-Lively, and Bloomerang into Levitate. This donation information will be associated with the contact information of the donor and can be used in our Donation Boards!
There are three required fields for creating a donation: Email Address, Donor Name, and Donation Amount. If the Donation Date is not provided through the zap from the payment platform, we default to today’s date. So, in order for a donation to be created, the zap must include the Email Address, Donor Name, and Donation Amount.
There are other fields that can be mapped over to Levitate, too!
While there are templates available, there is no guarantee that the template will work between your source system, Zapier, and Levitate. We highly recommend that all Zaps are set up and mapped manually.
Paypal
When getting connected to PayPal in Zapier, you must follow the prompt to add a Zapier URL to your PayPal IPN settings. It's linked and explained when you click through the 'PayPal IPN settings' link.
Levitate |
Paypal |
donorId | payer_id |
donorName | first_name + last_name |
amount | payment_gross |
date | payment_date |
stage | payment_status |
payer_email | |
externalID | receipt_id |
*Paypal is classified as a Premium Zapier App, which requires a paid Zapier subscription for use.
Stripe
When connecting to Stripe in Zapier, you'll first see a screen that asks for a 'Test mode secret API key'; you do not need to enter this. Just click 'Yes, contine to Stripe' and you'll just need to login with your regular Stripe credentials.
Levitate |
Stripe |
donorId | customer_id |
donorName | customer_name |
amount | amount |
stage | status |
customer_email | |
externalId | id |
Give Lively
When connecting to Give Lively in Zapier, you'll need to provide your Give Lively Domain, it must be your Production Domain. You'll also need to provide your Organization ID and a Give Lively API Key (not to be confused with the API Key we generate in Levitate). Here's what it looks like, steps are included.
Levitate |
Give Lively |
donorName | full_name |
amount | gross_amount |
date | date |
stage | payment_status |
campaign | campaign_id |
externalId | id |
Bloomerang
When connecting to Bloomerang in Zapier, you'll need to login with your Bloomerang credentials when prompted.
Levitate |
Bloomerang |
donorID | Constituent_ID |
donorName | Constituent_FirstName, Constituent_LastName |
amount | PaymentAmount |
date | TransactionDate |
type | PaymentTributeType |
campaign | PaymentCampaign_ID |
Constituent_PrimaryEmail_Value |
|
externalId | TransactionID |
Want to create and update contacts in Levitate, from Bloomerang, using Zapier? We can do that too. Check out our guide here.
GiveButter
When connecting to GiveButter in Zapier, you will need to create and provide an API key using GiveButter's integration settings for Zapier. Only GiveButter admins can create an API key.
Levitate | GiveButter |
Donor Name Required |
First Name, Last Name* *These are two separate fields, both need to be mapped with a space between them. OR Giving Space Name** **Giving Space Name displays the First and Last name as one field |
Donor Email Required |
Email* *Like with all other Zaps, email will be used to initially merge contacts. Once a Zap contact has merged by email once, it will merge by AdditionalID from there on out |
Donation Amount Required |
Amount* *There are a few different cash value amounts listed, including a total with fees and the fee itself. We recommend asking on a case by case basis which amount is best for your record keeping and outreach. |
Donation Date | Created At |
Donation Type | Dedication Type* *This one might not be the most helpful field, but the best fit in GiveButter seems to be Dedication Type– which may or may not be relevant to how your org's data is stored. |
Campaign | It doesn’t seem like GiveButter is showing a user assigned campaign name that would be helpful to an end user. There are two fields associated with campaign, but both look like codes: |
Donation Stage | Status |
External ID | Campaign ID* *This field is used for making each donation logged in Levitate unique– this is not something that displays on the front end. |
Donor ID | Contact ID* This is the field that will allow contacts with multiple donations to continually merge, rather than create a new contact with every new donation. |
Just like with any other service used in tandem with Zapier, Zapier may require payment at a certain level or volume of usage. We do not charge our Levitate clients to use Zapier + Levitate, but other platforms might.