Jobber

Nimbata’s Jobber integration sends your calls to Jobber. When a caller is not one of your Jobber clients yet, Nimbata can create the client, a request and a client note. When the caller is already a client, Nimbata can add a note to their client record, create a request for them, or update their name and billing details. A workflow decides which calls are sent.

Connect Jobber

You can connect from Nimbata, or install Nimbata from Jobber’s App Marketplace. Either way, the connection belongs to the Nimbata project that is open when you finish.

Configure Jobber

Each setup, such as Jobber Settings 1, has two sections: Caller not found, what Nimbata creates when the caller is not a Jobber client, and Caller found, what it does when they are. Nimbata recognises a caller by matching their phone number against your Jobber clients. To send different calls to Jobber in different ways, click Set up Jobber to add another setup; each workflow picks the setup it sends.

Nimbata can write three kinds of Jobber records, each with a fixed set of fields:

Record	Fields
Client	First Name, Last Name, Company Name, Title, Phone, Email, Billing Street 1, Billing Street 2, Billing City, Billing State / Province, Billing Postal Code, Billing Country
Request	Associated Client, Title
Client Note	Associated Client, Message

Each field takes Nimbata call fields (such as Caller ID or Configured Tracking Source), your own text, or both.

1. 1Configure what happens when a new caller reaches you

   In the Caller not found section, click Add object for each record to create, then map its fields. Click Use Default Config (1) to fill in the recommended setup:

   1. A Client named Nimbata Lead, with the caller’s number as its Phone.
   2. A Request for that client, titled New Nimbata Call.
   3. A Client Note on that client with the tracking source and the tracking number’s name.

   A Request or a Client Note needs a client: in Associated Client, the New tab offers New client Id, the client this setup creates first. You can also pick one of your existing clients with Search client.

   Caller not found

   Choose what to create when the caller is not already in Jobber.

   Create

   Client✕

   First Name

   Nimbata✕✕

   Last Name

   Lead✕✕

   Phone

   nCaller ID✕✕

   Create

   Request✕

   Associated Client

   nNew client Id✕✕

   Title

   New Nimbata Call✕✕

   Create

   Client Note✕

   Associated Client

   nNew client Id✕✕

   Message

   Tracking Source:✕nConfigured Tracking Source✕Tracking Number:✕nTracking Number Friendly Name✕✕

   Add objectUse Default Config1

2. 1Configure what happens when an existing client calls

   In the Caller found section, Jobber matches callers against Client records only. Choose how to handle duplicates (1), when the caller’s number is on more than one client: Handle first, Handle all or Ignore all.

   Then add what to do for the matched client. Use Default Config adds a Client Note on the matched client (Associated Client: Matched client Id) with the tracking source and tracking number. You can also:

   • Create a Request for the matched client.
   • Update the Client on its Update tab: its name, company, title and billing address. Nimbata never changes a matched client’s phone numbers or emails.

   Caller found

   Choose what to update when the caller already exists in Jobber.

   If a Caller ID is found in multiple objects, which entity should be enriched?

   Client

   When the same Caller ID is found multiple times within the same object, how would you like our app to handle the call event?

   Handle firstHandle allIgnore all

   1

   CreateUpdate

   Client Note✕

   Associated Client

   nMatched client Id✕✕

   Message

   Tracking Source:✕nConfigured Tracking Source✕Tracking Number:✕nTracking Number Friendly Name✕✕

   Add objectUse Default Config

Test the integration

1. Click Send Test and Save

   Click Send Test and Save at the bottom of the page. A panel opens with a box for each Nimbata field your setup uses, filled in from your project’s latest call.

2. Send a test event

   Change the values if you like, keep a Caller ID, and click Send event. The test runs exactly like a call and writes real records in Jobber: if the Caller ID matches a client, your Caller found actions run, otherwise your Caller not found actions. The panel lists the result of each record, such as “Client created successfully. ID: …”, or “Nothing to do.” when that path has no records set up.

3. Save the setup

   Click Save, and delete any test records you do not want to keep in Jobber.

Send calls with a workflow

Nimbata sends a call to Jobber when a workflow with a Jobber action runs for it. A workflow that runs when a call ends, with no filter, sends every call, and its filters (for example call outcome or tracking number) narrow it down. Jobber is available in workflows for inbound and outbound calls, not for forms or text messages.

1. Create a workflow

   Go to Workflows, click Create and choose From Scratch. Keep the Inbound Call trigger with Call Ends, and add any filters you need.

2. 1Add the Jobber action

   Click the + plus sign, select Perform action, and choose Jobber under Integrations. Pick your setup under Select configuration (1), then click OK.

   JobberConfigure

   ✕

   Jobber Settings 1×✕1

   OK

3. 1Enable the workflow

   Click Enable (1).

   Jobber callsWorkflow is valid.

   Enable1

   Trigger Enrollment

   Inbound CallOutbound CallForm SubmissionSMS Received

   A customer calls your tracking number

   Fires whenCall StartsCall EndsUser Updates Property

   Action group1

   JobberJobber Settings 1✕

   Add another action

   Finish

Detailed guide: Create a workflow

Check it worked

The Jobber page now shows the workflow that uses the integration. Place a test call to one of your tracking numbers: once it ends, the client, request or note appears in Jobber.

Jobber

Harbor & Pine Plumbing

Create clients, requests, and notes in Jobber automatically when your phone rings.

Used in 1 workflow

Events are sent when an inbound call ends.

Manage workflows+ Create

Set up Jobber

Jobber Settings 13 actions configuredJobber calls

Disconnect Jobber

• In Nimbata: open the three-dot menu at the top of the Jobber page and click Disconnect. Nimbata also disconnects its app in Jobber, unless another of your projects still uses the same Jobber account. Your setups are kept, so you can reconnect later.
• In Jobber: disconnecting Nimbata from Jobber disconnects every Nimbata project that uses that Jobber account. Their setups are kept too.
• Remove the setup: Remove setup, in the same menu, permanently deletes the project’s Jobber setups and connection. It is greyed out while workflows use Jobber.

Limitations

• Nimbata writes Clients, Requests and Client Notes only, with the fields listed above. It does not write properties, quotes, jobs or custom fields.
• Requests and Client Notes are only ever created, never updated.
• Updating a matched client never changes its phone numbers or emails.
• Jobber receives calls only: form submissions and text messages cannot be sent to it.

Troubleshooting

You don’t see Jobber on the Integrations page

Jobber is not yet available on every Nimbata account. If your plan doesn’t include it, Go to integration on the tile offers an upgrade instead of opening the page.

The Jobber tile says Disconnected

Nimbata has lost its connection to Jobber, for example because Nimbata was disconnected in Jobber. Your Jobber settings are saved, but nothing is sent until you reconnect: open the integration and click Reconnect in the red Disconnected. banner.

Integrations

JobberDisconnected

Create clients, requests, and notes in Jobber automatically when your phone rings.

Go to integration

A test or a call reports an error

Message	What to do
Please provide a valid caller id	Fill in the Caller ID box in the test panel.
Client requires a name or a phone number	Map First Name, Last Name, Company Name or Phone on the Client.
Request requires an associated client	Set Associated Client on the Request: New client Id under Caller not found (with a Client created above it), or Matched client Id under Caller found.
Note requires an associated client	Set Associated Client on the Client Note, as for a Request.
Client update skipped: no fields to update.	The Client’s Update tab has no fields mapped. Map one, or remove the Client from Caller found.
Note skipped: message is empty.	The note’s Message was empty for this call. Add text or fields that always have a value.
Jobber is not connected. Connect Jobber again to continue.	Reconnect Jobber, as above.

A caller who is already a client gets a new client

• Check that the client’s phone number in Jobber matches the caller’s number: Nimbata compares the last 7 to 10 digits.
• Check that Caller found has the records you want, so a match has something to do.

Calls are not reaching Jobber

• Check that a workflow with a Jobber action is enabled, and that its filters let the call through.
• Check that the workflow’s Jobber action uses the setup you configured, under Select configuration.
• Check that the Jobber tile does not say Disconnected.
• Send a test from Send Test and Save to see the error Jobber returns.