JobNimbus
Create and manage contacts, jobs, tasks and notes in JobNimbus, the field-service CRM built for roofing and exterior contractors.
About
JobNimbus ships in the w6w first-party pack. It declares 14 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.jobnimbus- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management
Overview
JobNimbus is a field-service CRM built for roofing and other exterior/home-services contractors — contacts and jobs move through customer-configured workflows (Lead, Inspection, Approved, …), with tasks, notes and file attachments hung off either one.
This app covers the core of JobNimbus’s own “Open API”: full read/write on Contacts and Jobs (get, list, create, update, and the soft-delete JobNimbus itself exposes as a status flip), plus creating and listing Tasks and Activities (notes) against either. Every JobNimbus record carries a jnid — the id every other action takes to address it — and every list read supports JobNimbus’s own Elasticsearch-syntax filter, offset pagination, and sort.
Authentication is a single static API Key, scoped by an assignable JobNimbus “Access Profile,” the same key used by JobNimbus’s own third-party integrations (BirdEye, CompanyCam, Zapier, …). A health check tracks JobNimbus’s own status page; JobNimbus publishes no rate-limit headers, so quota headroom is declared unavailable rather than guessed.
Build with JobNimbus
Three routes to the same 14 actions. The Workflow tab is generated from JobNimbus's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List Activities
activity-list List JobNimbus activities (notes and other logged events), newest first by default. Filter by `related.id` to scope to one contact or job, e.g. {"must":[{"term":{"related.id":"<jnid>"}}]}.
Delete Contact
contact-delete Deactivate a JobNimbus contact (JobNimbus's own "delete": the record is flagged inactive, not removed).
List Contacts
contact-list List JobNimbus contacts, newest first by default. Supports JobNimbus's own Elasticsearch-syntax filter, offset pagination and sort.
Update Contact
contact-update Update fields on an existing JobNimbus contact. Only the fields supplied are changed.
Delete Job
job-delete Deactivate a JobNimbus job (JobNimbus's own "delete": the record is flagged inactive, not removed).
List Jobs
job-list List JobNimbus jobs, newest first by default. Supports JobNimbus's own Elasticsearch-syntax filter, offset pagination and sort.
Update Job
job-update Update fields on an existing JobNimbus job. Only the fields supplied are changed.
List Tasks
task-list List JobNimbus tasks (to-dos and appointments), newest first by default. Filter by `related.id` to scope to one contact or job, e.g. {"must":[{"term":{"related.id":"<jnid>"}}]}.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying JobNimbus's real ids.
{
"manifestVersion": "2",
"name": "jobnimbus-example",
"steps": [
{
"id": "activity-create",
"uses": {
"app": "io.w6w.jobnimbus",
"action": "activity-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"note": "<note>"
}
}
]
}Here are some of the things you can do
-
Create Activity (Note)
performactivity-create -
List Activities
readactivity-list -
Create Contact
performcontact-create -
Get Contact
readcontact-get -
List Contacts
readcontact-list
+9 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for JobNimbus, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to JobNimbus. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "activity-create",
payload: {
note: "<value>",
// related_jnid: "<value>",
// record_type_name: "<value>",
// extra: "<value>",
// actor: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action activity-create --payload '{"note":"<value>"}'Give an AI agent JobNimbus — without giving it JobNimbus's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.jobnimbus#activity-create",
"input": {
"note": "<note>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's JobNimbus connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
JobNimbus's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. JobNimbus itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
JobNimbus declares its own checks, so its health is a property of the app rather than something the host guesses at.
JobNimbus platform status
The "Public API" component from status.jobnimbus.com, plus the rest of JobNimbus's own status page for visibility.