Resources · Make integration

Gamfi Make integrationAutomate Gamfi with Make.

Can Make add employees to Gamfi and start their processes for you? The Gamfi Make integration gives you 9 modules: 1 trigger, 7 actions and 1 search. This guide is for HR and ops teams new to Make, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Gamfi Make integration do for your HR team?

The Gamfi Make integration links your Gamfi account to Make so that employees and processes move without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search. Make runs that chain for you.

New hires land in Gamfi on their own. When a person is recorded in another tool, Add an Employee creates them in Gamfi, and Start a Process can open their first process right after, all mapped from the same data.

Process updates reach the rest of your stack. Watch Process Data checks Gamfi on the scenario's schedule. If its bundles carry the employee's ID (check with Run once), Get an Employee details (by ID) tells you who the process belongs to, then send that to a sheet, a chat or a CRM.

Closing the loop from outside Gamfi. A signed document or a ticket marked done elsewhere can call Complete a Process, so nobody has to tick the box by hand.

Know the limits before you start. Make's own documentation for Gamfi is thin: it says there isn't enough public information about the app, and it lists the 9 modules without describing their fields. Expect to learn each module by opening it and testing with a real record. If a step fails, the Make troubleshooting guide covers the common errors, and the Make training teaches the editor from scratch.

Also weighing n8n? The n8n vs Make comparison lays out the criteria side by side, without picking a winner for you.

Connect

How do you connect Gamfi to Make?

  1. 01

    Add a Gamfi module

    In a scenario, click the +, search for Gamfi and pick any of its modules. Make then asks for a connection, meaning your Gamfi account linked to Make once and reused by every Gamfi module afterwards. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the workspace it points to. Then either approve Make on the Gamfi page that opens, or paste the key Gamfi gives you, depending on what the connection window shows.

  3. 03

    Save and check

    Click Save. The module now shows your connection in its dropdown, and Make can list what it can read from Gamfi when you fill the fields. If the list stays empty, the connection is the first thing to recheck.

First scenario

Your first scenario: onboard a new hire in Gamfi

GoalWhen a new hire is recorded in another app, Make creates the employee in Gamfi and starts a process for them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the tool where new hires appear first, for example a form or a sheet, and choose the module that watches new entries.

  2. 02

    Add an Employee in Gamfi

    Click the + on the right of that first module, search for Gamfi and pick Add an Employee. Create the connection, then map the name and contact details from the previous module into the fields Make shows.

  3. 03

    Start a Process

    Add Start a Process after it. Make lists what it can read from your Gamfi account, so choose the process you want every new hire to go through, and map the employee created one step earlier.

  4. 04

    Test with Run once

    Add one test entry in the source tool and click Run once. Open each module's bubble to read the bundles it received, a bundle being one item passed along, here one person. Check that the employee shows up in Gamfi.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and that is the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Triggers

What can start a Gamfi scenario?

1 module starts a scenario when something happens in Gamfi. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Gamfi as soon as it happens.

Gamfi1Watch Process Data

Watch Process Data

triggerIn the docs only

Watch Process Data brings Gamfi process information into Make, so a change on the HR side can kick off work in your other tools. It is Gamfi's only trigger, and Make's documentation does not describe it.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes by default; the documentation does not mark it as instant and its name (Watch) points to a polling trigger, so expect a delay.
When to use it
you want a manager, a sheet or a CRM to hear about process updates without anyone forwarding them.
Watch out
run it once on a real account and read the bundles before you build on it, since the fields it returns are not documented.
Modules

What can Make do in Gamfi?

Gamfi gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Gamfi1

Add an Employee

ActionIn the docs only

Add an Employee creates a person in Gamfi from data arriving in your scenario, so nobody retypes a new hire who already exists in your form, ATS or spreadsheet.

When to use it
as the first Gamfi step of an onboarding scenario, before any process is started for that person.
Watch out
the documentation says nothing about duplicates, so look the person up by e-mail first if the same hire could reach the scenario twice.
Gamfi2

Complete a Process

ActionIn the docs only

Complete a Process marks a Gamfi process as finished from outside Gamfi, which keeps the HR record in step with what actually happened elsewhere.

When to use it
a contract gets signed, equipment is handed over or a ticket closes in another app, and that event should end the matching process.
Watch out
the module has to know which process to close, so keep its identifier from the step that started or found it.
Gamfi3

Delete a Process

ActionIn the docs only

Delete a Process removes a process from Gamfi, handy for clearing out processes that were opened by mistake or for someone who never joined.

When to use it
an offer is withdrawn in your recruiting tool and the onboarding process started for that person should disappear.
Watch out
the documentation mentions no undo, so treat every run as final. Test it on a dummy process with Run once before you let a live scenario call it.
Gamfi4

Get an Employee details (by ID)

ActionIn the docs only

Get an Employee details (by ID) fetches one person's Gamfi record when you already hold their Gamfi identifier, typically handed over by an earlier Gamfi module.

When to use it
after Watch Process Data, if a Run once shows an employee ID in its bundles, to turn it into a name and contact details you can send to someone.
Watch out
an ID from another tool will not match. Use the e-mail or phone variant when the data comes from outside Gamfi.
Gamfi5

Get an Employee details (by e-mail)

ActionIn the docs only

Get an Employee details (by e-mail) finds a Gamfi employee from their work address, the identifier most other apps already carry.

When to use it
a message, a calendar invite or a support ticket arrives with only an address, and you need the matching Gamfi profile before acting.
Watch out
addresses get typed differently from one tool to the next. Run once with a known colleague to see what comes back when the spelling differs.
Gamfi6

Get an Employee details (by phone number)

ActionIn the docs only

Get an Employee details (by phone number) pulls a Gamfi profile when a phone number is the only thing you have about the person.

When to use it
texts or calls logged in a messaging or telephony app, where no e-mail travels with the contact.
Watch out
the documentation gives no expected number format. Test with numbers written the way your source app writes them, with and without the country prefix, before you rely on it.
Gamfi7

List Workflows

SearchIn the docs only

List Workflows returns the workflows set up in your Gamfi account, so a scenario can see what exists before it starts anything.

When to use it
your scenario needs to know which workflows exist before acting, or you want to keep an outside sheet in sync with what HR has configured.
Watch out
as a search, it can return zero, one or many bundles. Every module after it then runs once per workflow, and each run counts as an operation on your plan.
Gamfi8

Start a Process

ActionIn the docs only

Start a Process launches a Gamfi process on your behalf, turning an event elsewhere into the first HR step without a manual click.

When to use it
just after Add an Employee in an onboarding flow, or when a status change in another app should open a review or an offboarding.
Watch out
the documentation lists no fields, so open the module after connecting and check which process and which employee it expects.
Need help

Need help automating Gamfi with Make?

A person reads every message.

FAQ

Gamfi and Make: frequent questions

01Is the Gamfi Make integration free?
Yes. Gamfi is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and count usage in operations each month. Make charges nothing extra for Gamfi itself.
02What do you need to connect Gamfi to Make?
A Gamfi account and a Make account are enough as far as the documentation shows. Make lists no prerequisite and no official steps for Gamfi, so you follow the generic flow: add a Gamfi module, click Create a connection, optionally name it, authorize Make on the Gamfi page or paste the key Gamfi gives you, then click Save. The same connection serves all 9 modules afterwards. If the authorization window asks for something you do not have, ask your Gamfi administrator before going further.
03Does the Gamfi trigger in Make react in real time?
Most likely not. Make's documentation does not state its type, but its name (Watch) and the lack of any instant marker point to a scheduled trigger: Make checks Gamfi on the scenario's schedule, every 15 minutes by default, or every minute at best on a paid plan. If you need a faster reaction, start the scenario from an app that calls Make the moment something happens, then use the Gamfi modules as actions.
04What if a Gamfi module is missing in Make?
It depends on what you need. Gamfi has no Make an API Call module in Make, so you cannot reach the rest of its API from the editor. Make also warns that its Gamfi documentation is limited for lack of public information. Check first whether one of the 9 modules covers the job once you open it, try another app that holds the same data, or ask the team for help on a custom route.
05Should you use Make or n8n with Gamfi?
It depends on your criteria rather than on Gamfi alone. This page covers the Make side: 9 modules, a scheduled trigger and a connection that takes a few clicks. Many apps also have an n8n node, so check whether Gamfi does before you compare. Weigh the modules each tool offers for Gamfi, the editor your team already knows and the other apps in your stack. Neither tool is ranked here.