Skip to main content

JobNimbus: Connect Your Account

This guide walks you through connecting your JobNimbus (JN) account to AutoRev so your AI receptionist can create customers, book jobs, and push estimates into JobNimbus.

Estimated time: 5 minutes.

Why connect JobNimbus​

  • Your AI receptionist creates real customers and jobs in JobNimbus when callers book.
  • The AI looks up callers by phone and pulls their full JobNimbus history into the call so it can answer "where are you with my roof?" without putting the customer on hold.
  • Estimates the AI builds during the call get pushed into JobNimbus as drafts your sales team can finalize and send.
  • Daily KPIs (leads, jobs, revenue) flow from JobNimbus into your AutoRev dashboard.

Step 1: Get your JobNimbus API key​

JobNimbus uses a single API key per user.

  1. Log into JobNimbus at app.jobnimbus.com.

  2. Click your name or profile icon in the top right.

  3. Click Settings.

  4. In the left sidebar, look for API (sometimes nested under Integrations or Developer).

  5. Click API Access or Generate API Key.

  6. Click Generate New Key (or Reveal Key if one is already there).

  7. Copy the API key. It looks like a long random string.

  8. Note your JobNimbus User Email (the email on the account that owns this key). Some API calls are scoped to the issuing user.

Save the key somewhere safe.

Step 2: Required permissions​

JobNimbus API keys inherit the permissions of the user who created them. To give AutoRev full power, the user who generates the key should have these permissions in JobNimbus:

  • Contacts — view, create, edit. So the AI can create new customer records.
  • Jobs — view, create, edit. So the AI can book new jobs.
  • Estimates — view, create, edit. So the AI can push draft estimates.
  • Invoices — view. So the AI can quote outstanding balances.
  • Tasks — view, create. So the AI can create follow-up tasks for your sales team.
  • Notes — create. So the AI can log call summaries.

Tip: the cleanest setup is to create a dedicated JobNimbus user called something like "AutoRev AI" with admin or near-admin permissions, then generate the API key from that user's account. This way, every action the AI takes in JobNimbus is clearly labeled as having come from "AutoRev AI" in your audit log, separate from your real humans.

Step 3: Connect to AutoRev​

Once you have your JobNimbus API key:

In the AutoRev dashboard, go to Settings > Integrations, open the card for this integration, paste your credentials, and click Connect. Credentials are validated live against the provider before anything is saved. (If you use AutoRev through the Claude connector, you can also just ask Claude to connect it for you.)

How to test the connection​

After connecting, the card shows the live connection state. The connect step already validated your credentials with a real API call, so a green card means you are live.

A note for power users: v1 vs v2 endpoints​

JobNimbus runs two API versions side by side. AutoRev's integration uses the newer /v2/ paths where available, and falls back to v1 for endpoints that have not been ported yet. You do not need to do anything special, both are gated by the same API key. We mention it only so you are not surprised if you see /v2/ paths in your AutoRev audit log.

Common issues​

"401 Unauthorized" error The API key was copied incorrectly, or the user who created the key was deactivated in JobNimbus. Regenerate the key in JN and reconnect.

"403 Forbidden" on specific actions (e.g., creating an estimate works but recording a payment fails) The user who generated the key does not have the required permission for that specific action in JobNimbus. Check their JN role and add the missing permission. The key picks up the new permission within a few minutes, no need to regenerate or reconnect.

The AI created a contact in JobNimbus but the address is missing or wrong JobNimbus has separate fields for billing address, service address, and contact address. The AI fills in service address from the call. If you want a different field populated, ask Claude to walk you through which address field to default to.

Jobs are being created without a status JobNimbus requires every job to have a workflow status. AutoRev defaults to "New Lead" or "Estimate Requested" depending on the call type. If your JobNimbus workflow uses custom status names, ask Claude to map them: "I want new AI bookings to start in the 'Phone Inquiry' status, not 'New Lead'."

The AI says JobNimbus is connected but list_jobs returns 0 results The API key user's view permissions in JobNimbus are scoped to certain teams or territories. Make sure the user can see jobs across all teams you want the AI to know about. The cleanest fix is using an admin-level user for the API key.

Need help?​

Email support@autorev.ai or ask Claude "I'm having trouble with my JobNimbus integration."