Skip to main content

Sometimes source data, especially from a spreadsheet, already has a Bloomerang account number.

Using this as the search key (which is possible with Bloomerang’s internal import tool) would greatly reduce mismatched searches. It would also prevent duplicate account creation when the source data has no (or a different) mailing address, phone, or email address.

If it’s not possible with the standard action steps, can it be done with webhooks?

Hi ​@aaron_s,

 

Welcome to the Community.

 

Using unique identifiers like account numbers in Zapier can improve data accuracy and prevent duplicates. To match Bloomerang constituents, set up a "Find  Constituent" action step, use 'Account Number' as the search key, and map it to your spreadsheet column. If standard steps don't suffice, custom API requests via webhooks may be an alternative, but they require knowledge of Bloomerang's API.

 

Let us know if you have further inquiries.


use 'Account Number' as the search key, and map it to your spreadsheet column.

That’s what I would expect, but Account Number is not an available field in the "Find  Constituent" action. Hence the question.


Hi ​@aaron_s,

Before we dig deeper into this, would you mind sharing a detailed screenshot of how your Zap is configured? Also, please share a screenshot of the “CONFIGURE” section of the action step that shows all of its fields.

Please don't include personal information in the screenshot, or be sure blur out any personal information.

Thanks!


I think this is a matter of the options available, not my specific configuration. You can tell from the action step description that Account Number isn’t an available key. Bloomerang Support said this might be configurable by Zapier though 🤞

Search step description

 

But in case there’s a solution...

Here’s the overall view: 

Steps 5 and 9 are using name and email to search, but I’m wishing Account Number was possible.

(The zap uses paths because the Bloomerang CRM handles name fields for Individuals differently than Organizations.) 

 

The configuration for searching on Path A:

See? No option for mapping an Account Number field.

The configuration for searching on Path B:

Still no Account Number field.

 


Hi ​@aaron_s,

Thank you for sending over the screenshots. I appreciate it!

It looks like it’s not possible to use the Account Number as the search key. I’d recommend reaching out to our Support Team to create a feature request on your behalf.

You can reach our Support Team here: https://zapier.com/app/get-help

 


Hi there, ​@aaron_s 👋

You’re right, I don’t see any option to search for a constituent by their account number either. As Ken mentioned, I’d suggest contacting our Support Team to submit a new feature request for that functionality to be added. 

But in the meantime, I had a look at Bloomerang’s API documentation and there’s a /constituents/search endpoint so you may well be able to use a Webhooks action to perform a search via the account number. It looks like it would accept a text string for the search so you could potentially use the account number in that search parameter:

9398bbe3e165fe9271e9dbb38ff584b1.png

You’d need to set up the GET request as per Bloomerang’s API documentation, but I’d recommend also checking out our Send webhooks in Zaps guide for general guidance on how to set up that type of action.

Happy to lend a hand if you get stuck at any point on that—just let me know! 🙂


Reply