How to use Brokerkit with Zapier
Brokerkit's native Zapier app lets you connect Brokerkit with the other tools your team already uses. You can use Zapier to create or update Brokerkit contacts, add contacts to campaigns, and build follow-up workflows without copying information by hand.
This article covers the native Zapier app, which uses a Brokerkit authorization screen inside Zapier. If you are using the older webhook or direct API-key setup, see Integrating with Zapier for importing leads or agents.
Before you start
You will need:
- A Brokerkit account with access to the team you want to connect
- Admin access if you are connecting Zapier for the team
- A Zapier account
- A clear source app, such as a lead form, recruiting platform, spreadsheet, or scheduling tool
Start from Brokerkit
- In Brokerkit, open Account Settings.
- Select the Integrations tab.
- In the Zapier Integration section, select Set up on Zapier.
- You can also start from one of the popular templates, such as Calendly, WizeHire, Facebook Lead Ads, Google Forms, or Eventbrite.

Choose Brokerkit in Zapier
Zapier will open the Brokerkit integrations page. From there, you can connect Brokerkit to another app or pick one of the suggested app pairings.


When creating a Zap manually, search for Brokerkit in Zapier's app selector.

Connect Brokerkit to Zapier
- In Zapier, select Brokerkit as the app for your Zap step.
- When Zapier asks you to connect Brokerkit, select Connect.
- Brokerkit will ask you to authorize Zapier.
- Review the access Zapier is requesting, then select Authorize.


The authorization screen may include permissions for reading contacts, creating and updating contacts, starting and stopping campaigns, and sending emails to contacts. These permissions let Zapier perform the actions you configure in your Zaps.
Create or update contacts in Brokerkit
Use Create or Update Contact when another app collects a new lead, recruit, agent, candidate, or contact that should appear in Brokerkit.
During setup, map the fields from your source app into Brokerkit fields. Common fields include:
- Product, such as Recruiting or Retention
- First name and last name
- Email address
- Lead source
- Phone numbers
- Status
- Owner or team member
- Production label
- Notes or other context from the source app
Brokerkit uses matching logic to update existing contacts when possible instead of creating unnecessary duplicates. Email is especially important because it helps identify the right contact.

Use Brokerkit dropdowns in Zapier
Brokerkit sends Zapier the current options from your account for fields like product, lead source, lead status, team members, and production labels. That means your Zap setup can use the same values your team already uses in Brokerkit.
If an option is missing, update it in Brokerkit first, then refresh the field in Zapier.
Add contacts to campaigns
You can also use Zapier to add a Brokerkit contact to a campaign. After mapping the required fields, use Zapier's test step to confirm the campaign subscription is sent to Brokerkit.

Build follow-up workflows
After contacts are created or updated, you can use Brokerkit and Zapier together to keep follow-up moving. Depending on the Zap you build, you may be able to:
- Add or update a contact from another app
- Keep key contact details current
- Add contacts to the right lead source or status
- Add contacts to a campaign
- Send relevant updates back into Brokerkit activity history
Feed Signed or Onboarding contacts into a Zap
For an onboarding handoff, Signed in Recruiting and Onboarding in Retention use the same stored onboarding status. Create a dedicated Brokerkit saved search for that status and use the Zapier saved-search polling trigger to find matching contacts in created-at order. This is a polling workflow, not a direct stage-change event. The live fields available to your Zap must be confirmed in Zapier during setup.
Tips for a clean setup
- Always map email when your source app provides it.
- Use consistent lead sources so your team can filter and report on imported contacts.
- Test with one sample contact before turning on a Zap for live traffic.
- Check for duplicate contacts after your first few runs.
- Name your Zap clearly so your team knows what system is feeding Brokerkit.
Troubleshooting
I do not see the Brokerkit option I need in Zapier
Refresh the field in Zapier. If the option still does not appear, confirm that the value exists in Brokerkit and that your connected user has access to it.
Zapier created a duplicate contact
Check whether the source app sent an email address and whether the existing Brokerkit contact has the same email. If the contact was created with incomplete data, merge duplicates in Brokerkit and update your Zap field mapping.
My Zap test worked, but live records are not appearing
Check the Zap run history in Zapier first. If Zapier shows the step failed, review the error and field mapping. If Zapier shows the step succeeded but the contact is missing in Brokerkit, contact Brokerkit Support with the Zap run details.
Template account requirements
Brokerkit includes templates for common lead sources. Each template may have different account requirements in Zapier or in the source app:
- Calendly to Brokerkit requires a Calendly Standard or higher plan. A paid Zapier plan is not required if the Zap only has two steps.
- WizeHire to Brokerkit requires a paid WizeHire account and API key. A paid Zapier plan is not required if the Zap only has two steps.
- Facebook Lead Ads to Brokerkit requires a paid Zapier plan because Facebook Lead Ads is a premium Zapier app. You also need the right Facebook Page and Lead Ads permissions.
- Google Forms to Brokerkit does not require a paid Google Forms plan. A paid Zapier plan is not required if the Zap only has two steps.
- Eventbrite to Brokerkit does not require a paid Eventbrite plan for free events. Paid-ticket events may have Eventbrite fees. A paid Zapier plan is not required if the Zap only has two steps.