Resources · Make integration

Testlify Make integrationAutomate Testlify with Make.

What if every finished Testlify assessment reached your hiring team without anyone checking the dashboard? The Testlify Make integration gives you 5 modules: 1 instant trigger, 2 actions and 2 searches. This guide is for recruiters and ops leads, and it walks you from the connection to a working first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Testlify Make integration do for your hiring?

The Testlify Make integration links your Testlify account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. With it, candidate assessments go out, get tracked and get reported without copy and paste between tools.

Candidates tested the moment they qualify. When a candidate reaches the right stage in another tool you already use, Send an Assessment delivers the Testlify test to them, so nobody has to remember to invite each applicant by hand.

Results that reach the right person. Watch a Completed Assessment is an instant trigger: Testlify calls Make through a webhook as soon as a candidate finishes. Your scenario can then pass the news to the hiring manager in the app where they already work.

A status check before a follow-up. Get Test Status looks up where a given test stands using the invite ID, and List Assessments returns the assessments created in your account, which helps when a scenario must pick the right test.

Limits worth knowing: the official Testlify page in the Make documentation warns that its content is AI-generated from vendor docs and may contain mistakes, so test each module with a real candidate first. For anything the listed modules skip, Make an API call reaches the rest of the Testlify API. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make training helps if this is your first scenario.

Connect

How do you connect Testlify to Make?

  1. 01

    Generate your Testlify API key

    In Testlify, click the profile icon in the top navigation, open Settings, then the Developers tab. Under API Key, click Generate Key and copy the key shown on screen. You need an active Testlify account for this.

  2. 02

    Add a Testlify module in Make

    In your scenario, add any Testlify module and click Create a connection. A connection is your Testlify account linked to Make once, then reused by every Testlify module. The Connection name field is optional but helps if you manage several accounts.

  3. 03

    Paste the credentials and save

    Paste the key you copied from Testlify, or follow the instructions Make shows on screen, then confirm. Once saved, the connection appears in the module and you can start filling in its fields.

First scenario

Your first scenario with Testlify and Make

GoalWhen a candidate completes a Testlify assessment, Make looks up the test status so your hiring team knows what to do next.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + to place the first module. This first module decides when everything else runs.

  2. 02

    Add the Testlify trigger

    Search for Testlify, choose Watch a Completed Assessment, click Create a webhook, then Create a connection and link the account you prepared earlier.

  3. 03

    Add Get Test Status

    Click the + to the right of the trigger, pick Get Test Status and map the invite ID from the trigger's bundle, if Testlify sends one there (check it during Run once). You can then chain the app your team reads, a chat or a spreadsheet.

  4. 04

    Test with Run once

    Click Run once, then have a test candidate finish an assessment. Each bundle, one item passed from module to module, shows up so you can check what Make received.

  5. 05

    Switch it on

    Because the trigger is instant, Testlify calls Make whenever an assessment ends. Switch the scenario on and each completed test gets its status checked without further clicks.

Triggers

What starts a Testlify scenario

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

Testlify1Watch a Completed Assessment

Watch a Completed Assessment

Instant trigger

In Make“Triggers when the candidate completes the assessment.”

You hear about a finished assessment the moment the candidate submits it, so a strong profile never waits in a queue until someone logs in to Testlify.

How it fires
instant, Testlify calls Make through a webhook as soon as the candidate completes the test, which the lightning badge on the module shows.
When to use it
pick it whenever the end of a test should kick off the next hiring step, such as alerting a recruiter or updating a candidate record in another app.
Watch out
click Create a webhook before Create a connection, and switch the scenario on, or Make will not receive the call.
Modules

What the Testlify modules can do

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

Testlify1

Make an API call

Action

In Make“Perform an arbitrary authorized API call”

Covers whatever the four other Testlify modules leave out: it calls any endpoint of the Testlify API while reusing the connection you already created, so no second login.

When to use it
reach for it only after checking that Send an Assessment, Get Test Status and List Assessments do not already do the job.
Watch out
you describe the request yourself, so keep the Testlify API reference open while you set it up.
Testlify2

Send an Assessment

Action

In Make“Sends a Testlify assessment to a candidate.”

Puts a Testlify assessment in front of a candidate without you opening Testlify, which turns the invitation into a step your scenario handles for you.

When to use it
after a module from another app spots a new applicant, place this action so the test goes out as soon as the candidate qualifies.
Watch out
each run sends a real invitation, so test with your own email address before you switch the scenario on.
Testlify3

Get Test Status

Search

In Make“Retrieves the status of the test sent to a candidate using the invite ID.”

Tells you where a specific candidate stands on a test they were sent, using the invite ID, so your scenario can decide whether a reminder or a review comes next.

When to use it
choose it when you already hold the invite ID and want one precise answer rather than the whole list of assessments.
Watch out
as a search, it can return no result; add a filter so later modules skip empty runs.
Testlify4

List Assessments

Search

In Make“List of all the assessments created in your Testlify account”

Returns the assessments created in your Testlify account, one bundle per assessment, which gives later modules a clean list to pick from or to copy elsewhere.

When to use it
use it before Send an Assessment when the scenario must choose which test fits a role, or to mirror your catalog of tests in a spreadsheet.
Watch out
every assessment returned is a separate bundle, and each module after it runs once per bundle, which counts operations.
Need help

Need help automating Testlify with Make?

A person reads every message.

FAQ

Testlify and Make: common questions

01Is the Testlify Make integration free?
Yes, on the Make side. Testlify is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in operations, one per module run on one bundle. You still need an active Testlify account, whose pricing is set by Testlify.
02What do you need to connect Testlify to Make?
An active Testlify account and an API key. In Testlify, open the profile icon, go to Settings, then the Developers tab, and click Generate Key under API Key. In Make, add a Testlify module, click Create a connection, optionally give it a name, then paste the key or follow the on-screen instructions. For the instant trigger, click Create a webhook first. The same connection then serves every Testlify module in your scenarios.
03Does the Testlify trigger in Make work in real time?
Yes. Watch a Completed Assessment is an instant trigger: Testlify calls Make through a webhook as soon as a candidate completes an assessment, instead of Make checking on a schedule. That matters when a recruiter wants to call a strong candidate quickly. Remember to switch the scenario on, because a scenario that is off receives nothing. Scenarios built only on actions and searches start from the schedule on their first module instead.
04What if a Testlify module is missing in Make?
Use Make an API call. It reaches any endpoint of the Testlify API with the connection you already have, so you can cover what Send an Assessment, Get Test Status and List Assessments do not. Keep in mind that the Make documentation page for Testlify is flagged as AI-generated from vendor docs and may contain mistakes, so check important details with Testlify and test each module on a real candidate before relying on it.
05Should you use Make or n8n for Testlify?
It depends on the tool your team already runs. Testlify often has an n8n node as well, and neither choice is better by default. On Make, you get 5 ready modules, including an instant trigger for completed assessments and a module to call the rest of the API. Compare the modules each tool offers for Testlify and the other apps in your hiring process, then pick the one where your whole workflow fits.