Zapier connects third-party apps with Bloomerang CRM, using customizable workflows to automate everyday tasks. Use it with Bloomerang CRM to automatically accomplish tasks that you would normally perform manually. With Zapier, you can connect thousands of apps with Bloomerang CRM.
Zapier Terms
Before you get started with Zapier, familiarize yourself with these important terms and concepts.
Zaps
Zaps are automated workflows that connect Zapier apps. For example, a Zap might update a Bloomerang CRM constituent whenever a Classy transaction occurs. This automated process saves you the time and effort of updating Bloomerang CRM constituents for every Classy transaction, and reduces the risk of errors that might occur in the manual data entry process.
A Zap consists of Triggers and Actions.
Triggers
A Trigger is an event that starts a Zap. In the previous example, the trigger is a Classy transaction. This triggering event tells Zapier to start the workflow. Third-party apps may offer their own unique triggers. For example, Mailchimp offers the New Subscriber and New Unsubscriber triggers.
The following Zapier triggers are available specifically for Bloomerang CRM:
New Constituent: Triggers when a new constituent is created in Bloomerang CRM. For example, this trigger could be used to keep track of newly-added constituents in a Google Sheet.
New Interaction: Triggers when a new interaction is created.
New or Updated Constituent: Triggers when a constituent is either created or updated. This trigger can be helpful if your Zap workflow can potentially include either new constituents or updates to existing constituents.
New Task: Triggers when a new task is created. For example, this trigger could be used to send a new task from Bloomerang CRM to Slack when a task is created.
New Transaction: Triggers when a new transaction is created. For example, when a new transaction is created, a Zap could send an automatic thank-you message. You can further customize the trigger by setting the transaction type (donations, pledges, pledge payments, recurring donation schedules, recurring donation payments) or the minimum or maximum transaction amount that should activate the trigger.
Note: If the transaction is part of a split payment in Bloomerang CRM, the New Transaction trigger considers only the total amount of the original transaction.
New Transaction Payment: Triggers for each new donation, pledge payment, and recurring donation payment created. This trigger is useful for setting up automatic thank-you messages when recurring payments occur.
Tip: Use the New Transaction Payment trigger to distinguish between split payment designations. For example, when a new sales receipt is created in QuickBooks Online, the New Transaction Payment trigger creates one Bloomerang CRM sales receipt for each split.
Updated Constituent: Triggers when a constituent is updated. This trigger allows you to keep track of updates to constituents, so you can easily reference any changes.
Actions
An Action is an event that occurs in response to a trigger, and which completes the Zap. In the previous Classy example, the action is the constituent update that occurs in Bloomerang CRM.
Tip: This example contains only one trigger and one action, but Zapier supports more complex workflow logic. Zaps can include multiple actions in response to a trigger, branching paths, loops, and more. For more information about customizing Zapier workflows, see the Zapier documentation.
The following Bloomerang CRM actions are available in Zapier:
Create Constituent: Creates a new constituent.
Create Donation: Creates a new donation with line item support, up to a maximum of 10 line items.
Create Interaction: Creates a new interaction.
Create Task: Creates a new task.
Note: The Create Task action creates Bloomerang CRM tasks, not Zapier tasks.
Update Constituent: Updates an existing constituent.
Find Constituent: Finds a constituent by name and at least one of the following: address, phone, or email. Can create a constituent if none were found.
Tip: Use the Find Constituent action when creating a constituent to avoid creating a duplicate.
Tasks
A Task is a completed Zap. In the previous Classy example, every time a new Classy transaction occurs and a Bloomerang CRM constituent is updated, the Zap runs one time. Every time this Zap runs, one task is completed. If Classy receives 10 transactions, the Zap runs 10 times, and 10 Zapier tasks will be completed.
Note: Every completed Zap generates one completed Zapier task, regardless of how many actions a Zap performs. Even if your Zap performs multiple actions, it still only creates one completed Zapier task when it runs.
Connecting Zapier and Bloomerang CRM
Integrating with Zapier is done completely from within Zapier. You don’t have to do anything from within Bloomerang CRM. To begin connecting Bloomerang CRM and Zapier, visit the Zapier website and sign up for Zapier for nonprofits.
After you receive access to Zapier, visit the Bloomerang CRM integrations page on Zapier to start creating your own Zap workflows.
Getting Started with Zaps
To get started using Zaps to customize Bloomerang CRM workflows:
Log into your Zapier Account.
Go to the Bloomerang CRM integrations page.
(Optional) Click Connect Bloomerang CRM to 7,000+ apps to create a new Zap from scratch.
(Optional) In the list of Zap templates, click Try It to create a new Zap from a template. Review the template’s prebuilt settings and customize as needed. For more information about customizing templates, visit Zapier Learn.
Turn on your Zap.
Tip: Always test your Zap to verify your connection to Bloomerang CRM and the third-party app, and the accuracy of the data flowing into and out of the Zap.
Popular Zaps
Try these popular Zap templates for common third-party apps: