Resources · Zapier integration

PlanOK GCI Zapier integrationAutomate PlanOK GCI with Zapier.

The PlanOK GCI Zapier integration offers 20 triggers, 2 actions and 3 searches. Every trigger is checked on a timer, the app works on the free plan, and it follows a real estate sale from the first contact to reservations, promises and payments.

See the 25 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PlanOK GCI Zapier integration is for

The PlanOK GCI Zapier integration connects GCI, the real estate CRM that runs the sales cycle of a property project, to the rest of your tools. GCI records each step of a sale; Zapier spots the new ones and carries them elsewhere. Two actions and three searches let a Zap write back into GCI or look something up there.

Three results show the point. A sales team that never misses a lead: New Contact A, New Contact B or New Contact C picks up whatever lands in the centralizer, and Create Tracking logs the follow-up with its re-contact date. A finance view that stays current: New Payment, New Payment Entered, New Payment Reconciled and New Payment Reversed can feed the sheet your controller works from. A project manager who hears about every turn of a deal: New Reservation, New Promise and New Writing can post to the team chat, and New Resciliation or New Reservation Canceled flags the ones that fall through.

Now what Zapier does not do here. None of the 20 triggers is instant: every one waits for Zapier's next check. Only two actions exist, and neither creates a contact, a reservation or a payment. The searches only return promise details and sellers. Anything else stays a job inside GCI.

The same app also has a PlanOK GCI Make integration page, and Make vs Zapier sits next to it if you are still choosing.

Vocabulary

Zapier vocabulary, kept short

You do not need to know Zapier to use this page. These are the only words it relies on.

Zap
The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and ignores the rest.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. Each action that completes successfully is one task, and your plan sets how many you get.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for its latest items and keeps only those it has not seen yet.
Instant trigger
A trigger the app reports itself the moment the event happens. PlanOK GCI has none, and that shapes every Zap.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What a PlanOK GCI Zap really costs

PlanOK GCI is not a premium app, the kind Zapier reserves for paid plans: it works on the free plan. You pay in tasks, and only actions create them.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Searches and filtersMake the Zap multi-step: paid plan
  • Trigger and checksNever billed

The trigger never costs a task, and neither does Zapier checking GCI for new payments or reservations, however often it looks. Each action that succeeds counts once; one that fails does not. The free plan builds two-step Zaps only, one trigger and one action. Add a search step, a filter or a second action and you have a multi-step Zap, which needs a paid plan. Every useful search on this page therefore implies a paid plan.

Connect

Connect PlanOK GCI to Zapier in three steps

  1. 01

    Start a new connection

    Open the Apps page of your Zapier account and click + Add connection. Before that, make sure you have a GCI account with read or write access on the projects and records you do not own.

  2. 02

    Find PlanOK GCI

    Type PlanOK GCI in the dialog's search box, pick it, then click Add connection. A new tab opens on the GCI side and asks you to sign in with your usual credentials.

  3. 03

    Sign in and allow access

    Log in with the GCI account the Zaps should act on, then grant Zapier access. The connection is stored once and every later GCI step, trigger, action or search, reuses it.

First Zap

Your first Zap: every new quote gets its seller and a follow-up

GoalWhen a quote appears in GCI, find the seller behind it and log a tracking entry so the follow-up is never forgotten.

  1. 01

    Set the trigger

    Create a Zap, choose PlanOK GCI as the app that starts it and New Quote as the event, then pick your GCI connection for every step.

  2. 02

    Test with a real quote

    Run the test. Zapier brings back the three most recent quotes of your account; choose a real one so the next steps are mapped on true values.

  3. 03

    Add the search

    Add a step, choose PlanOK GCI and, under SEARCH at the bottom of the Action event list, pick Obtain Seller by Quote. Point it at the quote from step one.

  4. 04

    Add Create Tracking

    Add PlanOK GCI again and pick Create Tracking. Map the client, project, medium, contact type and expectation IDs, and type the re-contact date as yyyy-mm-dd.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the tracking entry looks right in GCI, publish the Zap. It needs a paid plan, because the search makes it multi-step.

Triggers

The 20 PlanOK GCI triggers

20 events start a Zap when something happens in PlanOK GCI. Zapier checks for them at the interval your plan allows.

1

New Business

Polling trigger

In Zapier“Triggers when a new business is detected in GCI.”

Starts your Zap each time GCI registers a new business, the first trigger in this 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
open a matching row in the pipeline sheet your sales director reviews.
Watch out
businesses created before you publish the Zap are never picked up afterwards.
2

New Canceled Promises

Polling trigger

In Zapier“Triggers when a new canceled promise is detected in GCI.”

Reacts when Zapier finds a promise newly marked as canceled in GCI. Promise is GCI's own term, kept as the editor shows 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
alert the project manager and finance so nobody keeps counting on that promise.
Watch out
pair it with New Promise rather than New Promise (Deprecated) so both ends of the story match.
3

New Contact A

Polling trigger

In Zapier“Triggers when a new contact is detected to the centralizer.”

Catches every new contact detected in the GCI centralizer, with no condition at all.

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 raw lead to a shared sheet so nobody on the team has to log in to see it.
Watch out
it also sees the contacts B and C pick up, so running both in parallel sends the same person twice.
4

New Contact B

Polling trigger

In Zapier“Triggers when a new contact with email is detected to the centralizer.”

Fires only for centralizer contacts that come with an email address, which narrows the flow to leads you can actually write to.

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 leads into your email tool for a welcome sequence about the project.
Watch out
contacts that arrive without an email never reach this trigger, so keep A for a full count.
5

New Contact C

Polling trigger

In Zapier“Triggers when a new contact with name, project and mobile phone is detected to the centralizer.”

Waits for the most complete leads: centralizer contacts that carry a name, a project and a mobile phone.

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
hand a call-ready lead to the salesperson in charge of that project, with the number already there.
Watch out
a lead missing any of the three never starts this Zap, so do not use it to measure total demand.
6

New Current Account

Polling trigger

In Zapier“Triggers when a new current account is detected in GCI.”

Detects each new current account in GCI, so the record does not have to be copied by hand elsewhere.

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 the matching customer file in your accounting tool without anyone retyping the buyer's name.
Watch out
a migration that opens many accounts at once can be held back by Zapier's flood protection.
7

New Current Account Reservation

Polling trigger

In Zapier“Triggers when a new current account reservation is detected in GCI.”

Goes off when GCI records a current account reservation, a different record from the one New Reservation watches.

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
notify the collections team that a new reservation amount needs following.
Watch out
it is not the same trigger as New Reservation; test both and keep the one whose data your process needs.
8

New Payment

Polling trigger

In Zapier“Triggers when a new payment is detected in GCI.”

Runs on every new payment GCI detects, the broadest of the payment triggers in this app.

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 single payment log for the whole project in a spreadsheet the board can read.
Watch out
each payment starts a run, and each run spends one task per action, so keep an eye on your count on a busy project.
9

New Payment Reconciled

Polling trigger

In Zapier“Triggers when a new payment reconciled is detected in GCI.”

Waits for payments that GCI has marked as reconciled, money that is confirmed against the books rather than simply recorded.

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 sales agent that the buyer's payment is confirmed and the next step can start.
Watch out
reconciliations done before the Zap went live are not replayed.
10

New Payment Entered

Polling trigger

In Zapier“Triggers when a new payment entered is detected in GCI.”

Picks up each payment as it is entered in GCI, before any reconciliation has happened.

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
give finance an early heads-up so the reconciliation does not wait on someone noticing.
Watch out
the same payment can later show up on New Payment Reconciled too, so avoid writing it twice in the same sheet.
11

New Payment Reversed

Polling trigger

In Zapier“Triggers when a new payment reversed is detected in GCI.”

Flags payments that have been reversed in GCI, the ones that undo money you thought had arrived.

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
send an alert to the controller and the agent so they call the buyer before the file goes stale.
Watch out
Zapier only sees each reversal once; edits made to it afterwards do not start the Zap again.
12

New Promise (Deprecated)

Polling trigger

In Zapier“Triggers when a new promise is detected in GCI.”

The older version of the promise trigger, still listed in the editor with its deprecated tag.

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
only to understand an existing Zap someone built on it before the new version existed.
Watch out
for any new Zap pick New Promise instead; Zapier describes both with the same sentence, and only the deprecated one carries the warning.
13

New Promise

Polling trigger

In Zapier“Triggers when a new promise is detected in GCI.”

Fires for each new promise detected in GCI, the current version of this trigger and the one to build 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
announce each new promise in the team channel and open the checklist your process attaches to it.
Watch out
add Obtain Promise Details after it if the next step needs more than the trigger brings back.
14

New Project

Polling trigger

In Zapier“Triggers when a new proyect is added in GCI.”

Notices each new project added to GCI, whatever stage the rest of the sale is at.

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 the project's shared folder or channel so marketing and sales start from the same place.
Watch out
testing brings back the three most recent projects of the account, however old they are.
15

New Quote

Polling trigger

In Zapier“Triggers when a new quote is detected in GCI”

Starts a run whenever Zapier's check finds a new quote in GCI.

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
look up the seller with Obtain Seller by Quote and log a follow-up, as in the Zap above.
Watch out
adding that search turns the Zap multi-step, so the free plan is no longer enough.
16

New Resciliation

Polling trigger

In Zapier“Triggers when a new resciliation is detected in GCI.”

Signals each new resciliation detected in GCI. The word is GCI's own: check with your team which records it covers before building on 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
warn finance and the project lead together, from one Zap, instead of relying on someone noticing.
Watch out
canceled promises and canceled reservations have their own triggers; this one will not catch them.
17

New Reservation

Polling trigger

In Zapier“Triggers when a new reservation is detected in GCI.”

Fires on each reservation detected in GCI, when a buyer puts a unit on hold.

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
update the availability board your brokers check before they promise a unit to anyone.
Watch out
a Zap that writes back into GCI on every reservation must never touch what this trigger watches, or it loops.
18

New Reservation Canceled

Polling trigger

In Zapier“Triggers when a new reservation canceled is detected in GCI.”

Reacts to reservations canceled in GCI, the units that just became free again.

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
put the unit back on the availability board and tell the waiting list manager.
Watch out
a bulk cleanup of old reservations can return a huge batch that Zapier's flood protection holds back.
19

New Reservation With Medium

Polling trigger

In Zapier“Triggers when a new reservation is detected in GCI.”

A second reservation trigger. Its name points to the medium GCI attaches to a reservation, the same Medium ID that Create Tracking asks for.

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
when your reporting needs that medium alongside each reservation.
Watch out
Zapier gives it the same description as New Reservation, so test both and compare what each returns before choosing.
20

New Writing

Polling trigger

In Zapier“Triggers when a new writing is detected in GCI.”

Tracks every new writing detected in GCI, the last stage named in this list of 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
start the handover checklist for the after-sales team once a writing shows up.
Watch out
testing returns only the three latest writings of the account, which may be older than you expect.
Actions

The 2 PlanOK GCI actions

PlanOK GCI gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Tracking

Action

In Zapier“Create tracking in GCI.”

Logs a follow-up entry in GCI for a client and a project, with the date someone should get back in touch.

When to use it
make sure every new lead or quote gets a dated next step without a salesperson typing it.
Watch out
all six fields are required, five of them are GCI IDs, and the re-contact date must be written yyyy-mm-dd.
2

Update Centralizer

Action

In Zapier“Updated centralizer in GCI.”

Changes an existing centralizer entry in GCI rather than adding one, by stamping the date the contact really happened.

When to use it
once a call or meeting is logged in another tool, close the loop on the lead inside GCI.
Watch out
it needs the centralizer ID (ID Centralizador) and the real contact date (Fecha Real Contacto), both required.
Searches

The 3 PlanOK GCI searches

3 search steps look for data that already exists in PlanOK GCI, so a later step can use it.

A search step finds something that already exists in GCI and hands it to the steps that follow. In the editor, the three GCI searches sit at the bottom of the Action event list, under SEARCH. Each one makes the Zap multi-step, so it needs a paid plan.

1

Obtain Promise Details

Search

In Zapier“Obtain promise details in GCI.”

Pulls up the details of a promise already in GCI so later steps can use them.

When to use it
right after New Promise, when the message or document you build needs more than the trigger returned.
Watch out
whether it wants an exact value or something close is decided by GCI, so test it on a real promise first.
2

Obtain Seller by Quote

Search

In Zapier“Obtain seller by Quote in GCI.”

Finds the seller attached to a quote, which is how a Zap learns who owns the deal.

When to use it
between New Quote and an action, to route the follow-up or the alert to the right person.
Watch out
if no seller is found and the default is left on, every step after it is skipped.
3

Obtain Seller by RUT

Search

In Zapier“Obtain seller by RUT in GCI.”

Looks up a seller from a RUT number, useful when the identifier is all another tool gives you.

When to use it
when a form or spreadsheet holds the seller's RUT and the Zap needs the full seller record.
Watch out
the RUT field is required and must be typed without the hyphen and without the check digit.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that relied on it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. PlanOK GCI exposes no such variant, so none of its three searches will offer it.
  3. If multiple search results are found?
    When several items match, you choose: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When a PlanOK GCI Zap breaks

Zapier attaches no help article to PlanOK GCI, so these are the general limits that hit this app the hardest.

Most problems come from timing, overlaps and history, not from the connection. When a Zap misbehaves, the Zapier troubleshooting page is the next stop.

  • Past sales are never picked up

    A Zap reacts only to contacts, reservations or payments created after you publish it. Everything already in GCI stays there, and moving that history is a separate job.

  • Writing where the trigger watches

    A Zap that writes into the very place its own trigger watches sets itself off again and again, and burns through your task count fast.

  • Bulk imports get held back

    After a migration or a mass import into GCI, a trigger can suddenly return a huge batch. Zapier's flood protection can hold it back instead of running each item.

  • Each item runs only once

    Zapier remembers what it has already seen on a polling trigger. A reservation edited later is not new to it, so it will not start the Zap a second time.
Need help

Need help automating PlanOK GCI with Zapier?

A person reads every message.

FAQ

PlanOK GCI Zapier integration: common questions

01Is the PlanOK GCI Zapier integration free?
Yes, PlanOK GCI works on Zapier's free plan, because Zapier does not reserve it for paid plans. The free plan gives 100 tasks per month and unlimited Zaps, but every Zap stops at two steps: one trigger and one action. New Contact C followed by Create Tracking fits. Adding one of the three searches, a filter or a second action makes the Zap multi-step, and that needs a paid plan.
02How many tasks does a PlanOK GCI Zap use?
One task per action that succeeds, and nothing for the trigger. Zapier checking GCI for new payments or reservations costs nothing, however often it looks. A Zap with one action costs one task per new item; a Zap with three actions costs three. An action that fails is not counted. On a busy project, payment triggers are the ones that move your count, since every payment starts its own run.
03Does PlanOK GCI send data to Zapier in real time?
No. All 20 PlanOK GCI triggers are polling triggers and none is instant. Zapier goes and looks at regular intervals that depend on your plan: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. On paid plans you can also change that interval and run a check by hand from the editor while you build and test. PlanOK GCI has no instant trigger, so this delay applies to every Zap you build on it.
04What does it take to connect PlanOK GCI to Zapier?
A GCI account, with read or write access on the projects and records you do not own and want the Zap to touch. In Zapier, open the Apps page, click + Add connection, search for PlanOK GCI, click Add connection, sign in to GCI in the tab that opens and grant access. You do it once, and every later GCI step reuses that same connection. If a step later fails on a record, check that account's access first.
05Which New Contact trigger should be used: A, B or C?
It depends on how complete the lead must be. New Contact A fires for every new contact in the centralizer. New Contact B fires only when the contact has an email. New Contact C fires only when it has a name, a project and a mobile phone. Running A alongside B or C sends the same person twice, so pick one per Zap and match it to the next step.
06What if the PlanOK GCI operation you need is not available?
Then Zapier cannot do it with GCI today. The integration offers 20 triggers, two actions (Create Tracking and Update Centralizer) and three searches, nothing more. Creating a reservation, a payment or a contact from a Zap is not possible, so that work stays inside GCI. Check the list on this page first: the operation may exist under a name that does not match your vocabulary. Update Centralizer is the only action that changes an existing record.
07Zapier, Make or n8n for PlanOK GCI?
Decide on criteria rather than reputation. First, which tool offers the GCI operations your process needs; on Zapier that is 20 triggers, two actions and three searches. Second, timing: on Zapier every GCI trigger waits for the next check of your plan. Third, cost: compare how each tool bills a run against the volume of leads and payments your projects produce. None of these criteria names a winner in advance.
Same platform

Other docs you might need on this stack.

Browse all integrations