Zapier Integration

Brushfire offers several triggers through the web automation service, Zapier. A web automation service is one that connects two pieces of software through triggers and actions. A trigger is when something happens in one software and an action is what should be done in the other software because the trigger happened.

Currently, Brushfire only supports triggers. This means that when something happens in Brushfire, another software can be notified of the change. For example, every time an attendee registers for an event, you might want Zapier to respond to that trigger and update your CRM/ChMS accordingly. Or perhaps you want to receive a text or Slack notification every time an order is placed. The possibilities are almost endless!

To configure Zapier, you don't need to do anything in Brushfire, but you will need an API Key. To request an API Key, please visit

Please Note: The Brushfire Zaps are currently in an invite-only private beta. To make Zaps using Brushfire use this link: 

  1. Once you have your API Key, log into your Zapier account and click "Make a Zap."
  2. You'll need to select Brushfire as your Trigger app.

  3. Brushfire offers several triggers of different things that happen in the system. Select the one you are interested in reacting to.
  4. This is where you'll need your API Key. Collect "Connect a New Account" and a popup will open where you can type in your API Key to authenticate Zapier to Brushfire. 

    ZapInstructions3.png ZapInstructions4.png

  5. For most triggers, you'll have an option to select one or more events. If you do not select any events, then the trigger will occur for all events in the clients connected to your API Key. But if you just want to receive notifications for specific event(s), select them here.


  6. This next part is optional, but highly recommended. To verify that Zapier is connected properly AND to get a list of fields you can map to your action, you'll need to pull in sample data from Brushfire. Clicking the "Pull In Samples" button will poll Brushfire and return the newest data related to the trigger you're creating. If you selected multiple events in the previous step, Brushfire will only return data for the first event in the list. If each of your events use different attendee or buyer field options we recommend creating a new Zap for each unique event, so you'll have full access to use each field in your Zaps.


  7. Once Brushfire has responded with your sample data you can explore the data format we returned or click the "Continue" button to proceed. 

  8. You're done! Well, you're at least done with the Brushfire/trigger portion. Now you'll need to go through similar steps with the app you select for your action to get the Brushfire data into whatever software service you're using as your action.


Please note, Zaps deal with live data, so they are good for responding to live changes. If you have existing records that you need to move into a service, we recommend you export the CSV data for your events and import that into your system and then set up the Zap for changes going forward. For information about how to get data out of Brushfire, check out this article and for information on using Zapier to import spreadsheet data, check out this page.