JobNimbus

JobNimbus is a field service management and CRM platform built for service-based businesses such as roofing and construction contractors. Its Open API lets you manage jobs, contacts, tasks, activities, estimates, invoices, and files programmatically. Nexla connects to the JobNimbus REST API to ingest these records into your data flows and to write new and updated records back to your JobNimbus account.

Power end-to-end data operations for your JobNimbus API with Nexla. Our bi-directional JobNimbus connector is purpose-built for JobNimbus, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to JobNimbus or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your JobNimbus workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a JobNimbus credential, you need to generate an API key from your JobNimbus account. JobNimbus uses API key authentication for all API requests, with the key sent in the Authorization header using the Bearer prefix. Generating an API key requires customer admin access to your JobNimbus account.

To obtain your JobNimbus API key, follow these steps:

1. Sign in to your JobNimbus account using an account with administrator access.

2. Click the Settings menu in your JobNimbus account.

3. Open the API tab in Settings.

4. Click New API Key to generate a new key.

5. Assign an Access Profile to the key. The Access Profile determines the permissions granted to any software that uses the key. JobNimbus recommends assigning a profile with Full and Settings access so the key can perform all of the operations your integration needs.

6. Enter a description for the key in the Description field (for example, the name of your integration, such as "Nexla Integration"). This helps you identify the key later.

7. Save the key, then copy the generated API key string and store it securely. You will need this value when creating your Nexla credential.

The API key is a customer admin level token that grants permissions based on the Access Profile associated with it. Treat the key as sensitive information and keep it confidential. If the key is compromised, revoke it in the API tab of your JobNimbus Settings and generate a new one. For complete information about creating and managing API keys and using the JobNimbus Open API, see the JobNimbus API key guide, the JobNimbus Open API guide, and the JobNimbus Public API reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Your JobNimbus API key for authentication
Base URL	Yes	No	The base URL for the JobNimbus API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your JobNimbus API key in the API Key field. This key authenticates Nexla with the JobNimbus API and is sent in the Authorization header with the Bearer prefix. Keep this value confidential.

4. Enter the base URL for the JobNimbus API in the Base URL field. The default value is https://app.jobnimbus.com. Use this default unless your account requires a different host.

   The API key is a customer admin level token whose permissions are determined by its assigned Access Profile. If the key is compromised, revoke it in the API tab of your JobNimbus Settings and generate a new one. For more information, see the JobNimbus API key guide.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the JobNimbus connector tile, then select the credential that will be used to connect to the JobNimbus instance, and click Next; or, create a new JobNimbus credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common JobNimbus endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Jobs

Returns a list of all jobs in the JobNimbus account. Use this template to ingest job records for reporting, analytics, or synchronization with other systems.

• This endpoint automatically retrieves all jobs accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Contacts

Returns a list of all contacts in the JobNimbus account. Use this template to ingest contact records for analysis, reporting, or integration with other systems.

• This endpoint automatically retrieves all contacts accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Tasks

Returns a list of all tasks in the JobNimbus account. Use this template to ingest task records for scheduling, reporting, or workflow automation.

• This endpoint automatically retrieves all tasks accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Activities

Returns a list of all activities in the JobNimbus account. Use this template to ingest activity and note records for audit trails, reporting, or integration purposes.

• This endpoint automatically retrieves all activities accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Files

Returns a list of all files in the JobNimbus account. Use this template to ingest file metadata records for cataloging, reporting, or integration purposes.

• This endpoint automatically retrieves all files accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Products

Returns a list of all products in the JobNimbus account. Use this template to ingest product records for catalog management, reporting, or integration purposes.

• This endpoint automatically retrieves all products accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Payments

Returns a list of all payments in the JobNimbus account. Use this template to ingest payment records for financial reporting, reconciliation, or integration purposes.

• This endpoint automatically retrieves all payments accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List Work Orders

Returns a list of all work orders in the JobNimbus account. Use this template to ingest work order records for scheduling, reporting, or integration purposes.

• This endpoint automatically retrieves all work orders accessible to your API key's Access Profile. Nexla handles offset-based pagination automatically to fetch subsequent pages of results.

[Rest API] List or retrieve invoices

List or retrieve invoices from the JobNimbus account. Use this template to ingest invoice records for financial reporting, reconciliation, or integration purposes.

• This endpoint retrieves invoices accessible to your API key's Access Profile.

[Rest API] List or retrieve estimates

List or retrieve estimates from the JobNimbus account. Use this template to ingest estimate records for sales reporting, quoting, or integration purposes.

• This endpoint retrieves estimates accessible to your API key's Access Profile.

[Rest API] Retrieve a single job by ID

Retrieve a single job by ID from the JobNimbus account. Use this template when you need to fetch the details of one specific job rather than the full list.

• Enter the unique identifier of the job to retrieve in the Job ID field. This parameter is required and identifies which job record is returned.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

JobNimbus data sources can also be manually configured to ingest data from any valid JobNimbus API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new JobNimbus data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the JobNimbus destination, and select the Send to Destination option from the menu. Select the JobNimbus connector from the list of available destination connectors, then select the credential that will be used to connect to the JobNimbus account, and click Next; or, create a new JobNimbus credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common JobNimbus endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create a new job record in JobNimbus

Create a new job record in JobNimbus using records from a Nexset. Use this template to automatically add jobs based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new job. The request body must match the format expected by the JobNimbus API.

[Rest API] Update an existing job record

Update an existing job record in JobNimbus using records from a Nexset. Use this template to modify jobs that already exist in your account.

• Enter the unique identifier of the job to update in the Job ID field. This parameter is required and identifies which job record is modified.
• This endpoint sends each record as JSON in the request body to update the specified job.

[Rest API] Create a new contact

Create a new contact in JobNimbus using records from a Nexset. Use this template to automatically add contacts based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new contact. The request body must match the format expected by the JobNimbus API.

[Rest API] Update an existing contact record

Update an existing contact record in JobNimbus using records from a Nexset. Use this template to modify contacts that already exist in your account.

• Enter the unique identifier of the contact to update in the Contact ID field. This parameter is required and identifies which contact record is modified.
• This endpoint sends each record as JSON in the request body to update the specified contact.

[Rest API] Create a new task

Create a new task in JobNimbus using records from a Nexset. Use this template to automatically add tasks based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new task. The request body must match the format expected by the JobNimbus API.

[Rest API] Update an existing task

Update an existing task in JobNimbus using records from a Nexset. Use this template to modify tasks that already exist in your account.

• Enter the unique identifier of the task to update in the Task ID field. This parameter is required and identifies which task record is modified.
• This endpoint sends each record as JSON in the request body to update the specified task.

[Rest API] Create a new activity/note record

Create a new activity or note record in JobNimbus using records from a Nexset. Use this template to automatically log activities based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new activity or note. The request body must match the format expected by the JobNimbus API.

[Rest API] Create a new estimate

Create a new estimate in JobNimbus using records from a Nexset. Use this template to automatically add estimates based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new estimate. The request body must match the format expected by the JobNimbus API.

[Rest API] Create a new invoice

Create a new invoice in JobNimbus using records from a Nexset. Use this template to automatically add invoices based on data from your Nexla flows.

• This endpoint sends each record as JSON in the request body to create a new invoice. The request body must match the format expected by the JobNimbus API.

Manual configuration

JobNimbus destinations can also be manually configured to send data to any valid JobNimbus API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

JobNimbus APIs typically expect JSON format for most operations. For update operations, include the ID of the object to be updated at the end of the URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured JobNimbus endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the JobNimbus endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.