JobNimbus is a CRM and project management software designed for contractors, helping streamline scheduling, estimates, invoicing, and job tracking.
JobNimbus is a CRM and project management software designed for contractors, helping streamline scheduling, estimates, invoicing, and job tracking. On Nagent, JobNimbus is exposed as a fully-configurable crm integration that any agent can call — 21 actions, and API key authentication. No code is required to wire JobNimbus into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use JobNimbus to automate the kinds of tasks crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire JobNimbus into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against JobNimbus, with input parameters and output schema. Drop these into any step of an agent built in Helix.
JOBNIMBUS_ACCOUNT_CREATE_LOCATIONTool to create a new location in JobNimbus. Use after gathering address and contact details.
Input parameters
Postal code for the location
City of the location
Short code or abbreviation for the location
Name of the location
Phone number for the location
Whether the location is active
State or province of the location
Country of the location
First line of the location's address
Second line of the location's address
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_ACCOUNT_GET_SETTINGSTool to retrieve account-wide settings (workflows, types, sources). Use after authenticating to load or refresh workflow and source mappings.
Input parameters
Optional JobNimbus user email to impersonate this request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_ACTIVITY_GETRetrieves a specific JobNimbus activity by its unique jnid. Activities in JobNimbus represent logged events such as task modifications, contact updates, job creation, and other system actions. Each activity contains details about what changed, who made the change, and when it occurred. Use this action when you need detailed information about a specific activity, such as viewing the full history of changes or understanding who performed an action.
Input parameters
The unique JobNimbus ID (jnid) of the activity to retrieve. This is a hexadecimal string identifier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CONTACT_GETTool to retrieve a contact by ID. Use after obtaining the contact’s jnid to fetch full details.
Input parameters
The JobNimbus ID (jnid) of the contact to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CONTACT_LISTTool to list all contacts. Use when you need to fetch multiple contacts, e.g., for reporting or synchronization.
Input parameters
Zero-based offset for pagination. Defaults to 0.
Maximum number of contacts to return (>=1). Defaults to 1000.
Comma-separated list of contact fields to include. Defaults to all fields.
URL-encoded JSON filter for advanced querying.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CONTACT_UPDATETool to update an existing contact. Use when you have a contact's JNID and need to modify its fields. Call after fetching or creating a contact.
Input parameters
ZIP code of the contact
City of the contact
Unique JobNimbus identifier of the contact to update
Tags associated with the contact
Email address of the contact
Company name associated with the contact
Website URL
Last name of the contact
Fax number
First name of the contact
Home phone number
State of the contact
Work phone number
External identifier
Source from which the contact originated
Status of the contact
Type/category of the contact (record type name)
Internal notes or description
Display name of the contact
Mobile phone number
Address line 1
Address line 2
Name of the sales representative
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CREATE_FILE_TYPECreates a new file attachment type in JobNimbus. File types are custom categories used to organize and classify document attachments (e.g., contracts, warranties, photos, permits). You must create a file type before you can upload files with that category.
Input parameters
Whether the file type should be active and available for use immediately. Defaults to True.
The name for the new file attachment type (e.g., 'Contract', 'Warranty', 'Photo Gallery'). This will be used to categorize files in JobNimbus.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CREATE_MATERIAL_ORDERCreates a new material order in JobNimbus. A material order tracks materials needed for a job and can be submitted to suppliers. Material orders must be linked to a contact or job record and include at least one line item referencing an existing product from your Products & Services catalog. Prerequisites: - At least one contact or job record must exist (use JOBNIMBUS_CONTACT_LIST to find contacts) - Products must exist in your catalog (use JOBNIMBUS_LIST_PRODUCTS to find product IDs) Note: Custom line items are not supported - all items must reference existing products by their jnid.
Input parameters
List of items to include in this material order (at least one required). Each item must reference an existing product by its jnid.
Optional notes or comments about the order.
Optional material order number.
Numeric status code of the material order (0-7). Use 0 for Draft.
List of related jobs or contacts (at least one required). Material orders must be linked to a job or contact record.
Identifier of the vendor for this order.
User ID to whom this order is assigned.
Expected delivery date in ISO 8601 format (YYYY-MM-DD).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CREATE_TASKTool to create a new task. Use when scheduling or tracking tasks linked to contacts or jobs.
Input parameters
Title of the task.
List of related records (contacts or jobs) to attach this task to.
End date as a Unix timestamp (seconds since epoch). Use 0 or omit for open-ended tasks.
Start date as a Unix timestamp (seconds since epoch).
Numeric identifier of the task type.
Name of the task type as defined in account settings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_CREATE_WORKFLOW_STATUSTool to create a new status in an existing workflow. Use after confirming the workflow ID to add specialized status entries like 'Lead' or 'Inspection'.
Input parameters
Display name of the new status
Whether this status marks a lead
Whether the status is active
Whether this status marks closure
ID of the target workflow (obtained from JOBNIMBUS_ACCOUNT_GET_SETTINGS)
Whether this status should be archived
Whether to force mobile sync on status change
Whether to sync this status to QuickBooks
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_FILE_GETRetrieves the raw content of a specific file attachment from JobNimbus by its unique ID. This action downloads the actual file content (binary data for PDFs, images, etc.) but does NOT return file metadata like filename, content type, or size. If you need metadata, use the files list endpoint instead. Common use case: Download a file attachment after obtaining its jnid from a list files query or from a related record (contact, job, etc.).
Input parameters
The unique JobNimbus ID (jnid) of the file attachment to retrieve. This ID can be obtained from file list endpoints or from related record responses.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_ACTIVITIESTool to retrieve all activities. Use after authentication to fetch a paginated list of activities.
Input parameters
Maximum number of activities to return (>=1). Defaults to 1000.
URL-encoded JSON filter for advanced querying.
Zero-based offset for pagination. Defaults to 0.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_INVOICESTool to list all invoices (v2). Use when you need to fetch multiple invoice records.
Input parameters
Zero-based offset for pagination. Defaults to 0.
Maximum number of invoices to return (>=1). Defaults to 1000.
Comma-separated list of invoice fields to include. Defaults to all fields.
JSON filter for advanced querying (e.g., filter by status_name, customer, etc.). Note: May require proper URL encoding depending on API implementation.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_MATERIAL_ORDERSTool to list all material orders (v2). Use after authentication to fetch multiple material order records.
Input parameters
Zero-based offset for pagination. Defaults to 0.
Maximum number of material orders to return (>=1). Defaults to 1000.
Comma-separated list of material order fields to include. Defaults to all fields.
URL-encoded JSON filter for advanced querying.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_PAYMENTSTool to retrieve payments list with optional filters. Use after auth.
Input parameters
Page number for pagination (>=1). Defaults to 1.
Filter payments by associated job ID.
End date (YYYY-MM-DD) filter.
Number of payments per page (>=1). Defaults to 100.
Start date (YYYY-MM-DD) filter.
Filter payments by associated contact ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_PRODUCTSTool to list all products. Use after authentication to fetch full product catalog.
Input parameters
Zero-based offset for pagination. Defaults to 0.
Maximum number of products to return (>=1). Defaults to 1000.
Comma-separated list of product fields to include. Defaults to all fields.
URL-encoded JSON filter for advanced querying.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_LIST_WORKORDERSTool to retrieve all work orders (v2). Use after authentication when you need a paginated list of work orders.
Input parameters
Zero-based offset for pagination. Defaults to 0.
Maximum number of work orders to return (>=1). Defaults to 1000.
Comma-separated list of work order fields to include. Defaults to all fields.
URL-encoded JSON filter for advanced querying.
Field to sort results by. Defaults to 'date_created'.
Sort order: 'asc' or 'desc'. Defaults to 'desc'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_PRODUCT_GETRetrieves detailed information about a specific JobNimbus product using its jnid. Use this action when you need to get full details about a product, including pricing, cost, unit of measurement, and tax settings. Obtain the jnid first using the List Products action.
Input parameters
The JobNimbus product ID (jnid) to retrieve. A 22-character alphanumeric identifier.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_TASK_LISTTool to list all tasks. Use when you need an overview of tasks for planning or review.
Input parameters
Page number of results (1-indexed).
Filter tasks by status.
Filter by due date in YYYY-MM-DD format.
Number of results per page.
Filter by assigned user ID.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_UPDATE_TASKUpdate an existing JobNimbus task by its jnid. Allows updating task details like title, description, dates, priority, and task type. Use List Tasks action to find task jnids. Note: To update task type, both record_type and record_type_name must be provided together.
Input parameters
JobNimbus ID (jnid) of the task to update. Obtain from List Tasks or Create Task actions.
New title for the task
New end timestamp in Unix epoch seconds
Task priority: 0=none, 1=high, 2=medium, 3=low
New start timestamp in Unix epoch seconds
New description or notes for the task
Task type ID. Must be provided with record_type_name if updating task type.
Task type name. Must be provided with record_type if updating task type.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
JOBNIMBUS_UTILITY_GET_UOMSTool to retrieve list of supported units of measure. Use after authenticating when you need to present or validate measurement units.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 73 agents privately built on Nagent that already use JobNimbus.
Build on Nagent
Connect JobNimbus to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find JobNimbus, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, JobNimbus is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once JobNimbus is connected, you configure its 21 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop JobNimbus steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a JobNimbus event fires, the agent kicks off automatically.
Every JobNimbus action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While JobNimbus ships with 21 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching JobNimbus together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build JobNimbus-based workflows tailored to your business.