Zapier integration
Connect BlueSales to the apps you already use. A new lead comes in and a Blue calls them. A call ends and the transcript lands in your CRM. No code, no copying between tabs.

In practice
Two Zaps close the loop. The first turns a new enquiry into a lead and has a Blue call it. The second takes the finished call — summary, transcript, outcome — and puts it where your team works.
Every BlueSales step shown here is a real trigger, action or search in the integration.
Call every new enquiry
Web form · New submission
→ Jordan Reyes · +1 415 555 0134
BlueSales · Find or Create Lead
→ no match · added to Spring Roofing
BlueSales · Place Outbound Call
→ Riley is dialling +1 415 555 0134
Send every call to the team
BlueSales · New Call
→ Jordan Reyes · 3m 12s · successful
CRM · Update contact
→ AI summary saved to Jordan Reyes
Team chat · Send channel message
→ posted to #sales with the transcript
What’s included
Everything a workflow needs from your phone agents — hear about calls as they finish, feed leads to a campaign, and dial someone the moment it matters.
Triggers
Start a Zap when something happens in BlueSales.
A Blue finishes a call, inbound or outbound. Carries the transcript, AI summary, duration, outcome and recording link. Filter by Blue or by outcome.
A lead is added to the account — from a Zap, a CSV import or the dashboard. Filter by lead list.
A new Blue is created. Filter by type and role — useful for onboarding client accounts.
Actions
Have BlueSales do something when another app says so.
Makes a Blue dial a real number, right now. Uses call minutes; the result arrives through New Call.
Adds a lead to a lead list so an outbound Blue can call it.
Changes a lead. Fields you leave blank keep their current value.
Creates an empty list for a new outbound campaign.
Adds a catalogue entry — the description and offer an outbound Blue actually pitches.
Searches
Look records up mid-Zap instead of hard-coding IDs.
By phone number or email address.
Finds the lead, or creates it when there is no match — so a form or CRM never adds the same person twice.
The most recent call with a contact’s name or number, with transcript and summary. Scope it to a Blue and a time period.
By name. An exact match wins.
By name, gender, accent or engine type.
Recipes
Each of these takes a few minutes to set up and removes a job someone was doing by hand.
When
A form, ad or booking page captures a lead
Then
Find or Create Lead, then Place Outbound Call. A Blue rings them while they still remember filling it in.
When
New Call
Then
Write the AI summary and transcript onto the contact, and log the outcome as an activity.
When
New Call, successful calls only
Then
Post the summary and recording link to the channel your salespeople actually read.
When
A new row in a sheet
Then
Create Lead on the right list. Your outbound Blue works through it on its calling schedule.
When
A deal changes stage in your CRM
Then
Find Lead by phone number, then Update Lead — so the Blue never calls someone who already bought.
When
New Blue
Then
Open a project, add a row to the client tracker, and let the account manager know it is live.
Setup
One API key is the whole connection. Nothing to install, no webhook URLs to paste.
In BlueSales, go to Dashboard → API → API Keys and create a key. Tick the permissions for what your Zaps will do.
Add BlueSales as a step in a Zap and paste the key when asked. The connection shows your account email so you can tell accounts apart.
Blues, lead lists and business profiles appear as dropdowns — no IDs to copy across. Test the step and turn the Zap on.
Control
A Zap runs without anyone watching. That is only fine when it can do exactly what you meant and nothing more.
A Zap can only do what its key allows. Give a reporting Zap a read-only key and it cannot place a call, however it is set up.
Place Outbound Call is labelled as dialling a live number and using call minutes, and it refuses a Blue with no phone number attached before anything is dialled.
Find or Create Lead matches on phone number or email first, so a form that fires twice does not mean a person gets called twice.
A rejected key, a missing permission or an undialable number comes back as a sentence that names the problem — not a status code.
Anything Zapier connects to — CRMs, form builders, spreadsheets, team chat, ad platforms, booking tools. BlueSales supplies the triggers, actions and searches on this page; Zapier handles the other side.
The BlueSales triggers are polling triggers: Zapier checks for new calls, leads and Blues on its own schedule, which depends on your Zapier plan and can be up to 15 minutes. Actions such as Place Outbound Call run the moment the Zap reaches them.
Not from the same record. Zapier de-duplicates triggers on the record ID, and Find or Create Lead checks for an existing lead by phone number or email before adding one.
Leads added with Create Lead are called by your outbound Blue on its own calling schedule. Place Outbound Call is different — it dials immediately, so put a filter or schedule step in front of it if the Zap can run out of hours.
Nothing on top of your plan. The Zapier integration uses the BlueSales API, which is included with the Business and Agency plans. Calls placed through a Zap use call minutes like any other call, and Zapier’s own plan limits apply to how many tasks your Zaps run.
Included with the Business and Agency plans. One API key, and every Zap can reach your phone line.
Get started free