Integrating With Your CRM
Work more efficiently with an integration
An integration is an automation tool that connects your different software applications. GiveDirect can integrate with several widely used CRM databases, allowing your donations and payments to flow automatically into your database.
Definitions
Integration: An integration is an automation tool that connects your different software applications to transfer data between them.
Tasks: A task is an event step in an integration. Tasks can lookup, compare, combine and create records in your applications.
Transaction: A transaction for GiveDirect is any event that generates funds to be transferred to the charity. A transaction can be a donation, payment, registration, or membership.
CRM: Customer Relationship Management; typically used by a nonprofit as a donor database.
GiveDirect can integrate with:
Don't see your product on the list? Contact us to see if an integration is possible.
What does an integration cost?
An integration is made up of a series of tasks.
Pricing is based on the number of tasks performed in your integration.
Tasks | Price |
|---|---|
| 300 Tasks /mo | $15 |
| 750 Tasks /mo | $35 |
| 1500 Tasks /mo | $50 |
What is a Task?
A task is an action taken to look up or create records in your CRM.
As a general rule, most integrations require two standard tasks per transaction, although some charities may require more complex integrations with four or five tasks per transaction.
To select your price plan, multiply the average number of monthly transactions with the number of tasks performed.
A charity with 100 GiveDirect transactions per month, using the standard 2 tasks per transaction, would pay $15/month (100*2 = 200 tasks).
However, if the same charity uses a more complex task set (let's say 4 tasks per transaction), they would pay $35/month (100*4 = 400 tasks).
How does an integration work?
Field Map and Conditional Formatting
GiveDirect will work with you to determine what data needs to be transferred from GiveDirect into your CRM. During this step, we will establish your conditional formatting requirements (i.e., date formatting, field concatenation, fixed values like General Ledger Codes or Record Owner, and IF/THEN statements). We will also determine the number of tasks to be performed.
Standard Integration Tasks
There are two standard integrations tasks that must be completed for an integration. There could be other tasks, but these are the ones that will always happen:
- Look for an existing contact record using the donor's email address or create a new contact if none exists.
- Create a new donation record for the contact.
Adding Multiple Applications To An Integration
You can add multiple apps to your integration workflow. For example, you can create an integration that will create a donation record in Salesforce AND add an email address to a MailChimp email list. Or, you could create a donation record in Neon AND update a record in QuickBooks Online. Each connected app will represent a new task in your integration.
Timing
Integrations are run during a nightly "rollup" for all donations received that day. You will receive a report via email after the nightly roll up is complete.
Recurring Donations
For recurring donations, we collect and store the Account ID to be used for each donor. This saves the step of looking up the Contact each time.
Exclusions
An integration can be customized to exclude some of your campaign forms or even to exclude by program designation. For example, you may want to send your donations to your CRM, but not your event registrations. Or, perhaps you support a 3rd party with one of your program designations and you want to manage donations made to that program separately. You can opt to have donations designated to a particular program from your gift designation menu excluded from the integration.
Refunded GiveDirect Transactions
Donations that are refunded with either a credit or a chargeback are not sent in the nightly rollup. Every charity manages refunds differently which makes it too difficult to standardize. When you receive an email notification from GiveDirect that a donation has been refunded or charged back, you will need to adjust your database manually based on your charity's own process for managing refunds.
Future Updates
We understand your database requirements and business processes will change over time. Updates to your integration file are always free of charge.
What can GiveDirect not do?
- We cannot send over a picklist (drop down) value that contains an ampersand "&". The integration throws an error when this happens. If you have picklist values that contain "&", like a campaign fund, you will need to modify the picklist in your database to use "and" instead.
- We cannot update a transaction that was previously sent. If you correct or update values in the GiveDirect database for a record, you will also need to make a manual correction in your CRM.
How do I know if a transaction has been sent to my CRM?
In the donation detail page, you will see a CRM Donation ID at the bottom of the page along with a sent date. If there is no ID or date, then you may use the green "Send" button at the top of the page.
Note: The send button will not update a record that has been sent previously. It may create a duplicate record in your database. For databases that use a duplicate record check, like Salesforce and Donor Perfect, the Send button will do nothing. If a previously sent transaction needs to be edited for any reason, you will need to be manually enter the corrections in your CRM.