Resources · Make integration

HireTrack NX Make integrationAutomate HireTrack NX with Make.

Can Make update HireTrack NX for you when something changes elsewhere? The HireTrack NX Make integration gives you 4 modules: 3 actions and 1 search. This page shows how to link your account, what each module does and how to test a first scenario.

Try the HireTrack NX integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the HireTrack NX Make integration do?

The HireTrack NX Make integration links your HireTrack NX account to Make, a tool where you build a scenario (an automation made of connected bricks) without writing code. It has no trigger of its own, so a scenario starts from a schedule or from another app, then reads or changes HireTrack NX data.

Keep records in sync. When a form tool or a spreadsheet receives new information, a scenario can pass it to Update HireTrack NX, so nobody copies the same details twice.

Look something up before acting. Search Queries returns zero, one or several items, and the next module works on each of them. It is the safe way to check what exists before an update.

Reach what the list leaves out. Make an API Call calls any endpoint of the HireTrack NX API with the same connection, and Select Output QBE completes the set of actions.

Know the limit before you start: the Make documentation for this app is thin, because little public information exists about HireTrack NX. Expect to test each module with Run once rather than rely on a field guide. The Make troubleshooting page helps when a run fails, and the Make training covers the editor basics. The same app may also have an n8n node; the n8n vs Make comparison sets out how the two tools differ.

Connect

How do you connect HireTrack NX to Make?

  1. 01

    Add a HireTrack NX module

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

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, for example the account it belongs to. Then either authorize Make on the HireTrack NX page that opens, or paste the key HireTrack NX gives you.

  3. 03

    Save the connection

    Click Save. The connection now appears in the module, and the other HireTrack NX modules of your scenario can pick it from the same list without asking again.

First scenario

Build your first scenario with HireTrack NX

GoalWhen new data lands in another app, Make finds the matching HireTrack NX records and updates them.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the module of the app where your data starts, since HireTrack NX has no trigger.

  2. 02

    Add Search Queries

    Click the + on the right, search HireTrack NX and choose Search Queries. Create the connection if needed, then map the value to look for from the first module.

  3. 03

    Add Update HireTrack NX

    Add Update HireTrack NX after the search. Fill its fields with data from the previous modules; Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along. Check that the search found the right record before trusting the update.

  5. 05

    Schedule and switch on

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

Modules

What each HireTrack NX module does

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

HireTrack NX1

Make an API Call

ActionIn the docs only

This module gives you access to any endpoint of the HireTrack NX API, with the connection you already set up, so nothing is out of reach just because no module covers it.

When to use it
the three other modules do not do what your process needs, and the HireTrack NX API does.
Watch out
you write the request yourself, so check what the HireTrack NX API expects and test with Run once.
HireTrack NX2

Search Queries

SearchIn the docs only

As its name suggests, Search Queries finds existing HireTrack NX data and hand it to the next module. Like any search in Make, it can return zero, one or several bundles.

When to use it
before an update, to find the exact record an incoming change refers to.
Watch out
several results mean the following modules run once per result, and each run counts as an operation.
HireTrack NX3

Select Output QBE

ActionIn the docs only

Select Output QBE is an action that works on one item at a time. The Make documentation gives no description of what it returns, so the safest way to learn it is to add it and read the bundle it produces.

When to use it
when your HireTrack NX setup relies on it and you want that step inside the scenario.
Watch out
test it with Run once on sample data before mapping its output anywhere.
HireTrack NX4

Update HireTrack NX

ActionIn the docs only

With Update HireTrack NX, data coming from another app ends up in your HireTrack NX account without anyone retyping it. It acts on one item per run.

When to use it
after Search Queries has found the record, to write the new details onto it.
Watch out
an update changes live data, so check the mapped values in a Run once test first.
Need help

Need help automating HireTrack NX with Make?

A person reads every message.

FAQ

HireTrack NX and Make: common questions

01Is the HireTrack NX Make integration free?
Yes, HireTrack NX is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month, one operation being one module run on one item.
02What do you need to connect HireTrack NX to Make?
A HireTrack NX account and a Make account. The Make documentation lists no specific prerequisite for this app. You add any HireTrack NX module, click Create a connection, optionally name it, then either authorize Make on the HireTrack NX page or paste the key HireTrack NX provides. After you click Save, every HireTrack NX module in your scenarios reuses that same connection, so you only do this once per account.
03Does the HireTrack NX Make integration react in real time?
No, because HireTrack NX has no trigger module in Make. A scenario therefore starts in one of two ways. Either you set a schedule on the first module, every 15 minutes by default, or 1 minute at the shortest on a paid plan. Or you start the scenario with a trigger from another app, such as a form or a spreadsheet, and let the HireTrack NX modules act after it. Both approaches work with the three actions and the search.
04What if a HireTrack NX module is missing in Make?
Use Make an API Call. It calls any endpoint of the HireTrack NX API with the connection you already have, which covers what Search Queries, Select Output QBE and Update HireTrack NX leave out. Keep in mind that the Make documentation for this app is limited, because little public information about HireTrack NX exists. You will need to know what the HireTrack NX API expects to write the request, and a Run once test to confirm the response before you switch the scenario on.
05Should you use Make or n8n for HireTrack NX?
It depends on the tool your team already uses. On Make, HireTrack NX offers 4 modules, one of them a generic API call, and runs on the Free plan as a standard app. The same app often has an n8n node too, so check what that node covers before choosing. This page does not rank the two tools: compare the modules each side offers for your process, then build the scenario where your other automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations