- Home
- Resources
- Integrations
- Perfleek
Perfleek Zapier integrationAutomate Perfleek with Zapier.
The Perfleek Zapier integration gives you 1 trigger, 0 actions and 0 searches. One thing goes out of this real estate CRM: each new lead. Here is how that trigger fires, where you can send the lead, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Perfleek Zapier integration actually does
The Perfleek Zapier integration takes the leads that arrive in Perfleek, a CRM built for real estate agents and brokers, and passes them to your other tools without code. It works in one direction only: Perfleek starts the Zap, and another app receives the lead.
Three results come up with a single trigger. An alert to the agent: New Leads posts each fresh buyer or seller inquiry in the team chat, so nobody has to refresh the CRM. A shared record: the same trigger adds a row to a spreadsheet the broker uses for reporting outside Perfleek. A first email: the lead goes to an email tool that sends the welcome message the agency already wrote.
Now the limits, and they are wide. Perfleek has no action in Zapier, so nothing can be written into Perfleek: a lead from a property portal or a website form cannot be pushed in through Zapier. There is no search either, and no trigger on an updated lead or a changed status. And the only trigger is polled: Zapier checks Perfleek on a timer, every 15 minutes on the Free plan. A Perfleek Zap is therefore a relay for new leads, not a two-way sync between Perfleek and your other tools.
To learn the editor step by step, there is the Zapier training.
Zapier words, in plain English
Seven terms come back on this page. Here they are once, without jargon.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger's event happens.
- Trigger
- The event that starts a Zap. With Perfleek there is just one: a new lead added. Once the Zap is on, Zapier waits for it.
- Action
- The step that does the work after the Zap starts. Perfleek has none, so every action in these Zaps belongs to another app.
- Task
- The unit Zapier bills: one action that completed successfully. The allowance on your plan is a count of those, and nothing else.
- Polling vs instant trigger
- Polling: Zapier asks the app for new items at a fixed interval. Instant: the app tells Zapier itself. New Leads is polled.
- Filter
- A step that lets the Zap go on only when the lead meets the condition you set, and stops it there otherwise.
- Connection
- Your Perfleek account linked to Zapier once, then reused by every Zap that starts on a Perfleek lead.
What a Perfleek Zap really costs
The Perfleek trigger costs nothing, and neither does Zapier checking Perfleek for new leads, however often it looks. A task is counted only when an action in the other app goes through.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, 2 steps per Zap
- Paid plan required for the appNo
A failed action is not counted, so a broken step does not drain the plan. A Zap that posts the lead in a chat uses one task per lead; add a spreadsheet row and it uses two. Perfleek is not reserved for paid plans, so it works on Free: 100 tasks a month and unlimited Zaps, but each Zap stops at two steps, one trigger and one action. A second action or a filter makes it a multi-step Zap, which needs a paid plan.
Connect your Perfleek account in 3 steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. You need a Perfleek account, plus read access on any leads you do not own yourself and want a Zap to see.
- 02
Pick Perfleek
In the dialog, type Perfleek and pick it from the results. Then click Add connection: Zapier opens a new tab where the Perfleek side of the link takes place.
- 03
Sign in and grant access
Sign in to Perfleek in that tab and grant Zapier access to the account. The connection is saved, and any Zap that starts on New Leads offers it in a list instead of asking again.
Your first Zap: each new lead logged and announced
GoalEach new Perfleek lead lands in the agency's spreadsheet and gets announced in the team chat.
- 01
Pick the trigger
In the Build stage, choose Perfleek as the app that starts the Zap and New Leads as the event. Select the connection you made earlier.
- 02
Test it on a real lead
Run the trigger test. Zapier brings back the three most recent leads of the connected account, so you map the next steps on a real inquiry rather than an empty shell.
- 03
Add the spreadsheet row
Add your spreadsheet app as the first action and map what the lead carries into its columns. This step alone would already fit the Free plan.
- 04
Add the chat message
Add the team chat app below it and write the message, with the lead's details mapped in. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each action once and read what came back before going on. When both look right, click Publish to switch the Zap on. Leads added from then on start it.
The Perfleek trigger
1 event starts a Zap when something happens in Perfleek. Zapier checks for them at the interval your plan allows.
New Leads
Polling triggerIn Zapier“Triggers when there's a new lead added.”
Starts a Zap for every lead added in Perfleek and hands that lead to the steps that follow. It is the only door out of Perfleek in Zapier, so every Perfleek Zap begins here.
When a Perfleek Zap breaks
Zapier attaches no help article to Perfleek, so the problems below are Zapier's general limits, seen through this app.
With a single polled trigger, they all come from timing and from what the trigger sees. For a method when a Zap stalls, see Zapier troubleshooting.
Existing leads never come through
A Zap only reacts to what is added after you publish it. The leads already in Perfleek stay there; moving that backlog is a separate job.Leads arrive in batches
Since New Leads is polled, a lead added right after a check waits for the next one. On Free that can mean up to 15 minutes before the agent hears about it.Bulk imports held back
Import a big list of contacts into Perfleek at once and the next check returns a huge pile. Zapier's flood protection can hold it back instead of running the Zap per lead.Duplicates are filtered out
Zapier keeps track of the leads it has already seen, so the same lead never starts the Zap twice. A lead that looks skipped was probably not new to Zapier.
Need help automating Perfleek with Zapier?
A person reads every message.



