JobNimbus
JobNimbus is a CRM and project management software designed for contractors, helping streamline scheduling, estimates, invoicing, and job tracking.
Verdict
Common use cases
- Log new leads from discovery calls
- Create tasks for site inspections mid-conversation
- Pull contact details before client meetings
- Place material orders after estimate approval
- Check workflow statuses during project reviews
Integration
- Vendor
- JobNimbus
- Category
- crm
- Auth
- API_KEY
- Tools
- 21
- Composio slug
jobnimbus
Tools
- Create File Attachment Type
Tool to create a new file attachment type. use when you need to register a custom document category before uploading files.
- Create Location
Tool to create a new location in jobnimbus. use after gathering address and contact details.
- Create Material Order
Tool to create a new material order (v2). use when you need to place a materials order for a contact after gathering item details.
- Create Task
Tool to create a new task. use when scheduling or tracking tasks linked to contacts or jobs.
- Create Workflow Status
Tool to create a new status in an existing workflow. use after confirming the workflow id to add specialized status entries like 'lead' or 'inspection'.
- Get Account Settings
Tool to retrieve account-wide settings (workflows, types, sources). use after authenticating to load or refresh workflow and source mappings.
- Get Activity by ID
Tool to retrieve a specific activity by its id. use after confirming the activity's jnid is valid.
- Get Contact by ID
Tool to retrieve a contact by id. use after obtaining the contact’s jnid to fetch full details.
- Get File Attachment by ID
Tool to retrieve a specific file attachment's raw content by id.
- Get Product by ID
Tool to retrieve a specific product by id (v2). use after confirming the product's jnid to fetch its details.
- Get Units of Measure
Tool to retrieve list of supported units of measure. use after authenticating when you need to present or validate measurement units.
- List Activities
Tool to retrieve all activities. use after authentication to fetch a paginated list of activities.
- List Contacts
Tool to list all contacts. use when you need to fetch multiple contacts, e.g., for reporting or synchronization.
- List Invoices
Tool to list all invoices (v2). use when you need to fetch multiple invoice records.
- List Material Orders
Tool to list all material orders (v2). use after authentication to fetch multiple material order records.
- List Payments
Tool to retrieve payments list with optional filters. use after auth.
- List Products
Tool to list all products. use after authentication to fetch full product catalog.
- List Tasks
Tool to list all tasks. use when you need an overview of tasks for planning or review.
- List Work Orders
Tool to retrieve all work orders (v2). use after authentication when you need a paginated list of work orders.
- Update Contact
Tool 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.
- Update Task
Tool to update an existing task. use after confirming the task’s jnid and desired changes.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for JobNimbus and click Connect. 3. You'll be prompted to paste your JobNimbus API key — generate one by logging into JobNimbus, going to Settings > API, and creating a new key with read and write permissions. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Switchy will confirm the connection by fetching your account settings (workflows, contact types, lead sources). 6. To test, open any Space and type '@JobNimbus get account settings' — you should see a list of your active workflows and statuses. 7. Now you can create contacts, tasks, or material orders by @mentioning JobNimbus and describing what you need in plain language.
What teammates see: by default, memories from JobNimbus are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Log New Lead
@JobNimbus create a new contact for Sarah Chen at 482 Maple Drive, Portland OR 97202. Phone is 503-555-0147. Tag this as a referral lead for roof replacement.Open in a Space →
Schedule Site Visit
@JobNimbus create a task called 'Initial site inspection' for contact ID 12849, due next Tuesday at 10am. Assign it to Mike and mark priority as high.Open in a Space →
Order Materials
@JobNimbus create a material order for contact ID 12849. Line items: 40 bundles asphalt shingles, 12 rolls underlayment, 8 boxes ridge cap. Ship to job site address on file.Open in a Space →
Retrieve Contact Info
@JobNimbus get contact details for ID 12849. Show me their address, phone, email, and any linked jobs or open tasks.Open in a Space →
Check Workflow Stages
@JobNimbus get account settings and list all workflow statuses. I need to see what stages are available for our roofing pipeline.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@JobNimbus show me all open tasks assigned to our roofing crew this week, grouped by job priority
Based on the current task data, you have 14 open tasks assigned to the roofing crew through Friday. High-priority jobs include the Miller residence re-roof (inspection due Tuesday, materials delivery Wednesday) and the Oakwood Commons commercial project (final walkthrough Thursday). Medium-priority tasks cover three residential repairs and one gutter replacement. All crew members have balanced workloads except Jake, who's carrying two extra site visits. This example illustrates how JobNimbus surfaces task assignments and job context—actual results depend on your account's task structure and custom fields.
This example demonstrates JobNimbus's strength in surfacing CRM task data for field service scheduling. Requires read access to tasks and contacts. The MCP can filter and group results, but complex crew-capacity logic may need multiple tool calls. Rate limits apply to bulk task queries—expect slower responses for accounts with 100+ active tasks.
@JobNimbus create a new contact for Sarah Chen at 482 Maple Drive, then add a task to call her Thursday about the roof estimate
Contact created successfully. Sarah Chen is now in your JobNimbus account with the Maple Drive address and a mobile number placeholder (you can update this later). I've also created a task titled 'Call Sarah Chen - Roof Estimate' scheduled for Thursday at 10 AM, assigned to your default sales rep. The task is linked to Sarah's contact record so notes and follow-ups stay connected. This example shows how JobNimbus handles sequential create operations—real workflows often require setting contact type, lead source, and workflow status at creation time.
This example highlights JobNimbus's write capabilities for contact and task creation, common in lead-intake workflows. Requires API key with create permissions for both contacts and tasks. The MCP will use your account's default workflow and status unless you specify them in the prompt. Side-effect: creates permanent records—no undo via MCP.
@JobNimbus pull the last 30 days of completed jobs, then draft a summary email for our investors showing total revenue and top three project types
Over the past 30 days, your team completed 47 jobs totaling $284,600 in invoiced revenue. The top three project types were residential re-roofs (18 jobs, $142K), commercial gutter systems (9 jobs, $76K), and storm damage repairs (12 jobs, $51K). Average job value was $6,055, up 12% from the prior month. Residential work drove the majority of volume, while commercial projects had higher per-job margins. This example demonstrates how JobNimbus data pairs with AI synthesis—actual revenue figures depend on your invoice records and job-type taxonomy being up to date in the CRM.
This example showcases JobNimbus's reporting data combined with AI-driven summarization, useful for investor updates or pipeline reviews. Requires read access to jobs and financial records. The MCP retrieves raw job data; the AI handles aggregation and narrative framing. Be aware that JobNimbus's date filters and custom fields vary by account—confirm your job records include revenue data before relying on this workflow.
Use-case deep-dives
When JobNimbus MCP wins for field service scheduling
A 6-person roofing company runs morning dispatch from Slack. The crew lead asks Switchy to pull today's jobs, check material orders, and create follow-up tasks for incomplete inspections. The JobNimbus MCP handles this because it exposes task creation, contact lookup, and material order tools in one integration—no context-switching between the CRM and a separate scheduling app. The API key auth means setup takes under two minutes. This works cleanly if your job volume stays under 40 active projects; beyond that, the 21-tool surface starts to feel narrow and you'll want direct JobNimbus access for bulk edits. If your dispatch ritual is already in Slack and your jobs live in JobNimbus, this MCP closes the loop without adding another dashboard.
Why this MCP falls short for high-velocity lead tracking
A 3-person solar sales team wants to update lead statuses and log follow-up calls during their weekly pipeline review. The JobNimbus MCP offers workflow status creation and contact retrieval, but it lacks a bulk-update tool and doesn't expose activity logging for calls or emails. You can create tasks one at a time, but if you're triaging 20+ leads in a 30-minute meeting, the round-trip latency makes this slower than just opening JobNimbus. The MCP shines when you need to create a single task or pull one contact's details mid-conversation, not when you're batch-processing pipeline changes. If your sales motion is high-touch and low-volume (under 10 new leads per week), the task and contact tools cover the essentials. Otherwise, keep JobNimbus open in a browser tab.
When custom document workflows justify the MCP overhead
A 4-person home services company fields support requests in a shared inbox and needs to attach photos, invoices, and warranty docs to the right JobNimbus contact. The MCP's file attachment type tool lets Switchy register custom categories (like 'warranty-claim' or 'before-photo') before uploading, so the support rep never leaves the chat thread. This matters if your document taxonomy is non-standard or changes often—JobNimbus's UI requires admin access to add attachment types, but the MCP exposes it as a tool any team member can invoke. The trade-off: if you're only uploading generic PDFs and JPEGs, the built-in JobNimbus mobile app is faster. Use this MCP when your attachment workflow has custom categories and you want to keep the support conversation in one place.
Frequently asked
What does the JobNimbus MCP do in Switchy?
It connects your JobNimbus CRM so AI agents can create contacts, tasks, material orders, and workflow statuses without leaving the chat. Agents can also retrieve account settings, pull contact details by ID, and create custom file attachment types. Think of it as giving your AI direct access to JobNimbus's core CRM operations—scheduling, ordering, and pipeline management—all through natural language.
Do I need admin access to connect JobNimbus?
You need a JobNimbus API key, which typically requires admin or owner-level permissions to generate. The key grants full read-write access to contacts, tasks, workflows, and material orders, so only connect it if you trust the team members using Switchy. JobNimbus doesn't offer granular API scopes—it's all or nothing.
Can the MCP update existing contacts or only create new ones?
The current tool set focuses on creation and retrieval—creating contacts, tasks, material orders, and workflow statuses, plus fetching contacts and activities by ID. If you need to update an existing contact's address or phone number, you'll still need to do that in JobNimbus directly or via their full API outside Switchy.
How does this compare to using JobNimbus's web app?
The MCP is faster for repetitive data entry—creating a dozen tasks or material orders from a conversation beats clicking through JobNimbus's UI. But it won't replace the web app for bulk imports, custom reporting, or visual pipeline management. Use the MCP when AI can handle the workflow; use the app when you need dashboards or advanced filtering.
Who on the team should connect JobNimbus to Switchy?
Whoever manages your JobNimbus API keys—usually an admin or operations lead. Once connected, any Switchy team member can trigger JobNimbus actions through AI, so only enable it if your team is comfortable with shared CRM access. The API key doesn't expire automatically, so rotate it if someone leaves.