Zapier Integration

You can now integrate any tool your team uses with BrandChamp using our Zapier integration. 

We created our Zapier integration to help your team streamline your work and create an easier and faster way to manage your BrandChamps and program.

You have four different events to choose from when creating your Zaps:

• Applicant Applied
• BrandChamp Added
• BrandChamp Removed
• BrandChamp Updated 

With these four events, you can set up several triggers and connect BrandChamp to your team's most essential tools. 

Below is the step-by-step process of integrating your BrandChamp account with Zapier.

Step 1: Create a New Zap and Set Up Trigger

From your Zapier account, hit “Create a Zap” and create your Trigger.

Search for BrandChamp in the search bar and then select BrandChamp. 

Once you have selected BrandChamp, you can choose the event you want to trigger.

You have four options for events:

1. Applicant Applied: You can use this event to trigger when someone applies to join your program. The event includes answers to any application form questions.
2. BrandChamp Added: You can use this event to trigger when a new applicant is approved, or a previously removed applicant is restored. The event includes answers to any application form questions.
3. BrandChamp Removed: You can use this event to trigger when a BrandChamp is removed from your program or a previously approved applicant is rejected.
4. BrandChamp Updated: This event can trigger when BrandChamp details are updated.

You could create a Zap for each event above that corresponds to the BrandChamp's life cycle.

For this example, we will use the “Applicant Applied” event to track signups to the program.

Once you select your event, hit “Continue.”

Step Two: Add the Account ID and API Key

Next, Zapier will ask you to choose an account. Hit “Choose” and select “BrandChamp (1.0.0)” from the dropdown list.

After selecting BrandChamp from the list, connect your BrandChamp account. To do this, you must add the Account ID and API Key from your BrandChamp to your Zapier account. 

To get the Account ID and API Key, log into your BrandChamp account, go to Settings > Integrations, and hit “Connect” to get the Account ID and API Key. 

After you hit connect, a screen will appear with the Account ID and API Key. 

Once you have those two values, navigate back to Zapier and add those two keys when prompted. 

After adding these two values, you can test your trigger. 

Step Three: Perform a Test Trigger

Now, it’s time to test the trigger. 

A test trigger will show you that the API key is working correctly. For this example, you can see that the integration has been working since Zapier pulled our three most recent applicants from BrandChamp.

Hit “Test Trigger.” If everything works correctly, Zapier will pull an example applicant from your pool of applicants.  

Select the record you wish to use for the test and hit “Continue with Selected Record.” 

Once the test is done, it’s time to set up your action. 

Step 4: Set Up Your Action

Now that you have performed your test trigger, you can set up any further actions or integrations with BrandChamp to other apps you use. For this example, we will create an action using Slack.

Under the “Actions” section, search for Slack. 

Once selected, you can select the event you want to trigger in Slack. For this example, I will select “Send Channel Message” to get alerted via Slack whenever we get a new applicant to our program. 

Once you hit “Continue,” choose the appropriate Slack channel to receive your notifications.

Then, you will need to fill out all of the action fields. 

First, select a channel you want your message to go to. Then, customize the message you want to be sent to your Slack when there is a new applicant. See the image below for an example!

Customize the rest of the fields and then hit “Continue.”

Step 5: Test Your Action

Before you test your action, review that all fields are set up correctly, then hit “Test Action.”

If set up correctly, you should receive a Slack message from Zapier to the designated channel. 

If you are happy with the test, hit “Publish,” and you will create your new Zap! 

Tips & Tricks

Checking if a Property Has Changed

A “BrandChamp Updated” event will be fired when any supported property is updated. Sometimes though you need to filter events only if a particular property has changed. To enable this, the “BrandChamp Updated” event contains special “<PropertyName> updated?” properties. For example, the event contains the “Tags” property but also a “Tags updated?” boolean property.

Perform an Action When a BrandChamp Registers

If you want to perform a particular action the first time a BrandChamp registers, you should start with the “BrandChamp Updated” event. Note: not the “BrandChamp Added” event since that one represents when an applicant is approved, not when they later register. Then apply a filter as shown below which will only fire when the “Register” property has changed and the value is “true”, which only happens the first time they register:

Syncing Registered BrandChamps to External Systems

Add or Update BrandChamps

As noted above, to identity registered BrandChamps you always need to start with the “BrandChamp Updated” event, not the “BrandChamp Added” event. The example below shows how you can add or update registered BrandChamps in Klaviyo.

We add a filter to only consider BrandChamps where the “Registered” property is true.

After that we use the “Create or Update Profile” action that Klaviyo provides to either add or update a profile in a Klavioyo List. The key property to set in that action is the “Unique Id” property - set that to the BrandChamp’s “User ID” property as shown below. That will be used to discover if the profile exists or not. You can then match other fields like email and name or even set custom properties with the BrandChamp’s tags for example, and those will be used to keep the Klaviyo profile updated with the latest values from BrandChamp.

Removing BrandChamps

To remove any BrandChamp removed from your program from the Klaviyo list, add a separate Zap which starts with the "BrandChamp Removed" event and then add a Klaviyo "Remove Profile from List" action. This event needs the ID of the profile to remove, so click the "Add search step" button:

In the "Find a Profile" step, map the Email field to the Email property from the "BrandChamp Removed" event:

The final "Remove Profile from List" step should now have automatically mapped the "Profile ID" field to the ID of the profile looked up in the second step:

When published this Zap will look up the Klaviyo profile ID by the removed BrandChamp's email and then call Klaviyo to remove that profile from the selected list.