Resources · Make integration

TestGorilla Make integrationAutomate TestGorilla with Make.

Stop copying candidates into TestGorilla by hand. The TestGorilla Make integration gives you 4 modules: 3 actions and 1 search. This page is for recruiters and ops teams, and it walks you from the API key to a working first scenario.

Try the TestGorilla integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TestGorilla Make integration automate?

The TestGorilla Make integration links your TestGorilla account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick. Here, those bricks invite candidates, list your assessments and fetch results.

Candidates tested without manual invites. A new applicant shows up in your form tool or ATS, and Invite a Candidate sends them the TestGorilla invitation. Nobody has to open TestGorilla to paste an email.

Scores back where the hiring team works. Get an Assessment Result pulls a result into the scenario so the next module can write it to a sheet, a CRM or a chat message. Pair it with the Airtable Make integration to keep a shortlist base up to date.

A clean pick list of tests. List Assessments returns the assessments in your account, handy when a scenario has to choose which test to send.

What the app does not do: it has no trigger module, so TestGorilla cannot start a scenario on its own. The scenario starts from another app or from Make's schedule. Anything the three actions miss goes through Make an API Call. Weighing tools? Read n8n vs Make, and check Make pricing before you scale up.

Connect

How do you connect TestGorilla to Make?

  1. 01

    Copy your API key

    In TestGorilla, open Integrations from your user menu, pick your ATS in the list, then click the toggle or gear icon. The setup window shows your API key: copy it. You need an active TestGorilla account for this.

  2. 02

    Add a TestGorilla module

    In your Make scenario, add any TestGorilla module and click Create a connection. A connection is your TestGorilla account linked to Make once, then reused by every TestGorilla module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in Connection name if you like, it is optional. Paste the API key you copied, or follow the instructions Make shows on screen, and save. The module can now read your account.

First scenario

Your first scenario with TestGorilla

GoalWhen a new applicant appears in another app, Make sends them a TestGorilla invitation.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where applicants arrive, such as your form tool or ATS, since TestGorilla has no trigger.

  2. 02

    Connect the source app

    Choose that app's module that picks up new applicants, click Create a connection and fill its fields. Make lists the forms or objects it can read once the account is linked.

  3. 03

    Add Invite a Candidate

    Click the + on the right of the first module, search TestGorilla and pick Invite a Candidate. Use your TestGorilla connection, then map the applicant data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one applicant. Check that the invitation went out.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Modules

What TestGorilla can do in Make

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

TestGorilla1

Get an Assessment Result

Action

In Make“Returns a result of the selected assessment.”

Brings the result of one assessment into your scenario, so the score can travel to wherever the hiring decision happens: a spreadsheet, a CRM record or a message to the hiring manager.

When to use it
after a candidate finishes a test and you want the outcome logged next to the rest of their file.
Watch out
it targets one assessment you select; to find which one, run List Assessments earlier in the scenario.
TestGorilla2

Invite a Candidate

Action

In Make“Sends an invitation to the selected candidate.”

Sends a TestGorilla invitation to the candidate you point it at, which removes the copy and paste step between your applicant source and the test platform.

When to use it
right after a new applicant lands in your ATS or form tool and should take the test.
Watch out
an invitation reaches a real person, so test with Run once on your own details before switching the scenario on.
TestGorilla3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the TestGorilla API from the scenario, reusing the same connection, so you are not stuck when the three listed actions stop short of what you need.

When to use it
a task the other modules do not cover, once you have found the matching endpoint in the TestGorilla API docs.
Watch out
you write the request yourself, so read the vendor docs before relying on it.
TestGorilla4

List Assessments

Search

In Make“Retrieves a list of assessments.”

Returns the assessments that exist in your TestGorilla account. As a search, it can hand back zero, one or several bundles, one per assessment, to the modules that follow.

When to use it
when a scenario must pick the right test before inviting someone or fetching a result.
Watch out
every returned assessment runs the next modules once, which costs one operation each, so filter before heavy steps.
Need help

Need help automating TestGorilla with Make?

A person reads every message.

FAQ

TestGorilla and Make: common questions

01Is the TestGorilla Make integration free?
Yes, on the Make side. TestGorilla is a standard app, available from the Free plan. That plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need your own active TestGorilla subscription, which TestGorilla prices on its own page. Every module run on one bundle counts as one operation on your plan.
02What do you need to connect TestGorilla to Make?
An active TestGorilla account and its API key. In TestGorilla, open Integrations from the user menu, select your ATS, then click the toggle or gear icon: the setup window shows the key. In Make, add a TestGorilla module, click Create a connection, paste the key and save. Every other TestGorilla module in your account reuses that connection. Remember that path: the same window is where you find the key again if you ever need to copy it.
03Does the TestGorilla Make integration have a real-time trigger?
No. The TestGorilla app has no trigger module at all, scheduled or instant. A scenario that uses it starts in another way: on a trigger from another app, such as the form tool or ATS where applicants arrive, or on Make's own schedule, every 15 minutes by default on a new scenario. The TestGorilla modules then run as steps after that start. In practice, pick the start that matches when a candidate enters your pipeline, then add the TestGorilla steps after it.
04What if the TestGorilla module you need is missing?
Use Make an API Call. It calls any endpoint of the TestGorilla API with the connection you already set up, so a task the three listed actions miss can still run inside the same scenario. Keep in mind that the Make documentation for this app is AI-generated from TestGorilla's own docs and may contain mistakes, so confirm important details with TestGorilla. If the call fails, the Make troubleshooting guides are a good next stop before contacting support.
05Should you use Make or n8n for TestGorilla?
It depends on your stack more than on TestGorilla. In Make, the app offers 4 modules plus Make an API Call, a visual editor and a Free plan to test on. If your team already builds workflows in n8n, check whether a TestGorilla node exists there before switching. Pick the tool where your other hiring apps already live, so every automation stays in one place. Both tools can call an API directly when a ready-made module falls short, so coverage alone rarely decides it.
Same platform

Other docs you might need on this stack.

Browse all integrations