PlanOK GCI
CRMConnect AI agents to PlanOK GCI, the real estate commercial management platform for Latin American developers. Agents create leads, register natural-person clients, and log tracking entries, then read the projects, units, reservations, promises, and quotations a deal moves through.
What This Integration Enables
PlanOK GCI, Gestión Comercial Inmobiliaria, is the commercial side of a real estate development business in Chile and across Latin America: which units exist, who enquired about them, which are reserved, which carry a signed promise, and what has been paid. The shape of this integration tells you exactly where PlanOK draws its line of trust, and it is worth being direct about it rather than implying more than is there. Reservations, promises, payments, quotations, and the business records that hold them are read only through this connector. There is no action that reserves a unit, signs a promise, records a payment, or moves a deal to the next stage of the funnel. The three writes available are Create Lead, Create Natural Client, and Create Tracking.
That is not a gap in the connector, it is the product being sensible. A reserva and a promesa de compraventa on a housing unit are commitments with legal and financial consequences for the developer, and PlanOK does not expose them to an external system to create. What it does expose is everything an agent needs to do the work that surrounds them. List Projects, Get Project Stages, Get Project Models, and Get Project Arrival Mediums read the catalog of what is being sold and how buyers are arriving at it. List Businesses, Get Business Reservations, and Get Business Promises read the state of a deal. List Reservations, List Promises, List Quotations, and List Payments read across the sales book, with payments distinguishing entered, reconciled, and reversed states, which is the distinction that separates a real cash position from an optimistic one. List Contact Types and List Expectations resolve the catalog values that Create Tracking and Create Lead depend on. Operationally: authentication takes three values issued to your inmobiliaria by PlanOK, the apikey, a numeric User ID, and that user's password. Only the login call uses the apikey; the service exchanges the credentials at the login endpoint for a session token, reuses it across subsequent requests, and re-authenticates automatically when it is rejected. Dates are supplied as YYYY-MM-DD, and the ids returned by the list operations are the inputs to the detail and create operations. This connector ships no triggers and registers no webhook subscription with PlanOK, so a flow watching for a new reservation is a scheduled poll of List Reservations with a date filter, not an event. Saying so plainly matters more here than usual, because a sales team that believes it will be notified the moment a unit is reserved and is actually being told six hours later will make a promise to a second buyer.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A portal enquiry that arrives as a registered lead rather than an email
Enquiries collect from listing portals, paid campaigns, and the showroom tablet. For each one the agent calls List Projects to resolve which development the enquiry names, Get Project Models to resolve the unit typology the buyer asked about, and Get Project Arrival Mediums to record how they arrived, because attribution in this business decides next quarter's media spend and a lead with a blank medium is a lead that teaches nobody anything. List Expectations resolves the expectation value that describes what the buyer is looking for. It then calls List Natural Clients on the RUT to see whether this person is already in the register. Where they are, Create Lead is written against the existing identity and Create Tracking logs the first contact. Where they are not, the lead is prepared and held at the gate below, because creating the identity is the step this connector cannot take back.
A daily sales position that separates money received from money promised
On a schedule the agent calls List Businesses to read the deals in flight, then Get Business Reservations and Get Business Promises on each to see which units are held and which have moved to a signed promise. List Payments is read with its state filter so entered, reconciled, and reversed amounts are counted separately rather than summed into one comforting number, and List Quotations shows what has been priced but not committed. The joined position lands in Google Sheets for the commercial manager and a short version posts to Slack, flagging promises with no reconciled payment against them and reservations older than the developer's holding policy. Every action in this run is a read, which is precisely why it can run every morning without an approval step.
Follow-up that survives the executive who did it
A sales executive finishes a call or a site visit, and the record of it goes into WhatsApp or a notes app and stops there. Instead, the flow resolves the client with List Natural Clients, reads List Client Trackings to see what has already been logged so the same conversation is not recorded twice, resolves the contact type through List Contact Types, and calls Create Tracking with the substance of the contact. Where the conversation named a specific unit, the agent reads Get Project Models and Get Project Stages to confirm that typology is still being sold at that stage before anything is promised verbally. If the buyer wants to hold a unit, the flow stops there and hands the reservation to a person, because reserving is not something this connector can do and pretending otherwise would be worse than the manual step.
Human-in-Loop Highlight
Create Natural Client is the write to gate here, and the reason is that it is a one way door dressed as a routine create. A natural client in GCI is the identity that everything else attaches to: the leads, the trackings, and eventually the reservation and the promise that a sales executive will make inside the platform. This connector offers List Natural Clients and Create Natural Client and nothing else. There is no update and no delete. A client created with a transposed RUT, an inverted apellido paterno and apellido materno, or a formatting variant of the same national identifier is a second person as far as GCI is concerned, and it will stay that way until somebody fixes it inside the platform by hand. What makes it costly rather than untidy is what happens next. The executive who takes the call searches the register, finds one of the two records, and makes the reservation against it. The trackings, the campaign attribution, and the earlier enquiry sit on the other one. The developer now has a buyer whose history is split across two identities at exactly the moment the file needs to be complete. So the agent resolves and stops. It runs List Natural Clients against every candidate identifier in the batch and posts to the sales manager: "62 enquiries ready to register. 48 resolved to exactly one existing client by RUT. 9 matched nothing and would create a new client. 5 need a decision: 3 match an existing client by name and email but the RUT differs by its check digit, 1 has no RUT at all and matches two clients with the same full name, and 1 matches a client whose record already carries a reservation on Torre Poniente. I cannot update or delete a client through this connector, so anything I create wrong has to be fixed inside GCI. Create the 9, and tell me which identity to use for the 5?" The manager answers once, and Create Natural Client runs only where a person confirmed the identity. This is the human-in-the-loop moment on a platform that will happily hold two versions of the same buyer, because an agent can prove that two RUTs differ and only a person can say which one belongs to the family standing in the showroom.
Agent Capabilities
19 actionsProjects
4- List Projects Returns the developments available to your inmobiliaria. The ids returned here are the inputs to the project detail operations and to Create Lead.
- Get Project Stages Returns the stages, or etapas, of a project. Used to confirm which phase of a development a unit typology belongs to before anything is discussed with a buyer.
- Get Project Models Returns the unit models of a project, which is the typology catalog a buyer is actually choosing from.
- Get Project Arrival Mediums Returns the arrival mediums configured for a project, so a lead is registered with a real attribution value rather than a blank one.
Deals
3- List Businesses Returns the commercial deals, or negocios, in flight. Read only, and the entry point to reading what is attached to each one.
- Get Business Reservations Returns the reservations attached to a business. Read only. Reservations are made inside GCI by a person and this connector reads their state rather than creating them.
- Get Business Promises Returns the promises attached to a business. Read only, and the signal that a deal has moved from a held unit to a signed commitment.
Sales
4- List Reservations Returns reservations across the sales book. Read only, used to see which units are currently held and for how long.
- List Promises Returns signed promises across the sales book. Read only, and the basis for a committed revenue view.
- List Payments Returns payments in their entered, reconciled, and reversed states. Read only, and the action that separates money actually received from money merely recorded.
- List Quotations Returns quotations. Read only, showing what has been priced without being committed to.
Leads
2- List Leads Returns registered leads. Used to check whether an enquiry has already been recorded before a duplicate is created.
- Create Lead Registers an enquiry against a resolved project, with its arrival medium and expectation. This is the write that gets a portal enquiry into the system on the day it arrives rather than at the end of the week.
Clients
4- List Natural Clients Returns the natural person clients in the register. This is the deduplication read, and the one that has to run on the RUT before any client is created.
- Create Natural Client Creates a natural person client. This connector exposes no update and no delete for clients, so a record created here is corrected inside GCI by a person, which is why it runs behind an approval.
- List Client Trackings Returns the tracking entries already logged against a client. Used to read the contact history before adding to it, so the same call is not recorded twice.
- Create Tracking Logs a follow-up contact against a client, with its contact type resolved from the catalog. This is how a conversation becomes part of the file instead of part of somebody's memory.
Catalog
2- List Contact Types Returns the configured contact types. Used to resolve the value Create Tracking expects rather than sending a label.
- List Expectations Returns the configured expectations, the values that describe what a buyer is looking for. Used to resolve the value Create Lead expects.
Frequently Asked Questions
What can FlowRunner do with PlanOK GCI?
FlowRunner agents can run List Projects, Get Project Stages, and Get Project Models in PlanOK GCI, plus 16 more actions.
Does connecting PlanOK GCI to FlowRunner require OAuth?
No. PlanOK GCI connects to FlowRunner with session-based authentication, no OAuth flow required.
Can PlanOK GCI trigger a FlowRunner workflow automatically?
PlanOK GCI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PlanOK GCI
$100 in credits. No card required. Connect in minutes.