Resources · Zapier integration

HireTrack NX Zapier integrationAutomate HireTrack NX with Zapier.

The HireTrack NX Zapier integration gives you 2 triggers, 2 actions and 1 search. Enough to let the Windows software behind your rental and live production jobs talk to the rest of your tools, instead of retyping the same booking twice.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the HireTrack NX Zapier integration actually does

It links HireTrack NX, the Windows application that organizes, schedules and keeps the money side of equipment rental and live event production in order, to the thousands of apps Zapier reaches. You build a Zap (one starting event, then the steps that follow it) and the data moves on its own.

Three results come up again and again. First, an alert the second something changes: Web Hook From HireTrack NX lets the app call Zapier itself, so a message lands in your team chat while the job is still fresh. Second, a regular feed out of your own queries: Select Output QBE reads the result of a QBE you wrote in HireTrack NX and pushes each new line to a sheet, a CRM or an email. Third, a written trace inside HireTrack NX: Create NoteBook Entry drops a note into the NoteBook, and Update HireTrack NX adds data through a QBE of your own.

Now the limits. Everything here runs through QBEs you write yourself: Zapier offers no ready-made list of jobs, clients or items. If no query exists for the data you want, nothing comes out. There is also no delete action and no find-or-create shortcut, and the only lookup is Search Queries.

One point matters more than the rest on a free plan. Only one of the two triggers is instant, and that one reacts right away, plan or no plan. More on that in the triggers block. If you are weighing other tools, the same app also has a HireTrack NX Make integration page, and the Make vs Zapier comparison sets the two side by side.

Vocabulary

Zapier words, one line each

Seven terms come back all over this page. Read them once and the rest goes faster.

Zap
The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. One action completed successfully equals one task, and your plan counts those.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier itself the moment the event occurs.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and halts it otherwise.
Search step
A step that looks up something already stored in an app, so the following steps can reuse what it found.
Cost

What it really costs to run

HireTrack NX is not a premium app, so it works on the free plan. The bill depends on actions, never on triggers.

  • Premium appNo, free plan accepted
  • Tasks on the free plan100 per month
  • Steps on the free plan2 (one trigger, one action)
  • Cost of a trigger0 tasks

The trigger costs nothing, however often Zapier checks. Each action that goes through counts as one task; a failed one is not counted. A Zap with three actions eats three tasks per run. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Add a filter, a second action or Search Queries and it becomes a multi-step Zap, which needs a paid plan. Keep that in mind before sketching anything longer than two cards.

Connect

Connect your HireTrack NX account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a HireTrack NX account, plus read or write rights on any data you do not own and want the Zap to touch.

  2. 02

    Pick HireTrack NX

    Type the name in the dialog, select HireTrack NX in the results, then confirm with Add connection. A connection is your account linked once, then reused by every step that calls the app.

  3. 03

    Sign in and grant access

    Sign in to HireTrack NX in the tab that opens and let Zapier access the account. From then on, the connection shows up in the account list of every HireTrack NX step you add.

First Zap

Your first Zap: new query results to the warehouse channel

GoalEvery new line returned by a HireTrack NX query reaches the warehouse crew in Slack, but only the lines worth their attention.

  1. 01

    Create the Zap on your query

    Start a new Zap, pick HireTrack NX and Select Output QBE, then your connection. In the required Output QBE field, choose the query the crew should see, and test: Zapier brings back the three latest items.

  2. 02

    Add the filter

    Click the plus icon, add Filter, then fill the three boxes: the value you spotted in the test, the rule, and what to compare it with. Pick a text rule for text.

  3. 03

    Post to Slack

    Add Slack with Send Channel Message, choose the channel and drop the query values into the message. This filter plus action makes it a multi-step Zap, so a paid plan.

  4. 04

    Test, then publish

    Run each step once and read what came back. When the Slack message looks right in the channel, click Publish to switch the Zap on.

Triggers

HireTrack NX triggers

2 events start a Zap when something happens in HireTrack NX, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Select Output QBE

Polling trigger

In Zapier“Triggers when there is new data available from the customer written QBE.”

Watches the output of a QBE you wrote in HireTrack NX and starts the Zap for each new piece of data it returns. Your query decides the scope, not Zapier.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a daily-style feed of new results into a spreadsheet or a report, where a short wait between checks changes nothing for the reader.
Watch out
the Output QBE field is required, so the query has to exist in HireTrack NX before you can set up this step. Zapier remembers what it already saw, so the same line never starts the Zap twice.
2

Web Hook From HireTrack NX

Instant trigger

In Zapier“HireTrack NX can call this Trigger to initiate an action.”

Here HireTrack NX makes the first move: the app calls this trigger itself to launch the Zap. Of the two triggers, it is the only instant one, and that is the most useful fact on the page for anyone on the free plan.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
anything time-sensitive, like warning the crew chief in chat as soon as a job changes, where waiting for the next check would be too late.
Watch out
it asks for a Qbe Id, a required field, so pick the matching query before testing. In the editor, a Zap built on it shows a lightning bolt.
Actions

HireTrack NX actions

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

1

Create NoteBook Entry

Action

In Zapier“Creates a new entry in the HireTrack NX NoteBook.”

Writes a fresh entry into the HireTrack NX NoteBook, so a message, a form answer or an email from another app leaves a dated trace where your team already looks.

When to use it
logging a client request received elsewhere next to the rest of the job history.
Watch out
Master API Key, Detail API Key and Currency are all required, and the step stops without them.
2

Update HireTrack NX

Action

In Zapier“Adds data to HireTrack NX using a customer written QBE.”

Pushes data into HireTrack NX through a QBE written on your side, which means the query, not Zapier, decides where the values end up.

When to use it
feeding back a status or an amount that changed in another tool, without opening the Windows app.
Watch out
do not aim it at the data your own Select Output QBE watches, or the Zap restarts itself.
Searches

HireTrack NX search

1 search step looks for data that already exists in HireTrack NX, so a later step can use it.

A search step finds something that already exists, so later steps can use it. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens next.

1

Search Queries

Search

In Zapier“Search for any data in HireTrack NX using a customer written QBE.”

Looks up any data in HireTrack NX through a QBE you wrote, then hands the result to the steps below it. That is how a Zap gets a job reference or an amount no earlier step carried.

When to use it
between a trigger from another app and an action that needs a HireTrack NX value.
Watch out
Select QBE is required, and adding this step makes the Zap multi-step.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and the steps relying on it are skipped. Switched on, the Zap goes on with nothing in hand.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. HireTrack NX offers no such variant, so you will not see it on Search Queries.
  3. If multiple search results are found?
    Three exits when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When it breaks

When the HireTrack NX Zap breaks

Zapier links no help article to this app, so the cases below are the general Zapier limits that hit a HireTrack NX Zap.

Most failures come from the Zap doing exactly what it was told. Read these four before you publish, and keep the Zapier troubleshooting guide nearby for the rest.

  • Old jobs never come through

    A Zap only reacts to what happens after you switch it on. Bookings that already sat in HireTrack NX are not picked up; moving that backlog is a separate job.
  • The Zap keeps restarting itself

    If Update HireTrack NX writes into the data your Select Output QBE reads, each write sets off the trigger again and burns through your task count fast.
  • A big import stalls the trigger

    After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.
  • A line shows up only once

    On the polling trigger Zapier tracks what it has seen. A query line it already handled will not start the Zap a second time, even if you expect it to.
Need help

Need help automating HireTrack NX with Zapier?

A person reads every message.

FAQ

HireTrack NX Zapier integration: frequent questions

01Is the HireTrack NX Zapier integration free?
Yes, as far as the app goes: HireTrack NX is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, with one catch nobody mentions up front. Every Zap stays at two steps, one trigger and one action. The moment you add a filter, a second action or the Search Queries step, the Zap turns multi-step and you need a paid plan. Prices are not listed here because the grids change too often.
02How many tasks does a HireTrack NX Zap use?
One task per action that succeeds, nothing else. The trigger is free, whether it is Select Output QBE checking on a timer or the web hook firing on its own. A Zap that creates one NoteBook entry costs one task per run. A Zap that searches, then updates, then posts to another app costs more, because every completed action is counted separately. An action that fails is not billed. Keep an eye on loops, since a Zap that restarts itself can drain 100 tasks quickly.
03Is HireTrack NX on Zapier real time?
One trigger is, the other is not. Web Hook From HireTrack NX is instant: the app calls Zapier as soon as the event happens, and the plan has no effect on the speed. Select Output QBE is a polling trigger, so Zapier asks HireTrack NX for new results at a fixed interval: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On a free account, building on the web hook is the only way to get an immediate reaction. Paid plans can also run a check by hand from the editor.
04What does it take to connect a HireTrack NX account?
A HireTrack NX account, plus read or write rights on any data you do not own and want the Zap to reach. In Zapier, open Apps, click + Add connection, find HireTrack NX, confirm, sign in and grant access. After that, the connection is reused by every HireTrack NX step. Plan a little prep on the app side as well: the triggers and the search ask for a QBE, and Create NoteBook Entry asks for a Master API Key, a Detail API Key and a Currency before it will run.
05Why does a HireTrack NX trigger stay empty in Zapier?
Most of the time, the query behind it returns nothing new. Both triggers depend on a QBE written in HireTrack NX: Select Output QBE needs an Output QBE, the web hook needs a Qbe Id. If the query selects no fresh data, Zapier has nothing to show during the test. Remember too that a Zap ignores everything created before it was switched on, and that the polling trigger never sends the same line twice. Check the query in HireTrack NX first, then test the step again.
06What if the HireTrack NX operation you want is missing?
Look at the QBEs before giving up. On Zapier, HireTrack NX exposes 2 triggers, 2 actions and 1 search, and four of those five run on a query written on the customer side. So the gap is often a query that does not exist yet rather than a missing feature. Update HireTrack NX and Search Queries can cover a lot once the right QBE is in place. If what you need is a delete or a find-or-create, the app simply does not offer it on Zapier.
07Zapier, Make or n8n for HireTrack NX?
Decide on criteria rather than on a ranking. On Zapier, the facts are clear: HireTrack NX is not premium, one trigger is instant, the free plan stops at two steps, and every successful action is billed as a task. So ask yourself how many steps your flows need, how many runs a month you expect, and whether instant reaction matters. Compare those numbers against what the other tools document for this same app before choosing. The deciding factor is your volume and your need for multi-step flows.