Resources · Zapier integration

JobNimbus Zapier integrationAutomate JobNimbus with Zapier.

The JobNimbus Zapier integration gives you 2 triggers, 6 actions and 2 searches. Both triggers are instant, so a new contact or job reaches your other tools right away, even on the free plan. Here is what each step does, costs and breaks.

See the 10 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the JobNimbus Zapier integration actually does

Zapier is a tool that links apps together without code. Hooked to JobNimbus, it watches your contacts and jobs, and the moment one is created, changed or deleted it can push that record somewhere else. It can also go the other way: create contacts, jobs and attachments in JobNimbus from a form, a sheet or an inbox.

Three results people usually build first. A clean lead intake: a web form answer becomes a JobNimbus contact through Create Contact, with no retyping. A job board your office can read: every new or edited job, caught by Job Created, Modified or Deleted, lands as a row in a shared sheet or a message in your team chat. Documents filed on the right record: a signed quote or a site photo arriving elsewhere gets attached to the matching contact or job with Create Attachment.

What Zapier does not do here. The only triggers watch contacts and jobs; nothing else in JobNimbus can start a Zap. There is no delete action, and no search for jobs: you can look up a contact by email or by ID, nothing else. Updates exist for contacts only, so changing a job's status from another app is out of reach with this integration.

If the same flow fits better elsewhere, compare it with the JobNimbus Make integration, or read the n8n vs Zapier breakdown before you commit.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are in plain English.

Zap
The automation you build on Zapier: one event that starts it, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it to happen.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills you for: one action that your Zap completed successfully. Your plan counts these each month.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is pushed by the app itself the moment the event occurs, with no waiting.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it quietly otherwise.
Search step
A step that looks up a record that already exists, such as a contact, so the next steps can reuse what it found.
Cost

What a JobNimbus Zap really costs

JobNimbus is not a premium app on Zapier, so it works from the free plan. What you pay for is tasks, not triggers.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger costZero tasks
  • Filter or searchMakes it multi-step, paid plan

The trigger never costs a task, and neither does Zapier checking for new data. Each action that succeeds counts once, so a Zap with three actions uses three times more than a Zap with one. A failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a filter, a search or a second action and it becomes a multi-step Zap, which needs a paid plan. A few apps and actions count more than one task per run.

Connect

Connect your JobNimbus account in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your JobNimbus account linked once, then reused by every Zap that touches it.

  2. 02

    Pick JobNimbus

    Type JobNimbus in the search box of the dialog, select it, then click Add connection. A new tab opens on the JobNimbus side, where the rest of the setup happens.

  3. 03

    Sign in and allow access

    Log in to JobNimbus in that tab and grant Zapier access to the account. You need your own JobNimbus account, plus read or write rights on any record you do not own and want the Zap to touch.

First Zap

Your first Zap: log every new JobNimbus job in a sheet

GoalEach time a job is created, edited or deleted in JobNimbus, add a row to a Google Sheets tracker, but only for the jobs that meet your condition.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose JobNimbus as the app and Job Created, Modified or Deleted as the event. Pick your JobNimbus connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent jobs from your account, so pick a real one to map from rather than an empty sample.

  3. 03

    Add the filter

    Since this trigger also fires on edits and deletions, add a Filter from the plus icon. Set the field, the rule and the value, then Configure & test. This makes the Zap multi-step.

  4. 04

    Add the action and map fields

    Add Google Sheets as the action app, choose the sheet, and map the job details you need from the JobNimbus step into the right columns.

  5. 05

    Test, then publish

    Test the action once and check the new row in your sheet. If it looks right, click Publish to switch the Zap on. From then on, every job that passes the filter lands in the sheet.

Triggers

JobNimbus triggers

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

1

Contact Created, Modified or Deleted

Instant trigger

In Zapier“Trigger when a new contact is created, modified or deleted.”

Starts your Zap whenever a contact in JobNimbus is added, edited or removed. One trigger covers all three events, so one Zap can keep another tool in step with every change to your customer list.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping a mailing list, a phone dialer or a spreadsheet in step with your customer base without exporting by hand.
Watch out
since edits and deletions also fire it, a Zap that should react to only some of those events needs a filter, which pushes it onto a paid plan.
2

Job Created, Modified or Deleted

Instant trigger

In Zapier“Trigger when a new job is created, modified or deleted.”

Kicks off a Zap each time a job in JobNimbus is opened, changed or dropped. For a crew business, that is the heartbeat of the pipeline: a job moving is usually what the office, the crew lead and the accountant all need to hear about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
pinging the crew channel or updating a scheduling board as soon as a roof inspection turns into a signed job.
Watch out
if a later step writes back to the same job, the edit fires the trigger again and the Zap can loop.
Actions

JobNimbus actions

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

1

Create Attachment

Action

In Zapier“Creates a new attachment.”

Drops a file onto an existing contact, job or task in JobNimbus, so documents end up next to the record they belong to.

When to use it
filing a signed estimate from your e-signature tool straight onto the matching job.
Watch out
it needs the file, a filename with its extension, and the ID of the record to attach it to.
2

Create Contact (Legacy)

Action

In Zapier“Creates a new contact.”

The older way to add a contact to JobNimbus, kept so existing Zaps keep running.

When to use it
only when you maintain a Zap that already relies on it.
Watch out
for any new Zap, pick Create Contact instead, the version that handles the display name.
3

Update Contact (Legacy)

Action

In Zapier“Update an existing contact.”

The original edit step for a JobNimbus contact, still listed for Zaps built before the newer version arrived.

When to use it
leave it in place on old Zaps that work, and build new ones on Update Contact.
Watch out
it requires the JobNimbus contact ID, so an earlier step has to supply it.
4

Update Contact

Action

In Zapier“Update an existing contact with Display Name.”

Changes the details of a contact already in JobNimbus, display name included, without opening the CRM.

When to use it
a customer corrects their phone number through a form, and the CRM record follows.
Watch out
it needs the contact ID; chain it after Find Contact by Email to get one.
5

Create Contact

Action

In Zapier“Creates a new contact with Display Name.”

Adds a new person or company to JobNimbus with its display name, the current version of the contact creation step.

When to use it
every quote request from your website or ad form should become a contact the sales rep can call.
Watch out
if the same lead can come back, run Find Contact by Email first so you update the existing card instead.
6

Create Job

Action

In Zapier“Creates a new job, requiring a Contact ID from Create Contact.”

Opens a new job in JobNimbus, tied to a contact that must already exist.

When to use it
a booked inspection in your calendar tool should turn into a job on the right customer.
Watch out
it requires a contact ID, typically the one returned by Create Contact or a search earlier in the same Zap.
Searches

JobNimbus searches

2 search steps look for data that already exists in JobNimbus, so a later step can use it.

Searches sit at the bottom of the action list in the editor, under SEARCH. They find a contact that already exists so a later step can use its ID. Some action fields also offer + Add search step, which inserts one and wires it in for you. Three settings decide what happens when the search does not find exactly one match.

1

Find Contact by Email

Search

In Zapier“Search for a JobNimbus contact by Email.”

Looks through JobNimbus for the contact matching an email address and hands back that record, ID included.

When to use it
a returning customer fills in a form again, and you want to update them instead of creating a second card.
Watch out
the email is the only input; if nothing comes back, the setting below decides whether the Zap stops or carries on.
2

Find Contact by ID

Search

In Zapier“Search for a JobNimbus contact by ID.”

Fetches the full JobNimbus contact behind an ID you already hold, for example one returned by Create Contact or another search.

When to use it
you hold a contact ID from an earlier step and need the rest of the record for the next one.
Watch out
without that ID from a previous step, this search has nothing to look up.

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 skips the steps that depended on it. Switched on, the Zap carries on without the contact.
  2. Create X if it doesn't exist yet?
    Not offered for JobNimbus searches: neither of them has a find-or-create version, so a missing contact has to be created in a separate step.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on to the following steps at once.
When it breaks

When a JobNimbus Zap breaks

Zapier links no help article to JobNimbus, so the known failure points are the general ones. They still bite.

Most broken JobNimbus Zaps come from four situations. If you are stuck on one that is not listed here, our Zapier troubleshooting page walks through the usual fixes.

  • Old contacts and jobs are ignored

    A Zap only reacts to what happens after you switch it on. Records already in JobNimbus are never picked up; moving that backlog is a separate job.

  • The Zap keeps firing itself

    Both triggers fire on edits. A Zap that updates the contact or job it was started by sets itself off again and burns through your tasks fast.

  • A bulk import goes missing

    After a mass import into JobNimbus, a sudden flood of events can be held back by Zapier's flood protection instead of running one by one.

  • No ID, no action

    Create Job, Update Contact and Create Attachment fail when the required ID is empty. Check that a search or creation step really returned it.
Need help

Need help automating JobNimbus with Zapier?

A person reads every message.

FAQ

JobNimbus Zapier integration: FAQ

01Is the JobNimbus Zapier integration free?
Yes, as long as you stay within the free plan's limits. JobNimbus is not a premium app on Zapier, so you can connect it without paying. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap can only have two steps: one trigger and one action. As soon as you add a filter, a search such as Find Contact by Email, or a second action, the Zap becomes multi-step and needs a paid plan. You also need your own JobNimbus account.
02How many tasks does a JobNimbus Zap use?
One per action that succeeds, and nothing for the trigger. If a new job starts your Zap and the Zap adds one row to a sheet, that run costs one task. If the same Zap also posts a message and creates an attachment, it costs three. Actions that fail are not counted. Zapier checking for new data never costs anything either. Keep in mind that a Zap which updates the contact it was started by can loop, and each loop eats tasks.
03Is the JobNimbus Zapier integration real time?
Yes for both triggers. Contact Created, Modified or Deleted and Job Created, Modified or Deleted are instant: JobNimbus tells Zapier as soon as the event happens, so the Zap starts right away, whatever your plan. The polling intervals of the plans, 15 minutes on Free and down to 1 on Team and Enterprise, do not apply to them. In the editor, an instant trigger shows a lightning bolt, which is a quick way to confirm it before you publish.
04What does it take to connect JobNimbus to Zapier?
A JobNimbus account you can sign in to, and a Zapier account. From the Apps page in Zapier, add a connection, pick JobNimbus, log in in the tab that opens and allow access. If your Zap needs to touch contacts or jobs that belong to a colleague, your JobNimbus user needs read or write rights on them. Once linked, the same connection is reused by every Zap you build with JobNimbus.
05Why does Create Job ask for a contact ID?
Because in JobNimbus every job hangs off a contact, and this action will not guess which one. The action expects the contact's JobNimbus ID. In practice you get it from an earlier step in the same Zap: either Create Contact just before, which returns the new ID, or Find Contact by Email when the customer already exists. Both routes add a step, which makes the Zap multi-step and therefore a paid-plan Zap.
06What if the JobNimbus action you want is not in Zapier?
Then this integration cannot do it directly. There is no action to update or delete a job, and the only triggers watch contacts and jobs. One option is to build around what exists, for instance by triggering on job changes and acting in another tool. Another is to compare the same workflow on Make or n8n, whose JobNimbus modules may cover different ground. Check the action list before designing a process that depends on a missing step.
07Zapier, Make or n8n for JobNimbus?
Start from the operations, not the brand. On Zapier, JobNimbus offers 2 instant triggers that fire straight away even on the free plan, 6 actions and 2 contact searches, but no job update and no job search. If your workflow needs one of those missing steps, check what Make and n8n offer for JobNimbus before you build. If what you need is in the list above, Zapier lets you start without paying, as long as each Zap stays at one trigger and one action.
Same platform

Other docs you might need on this stack.

Browse all integrations