Resources · Make integration

Grafea-GO Make integrationAutomate Grafea-GO with Make.

Can Make push data into Grafea-GO without a single line of code? Yes: the Grafea-GO Make integration offers 6 action modules around two objects, Enfant and Évènement. This page walks a Make beginner through the connection, a first scenario and each module.

Try the Grafea-GO integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Grafea-GO Make integration do?

It lets a Make scenario, the automation you build as a chain of modules, write to your Grafea-GO account. Each module is one brick of that chain. Grafea-GO brings 6 of them, all actions: they create or report on Enfant and Évènement items, and they run when something upstream starts the scenario.

Register an Enfant from another tool. A form app, a spreadsheet or a CRM starts the scenario, and Créer un Enfant adds the entry to Grafea-GO. Nobody retypes the same name twice.

Keep Évènement data in step. The modules Évènement Créé/Modifié and Évènement Supprimé cover changes to events. Place them after the step that holds the change, then check with Run once what each one returns.

Reach what the named modules miss. The Module Universel Grafea-GO is the generic entry point of the app, for the cases the five other modules do not cover.

One honest limit: Make's own documentation for Grafea-GO is incomplete, because little public information exists about the app. Test every module with a real record before you rely on it, and keep the Make troubleshooting guide close. Weighing tools first? Read the n8n vs Make comparison, or the Make review for the bigger picture.

Connect

How do you connect Grafea-GO to Make?

  1. 01

    Add a Grafea-GO module

    In a scenario, click the +, search for Grafea-GO and pick any of its modules. Then click Create a connection. A connection is your Grafea-GO account linked to Make once, and every Grafea-GO module reuses it afterwards.

  2. 02

    Name the connection

    This step is optional, yet it pays off when several accounts coexist. A clear label, such as the site or team it belongs to, makes the right account easy to spot later in the list of connections.

  3. 03

    Authorize and save

    Grant Make access on the Grafea-GO page that opens, or paste the key Grafea-GO gives you, depending on what the window asks. Click Save. The module can now list what it reads from your account.

First scenario

Your first scenario with Grafea-GO

GoalWhen a new entry lands in another app, Make creates an Enfant in Grafea-GO.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Grafea-GO has no trigger, so the first module comes from the app where new entries appear, such as your form tool.

  2. 02

    Add Créer un Enfant

    Click the + on the right of that first module, search for Grafea-GO and choose Créer un Enfant. Pick your connection, or click Create a connection if this is your first Grafea-GO module.

  3. 03

    Map the data

    Fill the module with values from the first module. Each item passing through is a bundle: one form entry, one row. Drag its values into the matching boxes instead of typing them.

  4. 04

    Test with Run once

    Click Run once and send a test entry. Make runs the scenario one time and shows the bundles each module received. Open Grafea-GO and check that the new Enfant is there.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which runs every 15 minutes by default, then switch the scenario on. Each module run on one bundle is an operation, which Make counts on your plan.

Modules

What the Grafea-GO modules do

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

Grafea-GO1

Créer un Enfant

ActionIn the docs only

This one adds a new Enfant to Grafea-GO, filled with data coming from an earlier module, so a registration made elsewhere ends up in your account without copy and paste.

When to use it
right after the module that receives a sign-up, whether it comes from a form or from a fresh row in a spreadsheet.
Watch out
no fields are listed anywhere. Run it once on a test record before going live.
Grafea-GO2

Enfant Créé/Modifié

ActionIn the docs only

You get a module built around Enfant items that were created or changed, as its name says. Make classes it as an action rather than a trigger, which means it never starts a scenario by itself.

When to use it
in a flow that must pass an Enfant update along to Grafea-GO or onward.
Watch out
the documentation says nothing more, so check what the bundle holds with Run once.
Grafea-GO3

Enfant Supprimé

ActionIn the docs only

Here the subject is an Enfant that was deleted, going by the module's name. Make lists it as an action, which means it sits after another module rather than opening the flow.

When to use it
when a removal elsewhere has to be reflected in Grafea-GO.
Watch out
the documentation does not say what a removal does inside Grafea-GO, so try it on a dummy Enfant first.
Grafea-GO4

Module Universel Grafea-GO

ActionIn the docs only

A generic door into Grafea-GO, useful when none of the five named modules fits what you want to do. It is the only module of the app that is not tied to Enfant or Évènement by name.

When to use it
for a need the other modules do not cover.
Watch out
Make publishes no detail on how it works, so ask your Grafea-GO administrator what it expects before building on it.
Grafea-GO5

Évènement Créé/Modifié

ActionIn the docs only

Évènement items that were created or updated are the focus of this module, according to its name. Like every Grafea-GO module it is an action: some other module or a schedule has to run first.

When to use it
when an event change on one side needs to show up in Grafea-GO.
Watch out
run a single test and read the result before mapping its values into later steps.
Grafea-GO6

Évènement Supprimé

ActionIn the docs only

The last module handles an Évènement that was removed, as its label indicates, and keeps your event list consistent with the rest of your tools once the scenario runs.

When to use it
when an event cancelled in another app must disappear from Grafea-GO too.
Watch out
nothing in the documentation says whether a removal can be undone, so treat it as final and test on a sample event.
Need help

Need help automating Grafea-GO with Make?

A person reads every message.

FAQ

Grafea-GO and Make: common questions

01Is the Grafea-GO Make integration free?
Yes. Grafea-GO is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle. This page quotes no price for Grafea-GO itself.
02What do you need to connect Grafea-GO to Make?
A Grafea-GO account and a Make account. Make's documentation gives no specific prerequisite and no dedicated connection steps for this app. The generic path applies: add a Grafea-GO module, click Create a connection, optionally name it, authorize Make on the Grafea-GO page or paste the key the app provides, then click Save. The connection is then reused by all 6 modules. If the window asks for a key you do not have, your Grafea-GO administrator is the person to ask.
03Does the Grafea-GO Make integration react in real time?
No, not by itself, because Grafea-GO has no trigger module in Make: its 6 modules are all actions. A scenario therefore starts elsewhere. Either a trigger from another app opens the flow, such as a new form entry, or you rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario. How fast the Grafea-GO step runs depends entirely on what starts the scenario.
04What if a Grafea-GO module is missing in Make?
It depends on the need. Try the Module Universel Grafea-GO first, since it is the generic entry point of the app. Grafea-GO has no Make an API Call module, so there is no raw request fallback inside Make. Keep in mind that Make's documentation for this app is incomplete, which is why every module deserves a test with Run once. If the gap remains, another app in your flow may cover the step, or the team can look at the case with you.
05Should you use Make or n8n for Grafea-GO?
It depends on where your other tools already live. On Make, Grafea-GO offers 6 action modules, a standard app available from the Free plan, but no trigger and no Make an API Call module. Many apps also have an n8n node, so check whether Grafea-GO has one before choosing. The useful criteria are simple: which platform already runs your other scenarios, and whether the available modules match the steps you need. Neither answer is right for everyone.
Same platform

Other docs you might need on this stack.

Browse all integrations