- Home
- Resources
- Integrations
- Salesflare
Salesflare Zapier integrationAutomate Salesflare with Zapier.
The Salesflare Zapier integration gives you 6 triggers, 13 actions and 7 searches to push new deals, contacts and tasks out of your CRM, or feed it from your other tools, without retyping a single record by hand, even on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Salesflare Zapier integration actually does for a sales team
Zapier sits between Salesflare and your other apps. When something new shows up in the CRM (an account, a contact, a deal, a task), it can start an automation. The other way round, it can write into Salesflare: create a contact, log a call, move an opportunity forward, all without you opening the CRM.
Three results you can expect once it runs. No inbound lead left without a next step: New Contact fires, Create Task puts a call on someone's list. A CRM that fills itself from your forms and calendars: Create Contact, Create Meeting and Create Call log what happened elsewhere, so the account history in Salesflare stays complete. Deals that update from the tools where the work really happens: Update Opportunity, paired with the search Find Opportunity, changes a deal you never had to open.
Now the part the app directory skips. All six Salesflare triggers are polling triggers: none of them is instant, so a free plan always waits for the next check. Every trigger starts with the word New. There is no trigger for a deal that changes stage or a contact that gets edited, only for items that appear. And there is no delete action at all: Zapier can create, update, attach and remove a contact from a workflow, but it cannot erase anything in Salesflare.
If you are weighing tools before you build, the Salesflare Make integration covers the same CRM from the Make side, and our Make vs Zapier comparison lays the two models side by side, criterion by criterion.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English, once.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every single time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, in Salesflare or in another app.
- Task
- The unit Zapier bills. One task equals one action your Zap completed successfully, and your plan counts how many of those you use.
- Polling vs instant
- A polling trigger is checked on a timer, Zapier asks the app what is new. An instant trigger is pushed by the app itself, the moment it happens.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and quietly stops it in every other case.
- Search step
- A step that looks up something already in an app, like an existing account, so the steps after it can reuse what it found.
What a Salesflare Zap really costs you
Salesflare is not a premium app on Zapier, so it works from the free plan. The real constraint is elsewhere.
- Free plan100 tasks per month
- Free plan Zap size2 steps: 1 trigger, 1 action
- Salesflare premium app?No
- Billed per runEach successful action
The trigger never costs a task, and neither does Zapier checking Salesflare for new items, however often it looks. You pay per action that succeeds: a Zap with three actions eats three tasks per run, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter, a search like Find Contact or a second action and the Zap becomes multi-step, which means a paid plan.
Connect Salesflare to Zapier in three steps
- 01
Open your Apps page
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Salesflare account linked to Zapier once, then reused by every step that touches Salesflare.
- 02
Pick Salesflare and confirm
Type Salesflare in the search box of the dialog, select it, then click Add connection. A new tab opens on the Salesflare side. You need an existing Salesflare account here, there is nothing to create from Zapier.
- 03
Sign in and grant access
Log in to Salesflare in that tab and allow Zapier to reach the account. If your Zaps will touch accounts or deals you do not own, make sure your Salesflare user can read and write them first.
Your first Zap: a call task for every qualified new contact
GoalEach new contact in Salesflare that matches your condition gets a call task.
- 01
Build: pick the trigger
Create a new Zap, choose Salesflare as the app and
New Contactas the event. Select the connection you just made. This is a polling trigger: on the free plan Zapier checks every 15 minutes. - 02
Test the trigger
Run the test. Zapier pulls the three most recent contacts from your Salesflare account, so pick a real one. Every field you map later comes from that sample.
- 03
Add the filter
Click the plus icon, add Filter, then set the field to look at, the rule and the value. Mind the rule type: a text rule on a number never passes. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add Create Task
Add a Salesflare action, pick
Create Taskand fill the Description field, which is required. Map the contact's name into it so the rep knows who to call without searching. - 05
Test, then publish
Test the action once and check the task in Salesflare. Then click Publish to switch the Zap on. From now on, only contacts created after that moment go through.
The 6 Salesflare triggers
6 events start a Zap when something happens in Salesflare. Zapier checks for them at the interval your plan allows.
New Account
Polling triggerIn Zapier“Triggers when a new account has been added.”
Starts your Zap each time a company record appears in Salesflare. It is the natural starting point for anything that should happen once per client company rather than once per person.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is added.”
Watches your Salesflare contact list and hands each fresh person to the Zap. Salesflare captures contacts automatically, so on a paid plan a filter behind it lets through only the people that matter to the Zap.
New Opportunity
Polling triggerIn Zapier“Triggers when a new opportunity has arrived.”
Fires when a deal lands in one of your Salesflare pipelines. This is the trigger to use when the moment that matters is the start of a sale, not the arrival of a new name. It only reacts to new deals: a deal moving from one stage to the next does not start it.
New Task
Polling triggerIn Zapier“Triggers when a new task is added.”
Picks up every to-do added in Salesflare. Useful when tasks need to live somewhere else too, like a personal to-do app or a shared board that the rest of the company actually reads.
New Workflow Event
Polling triggerIn Zapier“Triggers when an event happens to your workflow.”
Reports what happens inside one of your Salesflare workflows, the automated sequences you set up in the CRM, where a step can be something like sending an email. Each event on that workflow starts the Zap, which lets you react outside Salesflare to how a sequence is going.
New Workflow Step Event
Polling triggerIn Zapier“Triggers when an event happens to your workflow step.”
Narrower than the previous one: it watches a single step of a Salesflare workflow and a single kind of event on that step. You choose the workflow, the step and the event, and the Zap only moves when that exact combination happens.
The 13 Salesflare actions
Salesflare gives you 13 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Contact to Account
ActionIn Zapier“Add a contact to an account.”
Links a person who already exists in Salesflare to a company that already exists too. Both IDs are required, so this action usually follows two searches, or a trigger and one search.
Add User to Account
ActionIn Zapier“Add a user to an account.”
Assigns one of your own Salesflare users to an account in Salesflare. The account ID and the user are both required, and Find User gets you the second one.
Create Account
ActionIn Zapier“Creates a new account.”
Adds a company to Salesflare from data that arrived in another app. One setting matters more than the rest: you can tell it to reuse an existing account that has the same name rather than make a second one.
Create Call
ActionIn Zapier“Creates a new call.”
Logs a phone call in Salesflare after the fact. The Start Date field is required, so the step that feeds it must carry a date and time for the call, typically your phone or dialer tool.
Create Contact
ActionIn Zapier“Creates a new contact.”
Writes a new person into your Salesflare contacts. It is the simplest way to make sure people who reached you outside email, through a webinar or a chat widget, still end up in the CRM.
Create Meeting
ActionIn Zapier“Creates a new meeting.”
Records a meeting in Salesflare, with a required Start Date. Handy when meetings are booked in a tool the CRM does not watch, so the account history still shows that the meeting took place.
Create Internal Note
ActionIn Zapier“Creates a new internal note.”
Pins an internal note to an account. It needs the account ID and the note body, both required. Notes are where context from support tickets or onboarding calls stops getting lost.
Create Opportunity
ActionIn Zapier“Creates a new opportunity.”
Opens a deal in Salesflare without anyone clicking through the pipeline. Pair it with a qualifying step upstream so only serious requests become opportunities and your forecast does not fill with noise.
Create Task
ActionIn Zapier“Creates a new task.”
Puts a to-do on a Salesflare task list. The Description field is required, so write the action right there: who to call, and why. It is the action that turns any signal from another tool into a concrete next step for a rep.
Remove Contact From Workflow
ActionIn Zapier“Remove a contact from a certain workflow”
Takes a person out of a running Salesflare workflow. Three things are required: the workflow, the contact ID and whether the person met the goal on the way out.
Update Account
ActionIn Zapier“Update an existing account.”
Changes an account that is already in Salesflare. It needs the account ID, which usually comes from Find Account placed just before. Use it to keep company records in step with your billing or product data.
Update Contact
ActionIn Zapier“Updates an existing contact.”
Edits an existing person in Salesflare, identified by contact ID. Pair it with Find Contact when the source app only knows the email address, not the CRM's internal ID.
Update Opportunity
ActionIn Zapier“Update an existing opportunity.”
Moves or edits a deal that is already open. The opportunity ID is required; Find Opportunity gets it for you. This is the only way Zapier can push a deal forward, since no trigger reacts to stage changes.
The 7 Salesflare searches
7 search steps look for data that already exists in Salesflare, so a later step can use it.
A search step finds a record that already exists so the next step can use its ID. In the action list, searches sit at the bottom under the SEARCH heading. Some action fields also offer + Add search step, which inserts the right search and wires its result for you. How close a match must be is decided by Salesflare, not by Zapier. Three settings decide what happens next.
Find Account
SearchFind or createIn Zapier“Find an account.”
Looks up a company in Salesflare and returns its ID for Update Account, Create Internal Note or Add Contact to Account. The editor also shows Find or Create Account: same search, with the create box ticked, so a missing company gets made instead of stopping the Zap.
Find Contact
SearchFind or createIn Zapier“Find a contact.”
Finds a person in your contacts and hands their ID on. Its find-or-create twin, Find or Create Contact, is the cleanest way to feed Salesflare from forms without piling up duplicates: it is the same search with the create box ticked.
Find Opportunity
SearchIn Zapier“Find an opportunity.”
Locates an existing deal so Update Opportunity knows which one to change. Since no trigger reacts to deal changes, this search is the starting block of every deal-update Zap.
Find Person
SearchIn Zapier“Find a person.”
Returns a person record from Salesflare. Test it next to Find Contact on a real sample before you pick one: the test shows exactly what each of the two hands on to the next step.
Find Pipeline Stage
SearchIn Zapier“Find a pipeline stage.”
Retrieves a stage from your Salesflare pipelines. Use it when a deal must land in, or move to, a specific stage and the source app only knows that stage by name.
Find User
SearchIn Zapier“Find a user.”
Finds one of the Salesflare users on your team. It is the missing piece for Add User to Account, which needs a user, and for routing work to a named rep.
Find Workflow
SearchIn Zapier“Finds a Workflow”
Returns a Salesflare workflow from its name, which is required. It saves you from hard-coding a workflow choice when the name comes from another app, for example before Remove Contact From Workflow.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that needed it. Switch it on and the Zap carries on with nothing.
- Create X if it doesn't exist yet?Ticking it turns the search into find-or-create: the setting above disappears and the step asks for the fields needed to create the missing record.
- If multiple search results are found?Three ways out when several records match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When a Salesflare Zap breaks
Zapier attaches no help article of its own to Salesflare, so the failures you will meet are the general ones.
Most broken Salesflare Zaps come from four situations. They are worth knowing before you publish. When one shows up anyway, the Zapier troubleshooting guide walks through the fix.
The Zap ignores your existing records
A Zap only reacts to what happens after you publish it. Your current accounts, contacts and deals are never sent through. Moving that backlog is a separate job.A loop that burns your tasks
A Zap that writes into the place its own trigger watches restarts itself. New Contact plus Create Contact in the same Salesflare account is the classic case, and 100 free tasks go fast.A bulk import gets held back
After a bulk import or a migration, a trigger suddenly returns a huge batch. Zapier's flood protection can hold it back rather than run every record.Why a record is not processed twice
On polling triggers Zapier remembers what it has already seen, so the same contact or deal does not start the Zap a second time.
Need help automating Salesflare with Zapier?
A person reads every message.



