- Home
- Resources
- Integrations
- PeakIDX
PeakIDX Zapier integrationAutomate PeakIDX with Zapier.
PeakIDX Zapier integration: 1 trigger, 1 action, 0 searches. PeakIDX gives real estate agents and brokers a site with listing data. On Zapier, New Lead hands each new lead to your other tools, and Create Lead brings leads from elsewhere into your PeakIDX site.
Verified Trustpilot reviews · AI, automation & growth agency
What the PeakIDX Zapier integration does for an agent
The PeakIDX Zapier integration moves leads in and out of the site you run on PeakIDX. A Zap (an automation built from one trigger and one or more actions) can start when a new lead shows up in PeakIDX, or it can push a lead collected somewhere else into your PeakIDX site. Two operations, both about leads.
Leads in the tool you actually work from. New Lead can copy each lead into a sheet, a CRM or an email list, so a buyer who reached you through your site does not wait in a dashboard nobody opens.
One lead list instead of three. Create Lead imports a lead captured by another channel, an open-house sign-in form or a referral partner, into your PeakIDX site, where the rest of your leads already sit.
A follow-up that starts on its own. Paired with an email or a messaging app, New Lead can start the first contact with a new prospect without you copying an address by hand.
What Zapier does not do here: it cannot look up a lead (there is no search), update one, or touch listings. It also does not see a lead the moment it is created: New Lead is checked on a timer that depends on your plan. Everything else stays in PeakIDX. To compare Zapier with other platforms, see Make vs Zapier or n8n vs Zapier.
Zapier words, in plain English
Seven terms come back on every Zapier screen. One line each, and the rest of the page reads easily.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts a Zap, here a new lead in PeakIDX. Once the Zap is on, Zapier keeps watching for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something, such as importing a lead into PeakIDX.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts those and nothing else.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen. New Lead works this way.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your PeakIDX account linked to Zapier once, then reused by every Zap step that touches PeakIDX.
What a PeakIDX Zap costs, and how fast it runs
PeakIDX is not reserved for paid plans: it works on the free plan.
- New Lead triggerNever costs a task
- Successful actionCounted against your plan
- Failed actionNot counted
- Free plan100 tasks a month, two-step Zaps
The New Lead trigger costs nothing, however often Zapier checks for new leads. Each action that succeeds is counted, and one that fails is not. The free plan gives 100 tasks a month, but only two-step Zaps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Speed depends on the plan, because New Lead is a polling trigger: see the grid below for each plan.
Connect PeakIDX in three steps
- 01
Open Apps and add a connection
In Zapier, open the Apps page and click + Add connection. A dialog with a search box appears. You need a PeakIDX account, plus access to any site or leads you do not own but want the Zap to touch.
- 02
Pick PeakIDX and sign in
Search for PeakIDX, select it, then click Add connection. A new tab opens on PeakIDX: sign in with the account that runs the site whose leads you want, not a colleague's.
- 03
Grant access
PeakIDX asks you to let Zapier use the account. Accept. The connection is then reused by every PeakIDX step in every Zap, so you do it once per account.
Your first Zap: log qualified PeakIDX leads in a sheet
GoalEach new PeakIDX lead that meets your condition gets a row in a Google Sheets file the team works from.
- 01
Build: pick the trigger
Start a new Zap, choose PeakIDX as the app and New Lead as the event, then select your PeakIDX connection. The trigger needs no other setting before the test.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real lead and see which values it carries.
- 03
Add a filter
From the plus icon, add a Filter step and set the field, the rule and the value. A text rule on a number never passes, so pick the right type. The filter makes the Zap multi-step, which needs a paid plan.
- 04
Add the action
Add Google Sheets, pick the file and map the lead values from the test into the columns. Test the step once and read what came back before going on.
- 05
Publish
When the test row looks right, click Publish to switch the Zap on. From then on, new leads go through at the interval of your plan.
PeakIDX trigger
1 event starts a Zap when something happens in PeakIDX. Zapier checks for them at the interval your plan allows.
New Lead
Polling triggerIn Zapier“Triggers when a new lead is created.”
Starts a Zap for each new lead in your PeakIDX account, which is how a buyer or seller who reached your site ends up in the tools where you plan calls and follow-ups.
PeakIDX action
PeakIDX gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Lead
ActionIn Zapier“Imports a lead into the PeakIDX Site”
Imports a lead collected by another app into your PeakIDX site, so it sits with the leads your site captured on its own.
When a PeakIDX Zap breaks
Zapier ties no help article to PeakIDX, so the cases below are the general limits that apply to any Zap built on it.
None of them shows up as an error in PeakIDX. They show up as a lead missing from your sheet, a lead arriving later than you expected, or a task count that climbs too fast. When you are stuck, start from the Zapier troubleshooting page.
The lead loop
New Lead followed by Create Lead on the same account writes where the trigger watches. Each import becomes a new lead, the Zap fires again and burns tasks.No catch-up on the past
A Zap only reacts to leads created after you switch it on. Leads already in PeakIDX never go through it; moving them is a separate job.Flood protection after a bulk import
After a bulk import or a migration, New Lead returns a huge batch and Zapier can hold it back instead of running it.Each lead counted once
Zapier remembers which leads it has already seen on New Lead, so the same lead does not start the Zap twice.
Need help automating PeakIDX with Zapier?
A person reads every message.


