Resources · Make integration

PlanOK - GCI Make integrationAutomate PlanOK - GCI with Make.

Can Make pull your PlanOK - GCI projects and deals into other tools? The PlanOK - GCI Make integration gives you 6 action modules and no trigger. This page is for sales and operations teams: connect the account, build a first scenario, then pick the right module.

Try the PlanOK - GCI integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PlanOK - GCI Make integration do?

It links your PlanOK - GCI account, a CRM and sales tool, to Make, a no-code platform where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. The app brings 6 action modules, and none of them is a trigger, so something else has to start the scenario.

A project list that feeds your other tools. Put Obtener proyectos after a Make schedule and each project comes out as a bundle, one item passed to the next module, ready to be written into a sheet or a dashboard.

Deals checked without logging in. Obtener negocios, as its name suggests, reads your deals so a scenario can hand them to a messaging app or a report. Pair it with Obtener tipo contactos when the next step needs to know which contact types exist.

Payment channel details kept in step. Asociar informacion canales de pagos is the only module whose name points to writing rather than reading. Test it on one record before letting a scenario run it at scale.

Know the limits first. Make says it cannot publish complete documentation for PlanOK - GCI because too little public information exists, so the modules have no official description and the exact fields show up only once you open them in the editor. The Make troubleshooting guide helps when a run fails. The same app often has an n8n node too, and n8n vs Make lays out how the two tools differ. If a live project is on the line, the Make agency team can build it with you.

Connect

How do you connect PlanOK - GCI to Make?

  1. 01

    Add a PlanOK - GCI module

    In your scenario, click the +, search for PlanOK - GCI and pick any of its modules. Then click Create a connection. A connection is your account linked to Make once and reused by every module of the app.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when several accounts coexist. Then either approve Make on the PlanOK - GCI page that opens or paste the key the app provides, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and every other PlanOK - GCI module in your scenarios can select it without asking for your credentials again.

First scenario

Your first scenario with PlanOK - GCI

GoalWhen the Make schedule fires, Make reads your PlanOK - GCI projects and then fetches the model tied to each one.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since PlanOK - GCI has no trigger, start from another app or leave the start to Make's schedule.

  2. 02

    Add Obtener proyectos

    Search for PlanOK - GCI, pick Obtener proyectos and click Create a connection to link your account. Fill in the fields Make shows once the connection exists.

  3. 03

    Chain the project model

    Click the + on the right of the module, add Obtener modelo por proyecto and map the project from the previous module into its fields, so each project gets its own lookup.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which is the only reliable way to see what these modules actually return.

  5. 05

    Schedule and switch on

    Open the clock on the first module, keep the default of every 15 minutes or change it, then switch the scenario on. On the Free plan, 15 minutes is the shortest gap between scheduled runs.

Modules

What the PlanOK - GCI modules do

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

PlanOK - GCI1

Asociar informacion canales de pagos

ActionIn the docs only

This module links payment channel information in PlanOK - GCI, going by its name, which makes it the one module here that changes data instead of reading it.

When to use it
when a scenario receives payment details from another tool and they must land against the right record in PlanOK - GCI.
Watch out
Make publishes no description of its fields, so run it once on a test record and check the result in PlanOK - GCI.
PlanOK - GCI2

Llamada API

ActionIn the docs only

Its name means API call: the module is there to reach PlanOK - GCI directly when none of the other five covers what you need.

When to use it
after checking the other modules, for a request only the PlanOK - GCI API answers.
Watch out
it is not the universal Make an API Call module, and the documentation says nothing about its fields, so ask your PlanOK - GCI administrator what the API expects.
PlanOK - GCI3

Obtener modelo por proyecto

ActionIn the docs only

You get the model attached to one project, as the name indicates, which gives the next module detail that a plain project list lacks.

When to use it
right after Obtener proyectos, mapping each project into it so the lookup runs once per bundle.
Watch out
every project processed costs one operation, the unit Make counts on your plan, so a long list adds up quickly.
PlanOK - GCI4

Obtener negocios

ActionIn the docs only

Pulling your deals out of PlanOK - GCI is the job its name describes, and it turns the sales pipeline into bundles other apps can use.

When to use it
when the sales team wants deals copied into a report or sent to a chat channel without anyone exporting them by hand.
Watch out
press Run once before mapping anything, because only the bundles it returns show which deal fields you can actually use.
PlanOK - GCI5

Obtener proyectos

ActionIn the docs only

Going by its name, this module reads your projects, a natural first step since Obtener modelo por proyecto needs a project to work from.

When to use it
as the first PlanOK - GCI step of a scheduled scenario that feeds a sheet, a dashboard or the next module.
Watch out
the scenario has no trigger of its own, so the schedule on the first module decides when this read happens.
PlanOK - GCI6

Obtener tipo contactos

ActionIn the docs only

Retrieving the contact types defined in your PlanOK - GCI account is what this module is named for, handy reference data for later steps.

When to use it
when a later module or another app needs to sort or label contacts by the categories set up in PlanOK - GCI.
Watch out
this is reference data, not contacts themselves, so do not expect it to return names or emails.
Need help

Need help automating PlanOK - GCI with Make?

A person reads every message.

FAQ

PlanOK - GCI and Make: common questions

01Is the PlanOK - GCI Make integration free?
Yes, PlanOK - GCI is a standard app, so its modules work from the Make Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at most often, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans such as Core, Pro, Teams and Enterprise lift those limits and count usage in monthly credits. Your PlanOK - GCI subscription is a separate matter.
02What do you need to connect PlanOK - GCI to Make?
A PlanOK - GCI account and a Make account. The documentation lists no prerequisite and no app-specific steps, so the generic flow applies: add a module, click Create a connection, optionally name it, authorize Make on the PlanOK - GCI page or paste the key the app gives you, then click Save. If a key is required, your PlanOK - GCI administrator is the person to ask. Once saved, the same connection serves all 6 modules of the app.
03Can PlanOK - GCI start a Make scenario in real time?
No. PlanOK - GCI has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. Start it from the schedule on the first module, which runs every 15 minutes by default, or open the scenario with a trigger from another app, then place the PlanOK - GCI modules after it. For a check without waiting, click Run once in the editor. Keep in mind that each module in the chain then counts its own operations on your plan.
04What if a PlanOK - GCI module is missing in Make?
It depends on the need. The app has no universal Make an API Call module, but it does include its own Llamada API module, which you can try once you know what the PlanOK - GCI API expects. Make also warns that its documentation for this app is limited for lack of public information. When neither route works, the Hackceleration team can study the case with you. Start by testing Llamada API with Run once on a harmless request.
05Should you use Make or n8n for PlanOK - GCI?
It depends on the tool your team already works in. On Make, PlanOK - GCI brings 6 action modules and no trigger, available from the Free plan. The same app often has an n8n node as well, so compare the modules each tool offers for your use case before choosing. Pick the one whose modules cover your steps and whose editor your team is comfortable maintaining. Either way, test with Run once before switching anything on.
Same platform

Other docs you might need on this stack.

Browse all integrations