Resources · Make integration

JobNimbus Make integrationAutomate JobNimbus with Make.

Can Make keep your JobNimbus contacts, jobs and files in sync without code? The JobNimbus Make integration gives you 12 modules: 3 triggers, 7 actions and 2 searches. This guide shows what each one does, how to plug in your API key and how to run a first scenario.

Try the JobNimbus integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the JobNimbus Make integration do for you?

The JobNimbus Make integration links your JobNimbus account to Make, a no-code tool where you build a scenario, meaning an automation made of modules that pass data to each other. Make can spot new contacts, jobs and activities in JobNimbus, create or update contacts, and store files, all without writing code.

Leads land in JobNimbus on their own. A form in another app collects a request, and Create a Contact turns it into a JobNimbus contact, so nobody retypes a name or phone number.

Every new job reaches the rest of your stack. Watch Jobs picks up each job created in JobNimbus and hands it to the next module, which can post it to a team chat, add a row to a sheet or alert the office manager.

Documents follow the customer. When a signed quote already sits at a public link, Create a File by URL stores it in JobNimbus; List Files and Get a File bring files back out when another tool needs them.

Know the limits before you start. All 3 triggers are scheduled, so Make checks JobNimbus on the scenario's clock instead of being alerted the moment something happens, and they only react to new records. There is no module to create or edit a job; Make an API Call covers that. Make's own documentation for this app also warns that it was written with AI from JobNimbus documentation, so double-check any detail that matters. Plan limits are laid out on Make pricing, and if you are weighing tools, n8n vs Make sets the two side by side. To learn the editor properly, see Make training.

Connect

How do you connect JobNimbus to Make?

  1. 01

    Create an API key in JobNimbus

    In JobNimbus, open Settings, then API, and click New API key. Select a profile, type a name such as Make in the Description box, click save and copy the key JobNimbus displays.

  2. 02

    Add a JobNimbus module in Make

    In your Make scenario, add any JobNimbus module and click Create a connection. A connection is your JobNimbus account linked to Make once, then reused by every JobNimbus module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like; that field is optional. Paste the API key you copied, confirm, and Make can now read and write your JobNimbus data.

First scenario

Your first scenario: new leads become JobNimbus contacts

GoalWhen a new lead arrives in another app, Make creates the matching contact in JobNimbus.

  1. 01

    Start a blank scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your leads arrive first, such as a form tool or a spreadsheet, and connect it.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search JobNimbus and choose Create a Contact. Select your connection or click Create a connection to paste your API key.

  3. 03

    Map the lead's details

    Fill the contact fields Make shows by clicking inside each one and picking the matching value from the previous module. Each bundle, one lead in this case, becomes one contact.

  4. 04

    Test with Run once

    Submit a test lead in your source app, then click Run once. Open the bubble above each module to read the bundles it received, and check the new contact in JobNimbus.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set Scheduling. A new scenario runs every 15 minutes by default. Save, then flip the scenario on so it keeps working without you.

Triggers

Which JobNimbus triggers start a scenario?

3 modules start a scenario when something happens in JobNimbus. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by JobNimbus as soon as it happens.

JobNimbus1Watch Activities

Watch Activities

Scheduled trigger

In Make“Triggers when a new activity has been created.”

This trigger hands your scenario every activity newly logged in JobNimbus, so a note or task added by the team can travel to another tool without anyone copying it over.

How it fires
scheduled. Make checks JobNimbus on the scenario's schedule, which is every 15 minutes by default, and collects the activities created since its last check.
When to use it
pick it when a manager wants a running log of team activity in a shared sheet or chat channel.
Watch out
it only reacts to new activities; an edit to an older one does not start the scenario.
JobNimbus2Watch Contacts

Watch Contacts

Scheduled trigger

In Make“Triggers when a new contact has been created.”

Each contact created in JobNimbus becomes a bundle, one item passed to the next module, so a fresh customer record can flow straight into your mailing tool or accounting app.

How it fires
scheduled. Make polls JobNimbus at the rhythm set on the scenario's clock and returns the contacts added since the previous run.
When to use it
use it when a new contact should also exist somewhere else, such as a newsletter list or an invoicing tool.
Watch out
updates to existing contacts are not picked up, and on the Free plan the shortest gap between two checks is 15 minutes.
JobNimbus3Watch Jobs

Watch Jobs

Scheduled trigger

In Make“Triggers when a new job has been created.”

Watch Jobs sends every newly created JobNimbus job into your scenario, which makes it the natural starting point when the rest of the business needs to know about work that was just booked.

How it fires
scheduled. On every run Make asks JobNimbus which jobs appeared since the last check, following the scenario's schedule.
When to use it
choose it to alert a crew lead in chat or to open a matching folder in a storage app once Make has picked up the new job.
Watch out
Make has no module to create or edit a job afterwards; if you need that, Make an API Call is the route.
Modules

What can JobNimbus modules do in Make?

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

JobNimbus1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new contact to JobNimbus from data your scenario already holds, so a web lead or an imported customer lands in the CRM without manual entry.

When to use it
place it after any module that brings in a new person, like a form submission or a sheet row.
Watch out
it creates a record on every run; put Search Contacts before it if duplicates are a concern.
JobNimbus2

Create a File

Action

In Make“Creates a new file from the provided content.”

Saves a file into JobNimbus from content a previous module produced, such as a PDF generated by a document tool or an attachment pulled from an email.

When to use it
choose it when you hold the file itself inside the scenario rather than a link to it.
Watch out
on the Free plan Make handles files up to 5 MB, so check your plan before sending heavier documents.
JobNimbus3

Create a File by URL

Action

In Make“Creates a new file from the specified file URL.”

Stores a file in JobNimbus straight from a web address, which spares you a download step when the document already lives online, like a signed quote or a photo shared by link.

When to use it
prefer it over Create a File whenever the previous module gives you a link instead of file content.
Watch out
each run stores a new file, so test with Run once on one link before the scenario processes a whole batch.
JobNimbus4

Get a Contact

Action

In Make“Retrieves a contact specified by ID.”

Fetches one JobNimbus contact in full from its ID, so later modules can use its details, for instance to address an email or fill a document template.

When to use it
use it when an earlier module gives you a contact ID and you need the rest of the record.
Watch out
it needs an exact ID; if you only know a name or email, start with Search Contacts.
JobNimbus5

Get a File

Action

In Make“Retrieves a single file specified by ID.”

Retrieves a single JobNimbus file from its ID and passes it on, ready to be emailed, archived in cloud storage or attached somewhere else.

When to use it
reach for it when you already know which file you want, typically after List Files pointed to it.
Watch out
it returns one file per run; to handle a whole set, let List Files feed it.
JobNimbus6

Make an API Call

Action

In Make“Performs an arbitary authorized API call.”

Calls any endpoint of the JobNimbus API with the connection you already set up, which fills the gaps the other 11 modules leave, such as creating or changing a job.

When to use it
use it only when no ready-made module does what you need.
Watch out
you write the request yourself, so keep the JobNimbus API documentation open while you set it up.
JobNimbus7

Update a Contact

Action

In Make“Updates a contact specified by ID.”

Changes an existing JobNimbus contact identified by its ID, so a new phone number or address captured elsewhere reaches the CRM without anyone editing it by hand.

When to use it
use it when another tool becomes the place where customer details get corrected.
Watch out
changes overwrite the stored values, so test with Run once on a sample contact before switching the scenario on.
JobNimbus8

List Files

Search

In Make“Lists all files.”

Returns the files stored in JobNimbus, each one as its own bundle, so you can back them up, sort them or send them to another app in one pass.

When to use it
choose it for a backup or an export where you need every file, not a specific one.
Watch out
every file returned runs the following modules once, and each run counts as an operation on your Make plan.
JobNimbus9

Search Contacts

Search

In Make“Searches for contacts or lists them all.”

Looks through your JobNimbus contacts and hands back the matches, or all of them, so your scenario can check who already exists before it acts.

When to use it
put it in front of Create a Contact or Update a Contact to find the right person first.
Watch out
a search can return zero, one or several contacts, and the next modules run once for each result.
Need help

Need help automating JobNimbus with Make?

A person reads every message.

FAQ

JobNimbus and Make: common questions

01Is the JobNimbus Make integration free?
Yes, on the Make side. JobNimbus is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 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 remove the cap on active scenarios. You still need an active JobNimbus account, which JobNimbus bills separately.
02What do you need to connect JobNimbus to Make?
An active JobNimbus account and an API key. In JobNimbus, go to Settings, then API, click New API key, select a profile, add a description and save, then copy the key shown. In Make, add a JobNimbus module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 12 JobNimbus modules, so you only do this once per account, even when you build several scenarios later.
03How quickly do JobNimbus triggers in Make pick up new records?
It depends on the schedule you set. All 3 JobNimbus triggers, Watch Activities, Watch Contacts and Watch Jobs, are scheduled: Make checks JobNimbus at each run of the scenario rather than being notified by JobNimbus. A new scenario runs every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans can check as often as every minute. None of the JobNimbus modules is an instant trigger.
04What if a JobNimbus module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the JobNimbus API through the same connection, which covers jobs, since the 12 modules can watch new jobs but not create or edit them. You build the request yourself from the JobNimbus API documentation. Make's page on this app notes that it was written with AI from JobNimbus documentation, so confirm details with JobNimbus when something does not behave as described.
05Should you use Make or n8n for JobNimbus?
It depends on what you need and which tool your team already knows. On Make, JobNimbus offers 12 ready-made modules, a fallback through Make an API Call, and a Free plan that is enough to test a first scenario. n8n often has a node for the same app, so check its node list before deciding. Compare the modules each tool offers for your exact workflow rather than the brand, and pick the one whose editor you will keep maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations