Resources · Zapier integration

NiceJob Zapier integrationAutomate NiceJob with Zapier.

The NiceJob Zapier integration gives you 2 triggers, 8 actions and 1 search. Both triggers are instant and react to people and reviews; the actions add people, bookings, visits, cases, invoices, payments and employees, and enroll contacts in review campaigns.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NiceJob Zapier integration does for you

NiceJob is a platform that helps you collect more customer reviews and build your reputation online. Zapier connects it to your other tools through a Zap: an automation that starts on one event, then runs one or more steps for you. Here, the events are people and reviews, and the steps feed NiceJob.

Every review in front of the team. Review Created or Updated starts a Zap when a review is created or changed. Sent to a team chat, it means nobody has to log in to NiceJob to see what customers said.

Review requests that start on their own. Enroll Contact puts a contact into a NiceJob campaign, the Get Reviews campaign by default, from an email address alone. The contact can come from any step that carries an email.

A people list kept in sync. Create or Update Person, says its official description, creates a person or updates an existing person with the given email. Point it at another contact list and NiceJob follows it; check in the test how it treats a contact NiceJob already holds.

What Zapier does not do here. The integration has no step that deletes anything, and most actions (booking, case, visit, invoice, payment) need a NiceJob Person ID, which another tool does not hold on its own. If you are weighing platforms, see our Make vs Zapier comparison, or our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary, in one minute

Eight terms come back on this page. Here they are in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, and nothing runs before it.
Action
What the Zap does after it starts: the step that writes, sends or creates something for you in an app.
Task
The unit Zapier bills: one action that completes successfully. Your plan counts those and nothing else.
Polling vs instant
A polling trigger is checked by Zapier at a fixed interval. An instant trigger is reported by the app itself when the event happens.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What NiceJob costs you in Zapier tasks

NiceJob is not a premium app, so it works from the free plan. The bill is counted in tasks, and only completed actions count.

  • Triggernever costs a task
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps
  • Premium appno

The trigger never costs a task. Each NiceJob action that goes through costs one; an action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps. Find a Person, a filter or a second action makes the Zap multi-step, which needs a paid plan. The polling grid below is the standard Zapier one; it does not apply to the NiceJob triggers, which are both instant.

Connect

Connect your NiceJob account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your NiceJob account linked once, then reused by every step that uses NiceJob.

  2. 02

    Pick NiceJob and sign in

    Search for NiceJob by name in the dialog, pick it, then click Add connection. A tab opens on NiceJob: sign in with the account the Zap should work with.

  3. 03

    Grant access

    Allow Zapier to use that NiceJob account on the last screen. You need a NiceJob account, plus read or write access on anything you do not own yourself and want the Zap to touch.

First Zap

Your first NiceJob Zap, step by step

GoalLog every new or updated NiceJob person in a spreadsheet, then post a note to your team chat.

  1. 01

    Create the Zap

    Start a new Zap and pick NiceJob as the app that starts it. Choose Person Created or Updated as the event, then select your NiceJob connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map fields from a real person rather than a guess.

  3. 03

    Add the spreadsheet row

    Add your spreadsheet as the first action and place the values the test showed into the columns you want to keep for each person.

  4. 04

    Add the chat message

    Add a second action that posts to your team chat. It makes the Zap multi-step, so it needs a paid plan; without it, the Zap fits the free plan.

  5. 05

    Test, then publish

    Test each action once and read what came back. When both look right, publish the Zap to switch it on. For a guided pass, see our Zapier training.

Triggers

NiceJob triggers

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

1

Person Created or Updated

Instant trigger

In Zapier“Triggers when a new person is created or an existing person is updated.”

This trigger starts a Zap when a new person is created in NiceJob or an existing one is updated. One trigger covers both cases, so a Zap built on it sees new contacts and changes to known ones.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to keep a spreadsheet or another contact list in line with the people in NiceJob.
Watch out
an update starts the Zap as well as a creation, so read in the test what an update brings back before mapping it.
2

Review Created or Updated

Instant trigger

In Zapier“Triggers when a new review is created or an existing review is updated.”

Reacts to reviews: a new one, or a change to an existing one. It is the trigger behind any Zap that shares, files or answers what customers say about you.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
to post each review in a team chat or keep a running list of reviews in a spreadsheet.
Watch out
check in the test which review fields actually arrive before you map them; the official description does not list them.
Actions

NiceJob actions

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

1

Create Booking

Action

In Zapier“Creates a new Booking.”

Records a booking in NiceJob for a person. Person ID is required, and an optional Complete field says whether the booking is complete.

When to use it
when appointments set in another tool should also be tracked in NiceJob.
Watch out
Person ID must come from an earlier step; if you use Find a Person, check in the test whether it returns one.
2

Create Case

Action

In Zapier“Creates a new case.”

Opens a case in NiceJob for a person. The only required field is Person ID, the NiceJob ID of that person.

When to use it
when an issue logged in another tool should follow the person into NiceJob.
Watch out
without a search before it, the Person ID has to be typed or come from a step that holds it.
3

Create Employee

Action

In Zapier“Creates a new employee.”

Adds an employee to your NiceJob account from a single required field, the employee's Email.

When to use it
when a new team member recorded in another tool should also exist in NiceJob.
Watch out
map the employee's own address, not a shared one, and check the result in the test.
4

Create Invoice

Action

In Zapier“Creates a new Invoice.”

Creates an invoice in NiceJob. Person IDs, Total and Balance are required; Total includes tax and discounts, Balance is what remains due, and Paid is optional.

When to use it
when invoices issued elsewhere should also show in NiceJob.
Watch out
Total and Balance are separate fields; map each one to the right value.
5

Create or Update Person

Action

In Zapier“Creates a new Person or updates an exisitng person with the given email.”

Creates a person in NiceJob, or updates the existing person who has the given email. Email is the only required field.

When to use it
when contacts from another tool should reach NiceJob, whether they are new or already there.
Watch out
the official description speaks of updating an existing person with the given email; check in the test what happens with a contact NiceJob already holds.
6

Create Payment

Action

In Zapier“Creates a new payment.”

Records a payment against one or more people. Person IDs and Amount are required, and the field help says Amount is in dollars.

When to use it
when payments received in another tool should be logged in NiceJob.
Watch out
if your amounts are kept in another currency, check what you send against that field help.
7

Create Visit

Action

In Zapier“Creates a new visit.”

Adds a visit tied to a booking. Booking ID and Person ID are both required, with an optional Complete field.

When to use it
when a booking leads to one or more visits you want on record in NiceJob.
Watch out
two IDs are needed; confirm in the test that earlier steps carry both before you publish.
8

Enroll Contact

Action

In Zapier“Enrolls a contact into a NiceJob campaign, defaulting to the Get Reviews campaign.”

Puts a contact into a NiceJob campaign; the official description says it defaults to the Get Reviews campaign. Email is the only required field.

When to use it
when a contact recorded in another tool should receive a review request from NiceJob.
Watch out
run the test and check in NiceJob which campaign the contact landed in before you publish.
Searches

NiceJob search

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

A search step creates nothing: it finds a person who already exists in NiceJob and hands that person to the next steps. In the editor, searches sit at the bottom of the Action event list, under the SEARCH heading. Three settings decide what happens next.

1

Find a Person

Search

In Zapier“Find a person with a specific email address.”

Looks up a NiceJob person from an email address. Email is the only required field.

When to use it
before Create Booking, Create Case or Create Payment, starting from an email that another tool already holds, if the test shows it returns the ID those steps need.
Watch out
check in the test which value the search returns for the Person ID field before you map it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. NiceJob exposes no find-or-create variant, so Find a Person stays a plain search.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a NiceJob Zap breaks

Zapier links no help article to NiceJob, so the cases below are the general Zapier limits that apply to it.

Each case comes with a plain cause and a plain way out. If a Zap still misbehaves, open our Zapier troubleshooting guide.

  • Older reviews never show up

    A Zap only reacts to what happens after it is switched on. Reviews and people from before are not picked up; moving that backlog is a separate job.
  • The Zap keeps restarting itself

    As a general precaution, a Zap that writes into the place its own trigger watches can set itself off again and again, and burn through your tasks.
  • A big batch is held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.
  • The Zap stops at the search

    If Find a Person finds nothing and the setting is on its default, the Zap stops there and the booking, case or payment after it is skipped.
Need help

Need help automating NiceJob with Zapier?

A person reads every message.

FAQ

NiceJob Zapier integration: frequent questions

01Is the NiceJob Zapier integration free?
Yes, as long as each Zap stays at two steps. NiceJob is not a premium app, so it runs on the free plan, which gives 100 tasks a month and an unlimited number of Zaps. Each of those Zaps is one trigger and one action, such as a chat message for each review. Find a Person is a search, though, and a search makes the Zap multi-step, as does a filter or a second action. Those Zaps need a paid plan.
02How many tasks does a NiceJob Zap use?
One task per action that completes. The trigger never costs anything, whether it reports a person or a review. A Zap that adds each new person to a spreadsheet and then posts in chat uses two tasks per run. An action that does not go through is not counted. Remember that Person Created or Updated also fires on updates, so count those runs too before you estimate your monthly total.
03Do NiceJob triggers fire in real time?
Yes. Person Created or Updated and Review Created or Updated are both instant triggers: NiceJob tells Zapier the moment the event happens, so the Zap starts right away, whatever your plan. The interval grid of the plans, from 15 minutes on Free to 1 minute on Team and Enterprise, only concerns polling triggers, and NiceJob has none. In the editor, a lightning bolt marks a Zap built on an instant trigger.
04What does it take to connect NiceJob to Zapier?
A NiceJob account, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made from the Apps page of your Zapier account: click + Add connection, pick NiceJob, click Add connection, sign in to NiceJob in the tab that opens and grant access. After that, every step that uses NiceJob reuses the same connection, so the account is linked only once.
05Where does the Person ID for NiceJob actions come from?
From an earlier step that holds it. Create Booking, Create Case and Create Visit need a Person ID, and Create Invoice and Create Payment need Person IDs. Another tool will not have that NiceJob ID on its own. One route to test is Find a Person, which looks the person up from an email address; check in the test whether it returns a Person ID before you map it. That search makes the Zap multi-step, so it needs a paid plan.
06What if the NiceJob operation you want is not there?
Then the Zapier integration does not offer it today. The NiceJob page on Zapier shows the current list of triggers, actions and searches, and it is the reference to check before you plan a Zap around a step. Right now it holds two instant triggers on people and reviews, eight actions that create or update records or enroll contacts, and one search on people by email. Check that page again before each new automation.
07Zapier, Make or n8n for NiceJob?
It depends on your criteria, not on a ranking. With Zapier, both NiceJob triggers are instant, so the polling interval does not apply, and two-step Zaps run on the free plan. Most NiceJob actions need a Person ID, though, so when no earlier step holds that ID, a search such as Find a Person has to be tested for it, and a search means a paid plan. If many of your flows need that search, the price of multi-step runs is the point to compare. Check also that the NiceJob operations you rely on exist on the other platform.