Resources · Zapier integration

Planpoint Zapier integrationAutomate Planpoint with Zapier.

Planpoint Zapier integration: 12 triggers, 9 actions, 0 searches. Zapier can hear about new leads, signups and listing changes, then create or update projects, floors and units for you. Every trigger is checked on a timer, so your plan sets the pace.

See the 21 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Planpoint Zapier integration does for a developer

Planpoint shows a real estate project as interactive floor plans that you embed on your own site, with each unit and its availability. Zapier plugs it into the rest of your sales stack: twelve events in Planpoint can start a Zap, and nine actions let a Zap build or adjust projects, floors, groups and units without anyone opening the dashboard.

Leads in your CRM, not in an inbox. New Lead and New Portal Signup pick up the people who register on your viewer, across every project if you leave the project setting empty, and hand them to your sales tool.

Inventory that follows your pricing sheet. Update Unit/Space and Create Unit/Space let a Zap keep units in line with the spreadsheet or the property tool your team actually maintains.

A change log for every listing. Updated Unit/Space, Updated Floor and Updated Project report edits, so a sales manager can see what moved on the plan without checking it by hand.

What Zapier does not do with Planpoint: it has no search step, so a Zap cannot look up an existing unit by name; it has to receive it from a trigger or be told which one. And no trigger is instant: every check waits for your plan's interval. If those two points matter for your project, the n8n vs Zapier comparison is a useful next read.

Vocabulary

Zapier words you will meet on this page

Seven terms carry the rest of the page. One line each.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event that starts the Zap, such as a new lead or an edited unit. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that creates, updates or deletes something, in Planpoint or elsewhere.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks Planpoint for new items at a fixed interval and keeps only what it has not seen.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your Planpoint account linked to Zapier once, then reused by every step of every Zap that talks to Planpoint.
Cost

What a Planpoint Zap costs you

Checking Planpoint for new leads or edits never costs a task, however often Zapier looks. You pay for each action that succeeds; a failed action is not billed.

  • Trigger check0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Paid plan required for this appNo

The free plan gives 100 tasks a month and two-step Zaps: one trigger, one action. A second action or a filter makes the Zap multi-step, which needs a paid plan. Planpoint is open to the free plan. Since all twelve triggers are polling ones, the interval below is the delay you live with: up to 15 minutes on free. A few apps and actions take more than one task when they complete, so check a step before you budget on it. On paid plans you can change how often a check runs.

Connect

Connect your Planpoint account in 3 steps

  1. 01

    Start from the Apps page

    Open the Apps page of your Zapier account and click + Add connection. Type Planpoint in the search box of the dialog and select it. Use the Zapier account where your Planpoint Zaps will live.

  2. 02

    Sign in to Planpoint

    Click Add connection. Planpoint opens in a new tab: sign in with the account that holds your projects. If a colleague owns the project, ask for access first, or your Zaps will not reach it.

  3. 03

    Allow Zapier in

    Grant Zapier access to the account. The connection is now listed on your Apps page, and every Planpoint step you add later offers it in a menu instead of asking you to sign in again.

First Zap

Your first Zap: from viewer lead to sales follow-up

GoalEach new lead from your Planpoint viewer becomes a CRM contact, then gets a welcome email.

  1. 01

    Choose the trigger

    In the editor, pick Planpoint as the app that starts the Zap and New Lead as the event. Leave the project setting empty to catch leads from all your projects.

  2. 02

    Test with real leads

    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 person rather than a placeholder.

  3. 03

    Create the contact

    Add your CRM as the next app and map the lead into the contact. On the free plan, this single action is where the Zap stops.

  4. 04

    Send the welcome email

    Add an email step as a second action. Two actions make the Zap multi-step, so this part needs a paid plan. Stay on the CRM step alone if you keep the free plan.

  5. 05

    Test, then publish

    Test every step and read what came back. Click Publish to switch the Zap on. From then on, Zapier checks for new leads at your plan's interval.

Triggers

The 12 Planpoint triggers

12 events start a Zap when something happens in Planpoint. Zapier checks for them at the interval your plan allows.

1

New Floor

Polling trigger

In Zapier“Triggers when a new floor is created.”

Reports each floor added to a project, so a new level in a building shows up outside Planpoint without anyone announcing it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
open a checklist in your project tool for the floor plan visuals and unit data still to add to the new level.
Watch out
you must pick the project to watch; floors created in other projects are ignored by this Zap.
2

New Group

Polling trigger

In Zapier“Triggers when a new group is created.”

Starts a run whenever a new group appears in your Planpoint account. It needs no project setting, which makes it the simplest trigger in the list.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
let your web or marketing lead know that a new group exists, so its pages and branding get prepared.
Watch out
only groups created after you publish the Zap count; existing ones are never sent.
3

New Lead

Polling trigger

In Zapier“Triggers when a new lead signed up. Leave project empty to trigger across all projects in your account.”

Fires when someone signs up as a lead on your Planpoint viewer. It turns interest in a unit into a name your sales team can call.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
push every lead into your CRM and assign it to the agent in charge of that building.
Watch out
leave the project empty to watch every project at once; pick one only if each project feeds a different pipeline.
4

New Portal Event

Polling trigger

In Zapier“Triggers when a new portal event is recorded. Leave project empty to trigger across all projects in your account.”

Picks up each new event Planpoint records on your portal. It gives you a feed of what visitors do there, beyond plain signups.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
log portal activity in a spreadsheet your marketing team reviews to see which projects draw attention.
Watch out
an empty project setting means events from every project, and therefore more runs to pay for if each one triggers an action.
5

New Portal Signup

Polling trigger

In Zapier“Triggers when a new user signs up in the portal. Leave project and group empty to trigger across all projects in your account.”

Runs when a new user creates an account on your Planpoint portal. Different from a lead: this person has signed up to the portal itself.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
add each portal user to a newsletter about launches and price updates for the projects they follow.
Watch out
leave both project and group empty to cover your whole account; filling one narrows the Zap to that scope.
6

New Project

Polling trigger

In Zapier“Triggers when a new project is created.”

Tells Zapier each time a project is created in Planpoint. For an agency that runs several developments, it marks the start of a new listing.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
create a folder and a kickoff task for the team that will build the floor plans of the new project.
Watch out
a batch of projects created at once, during an import for example, can be held back by Zapier's flood protection.
7

New Unit/Space

Polling trigger

In Zapier“Triggers when a new unit or space is created.”

Watches one project and fires on every new unit or space added to it, whether an apartment, an office or a parking spot.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
copy each new unit into the pricing spreadsheet your sales team works from, so the two never drift apart.
Watch out
the project is required, so one Zap covers one project; duplicate the Zap for each building you sell.
8

Updated Floor

Polling trigger

In Zapier“Triggers when a floor is updated.”

Follows one specific floor and reports when it changes. Narrow by design: you choose both the project and the floor to keep an eye on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
alert the architect or the designer when someone edits the floor they signed off on.
Watch out
to follow several floors you need several Zaps, since the floor setting is required and takes one floor.
9

Updated Group

Polling trigger

In Zapier“Triggers when a group ticket is updated.”

Reports changes to a group you pick. Useful when a group carries settings that other teams rely on.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
post a short note in your team chat whenever the group behind a client's portal is edited, so nobody is caught off guard.
Watch out
the group setting is required; this trigger does not watch every group of the account at once.
10

Updated Project

Polling trigger

In Zapier“Triggers when a project is updated.”

Fires when the project you select is edited, for instance when someone changes what the viewer shows. It is the project-level counterpart of the unit triggers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a dated change log in a spreadsheet, so the sales director can see who touched the project settings.
Watch out
do not pair it with Update Project on the same project, or the Zap reacts to its own edits.
11

Updated Unit/Space

Polling trigger

In Zapier“Triggers when a unit or space is updated.”

Watches the units and spaces of one project and fires when one of them is edited.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
tell the agent who follows a buyer that the unit they discussed has just changed.
Watch out
a Zap that updates units in the same project with Update Unit/Space will fire itself again and again and drain your tasks.
12

Updated Units/Spaces

Polling trigger

In Zapier“Triggers when units or spaces are updated.”

The plural sibling of Updated Unit/Space: it reports units or spaces updated within the project you choose. Zapier does not document how the two differ in practice.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
test it next to Updated Unit/Space on a busy project and keep the one whose results fit your report.
Watch out
running both on the same project can report the same edit twice; pick one per Zap.
Actions

The 9 Planpoint actions

Planpoint gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Floor

Action

In Zapier“Creates a floor in the system.”

Adds a floor to an existing project, with the name you give it.

When to use it
build the levels of a tower from a spreadsheet instead of typing each one in Planpoint.
Watch out
the project has to exist first; create it by hand or with Create Project in an earlier step.
2

Create Group

Action

In Zapier“Creates a Group in the system.”

Creates a group in your Planpoint account from data held elsewhere.

When to use it
set up a group for each new client agency once your onboarding form comes in.
Watch out
a name, a namespace and a host name are all required, so collect all three in the earlier step.
3

Create Project

Action

In Zapier“Creates a Project in the system.”

Opens a new project in Planpoint from another tool, such as a deal marked won in your CRM.

When to use it
start the floor plan work the moment a developer signs.
Watch out
the plan size must match the type: a rental project takes small, medium, big or massive, any other type standard, large or massive.
4

Create Unit/Space

Action

In Zapier“Creates a Unit or Space in the system.”

Puts a new unit or space on a project, ready to show on the viewer.

When to use it
load inventory from the sheet your sales team keeps, one row per apartment.
Watch out
it asks for bedrooms, square feet and availability every time; switch on Unit Price TBD when the price is not set yet.
5

Delete Unit/Space

Action

In Zapier“Deletes a Unit or Space in the system”

Removes a unit or space from a project. The one destructive action of the app.

When to use it
take a unit off the viewer when it is withdrawn from sale in your property system.
Watch out
there is no undo from Zapier, so test it on a dummy unit and put a filter in front of it.
6

Update Floor

Action

In Zapier“Updates a Floor in the system.”

Edits a floor you designate inside a project, starting with its name.

When to use it
rename levels across a project after the architect revises the numbering in the master file.
Watch out
project, floor and name are all required, even if you only want to change one of them.
7

Update Group

Action

In Zapier“Updates a Group in the system”

Modifies a group you pick in Planpoint.

When to use it
keep a client's group settings in line with the record your account managers maintain in another tool.
Watch out
the group is the only required setting, so double-check you picked the right one before you publish.
8

Update Project

Action

In Zapier“Updates a Project in the system.”

Changes what the viewer of a project displays, from prices to sold units, through a long series of on and off switches.

When to use it
hide prices on every viewer of a project the day your sales director decides to sell on request only.
Watch out
a Zap built on Updated Project for that same project will react to this change.
9

Update Unit/Space

Action

In Zapier“Updates a Unit or Space in the system.”

Updates an existing unit or space in the project you pick, for example whether its price is still to be determined.

When to use it
switch Unit Price TBD off once the price of a unit is settled in your pricing sheet, so the viewer stays honest.
Watch out
paired with Updated Unit/Space on the same project, it loops; add a filter or watch another project.
When it breaks

When a Planpoint Zap breaks

Zapier lists no help article and no app-specific limit for Planpoint. The failures you will meet come from Zapier's general rules.

Four cases explain most of the surprises on a Planpoint Zap. If a run still fails, the Zapier troubleshooting page is the place to look next.

  • The Zap triggers itself in a loop

    Updated Unit/Space watching a project while Update Unit/Space writes into it sets the Zap off again and again, and burns tasks quickly.

  • Units created before publishing are missing

    A Zap reacts only to what happens after it is switched on. Existing leads, floors and units are not picked up; moving them is a separate job.

  • A bulk import gets held back

    Loading a whole building at once can return a huge batch on the next check, and Zapier's flood protection may hold it back.

  • The same item never runs twice

    Zapier remembers what it has already seen on a polling trigger. Editing an old lead does not make New Lead fire again for it.
Need help

Need help automating Planpoint with Zapier?

A person reads every message.

FAQ

Planpoint Zapier integration: FAQ

01Is the Planpoint Zapier integration free?
Yes, Planpoint works on the free Zapier plan; it is not reserved for paid plans. The free plan gives you 100 tasks a month and Zaps of two steps, one trigger and one action. That covers a Zap like New Lead to a CRM contact. Once you add a second action, a filter or a guard in front of Delete Unit/Space, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Planpoint Zap use?
One task per action that succeeds, and none for the trigger. Zapier can check Planpoint for new leads or edits as often as your plan allows without charging anything. When it finds a lead and creates a CRM contact, that run costs one task. A Zap with three actions costs three per lead. A failed action is not counted. On a launch, when many leads arrive, count your expected volume against the plan before you go live.
03Does Planpoint trigger Zaps in real time?
No. All twelve Planpoint triggers are polling triggers: Zapier asks Planpoint for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. So a lead who signs up may reach your CRM up to 15 minutes later on the free plan. On paid plans you can also run a check by hand from the editor when you need it sooner.
04What does it take to connect Planpoint to Zapier?
A Planpoint account, and access to any project you do not own yourself. From the Apps page of Zapier, click + Add connection, search for Planpoint, click Add connection, sign in in the tab that opens and grant access. Before building, make sure at least one project exists: most Planpoint triggers and actions require one, and Create Group also needs a namespace and a host name that you have to provide.
05Why does a Planpoint Zap keep running on its own?
Because it probably writes into the place it watches. If Updated Unit/Space follows a project and the same Zap uses Update Unit/Space on that project, each update looks like a fresh change on the next check, and the Zap starts again. The same goes for Updated Project with Update Project. Every loop costs tasks. Watch one project and write into another, or add a filter that only lets the changes you want through.
06What if the operation you need is not available?
Check the nearest match first. Planpoint offers twelve triggers and nine actions but no search step, so a Zap cannot look up a unit or a project by name; it has to receive it from a trigger or select it in the step settings. If you need to read data from Planpoint that no trigger provides, or delete something other than a unit, Zapier cannot do it with this app today. Note the gap and look at what the other tool in your Zap can do instead.
07Zapier, Make or n8n for Planpoint?
Decide by criteria, not by habit. Speed: on Zapier every Planpoint trigger is polling, so the delay is set by your plan; check what the other tools offer for this app. Coverage: Zapier gives you nine actions on projects, floors, groups and units but no search. Budget: each successful action is a task, so a busy launch with many leads adds up. Compare these three points for your own volume before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations