jobnimbus

What this skill does

# Jobnimbus

JobNimbus is a CRM and project management software designed for home service businesses. It helps contractors and remodelers manage leads, estimates, jobs, and payments all in one place.

Official docs: https://api.jobnimbus.com/

## Jobnimbus Overview

- **JobNimbus**
  - **Contact**
  - **Job**
  - **Estimate**
  - **Invoice**
  - **Payment**
  - **Material Order**
  - **Lead**
  - **Task**
  - **Form**
  - **Checklist**
  - **Report**
  - **Workflow**
  - **Board**
  - **File**
  - **Note**
  - **Appointment**
  - **Communication**
  - **Vendor**
  - **Project**
  - **Customer**
  - **Product**
  - **User**
  - **Team**
  - **Activity**
  - **Location**
  - **Item**
  - **Purchase Order**
  - **Credit**
  - **Change Order**
  - **Work Order**
  - **Transaction**
  - **Fund**
  - **Account**
  - **Deposit**
  - **Equipment**
  - **Time Tracking**
  - **Timesheet**
  - **Expense**
  - **Inventory**
  - **Order**
  - **Shipment**
  - **Bill**
  - **Tax Rate**
  - **Template**
  - **Script**
  - **Email**
  - **SMS**
  - **Call**
  - **Setting**
  - **Integration**
  - **Subscription**
  - **Notification**
  - **Tag**
  - **Custom Field**
  - **Saved View**
  - **Postal Mail**
  - **Statement**
  - **Proposal**
  - **Drawing**
  - **Certificate**
  - **Warranty**
  - **Referral**
  - **Commission**
  - **Weather**
  - **Inspection**
  - **Defect**
  - **Punch List**
  - **Permit**
  - **Submittal**
  - **Transmittal**
  - **Meeting**
  - **Decision**
  - **Risk**
  - **Issue**
  - **Lesson Learned**
  - **Resource**
  - **Deliverable**
  - **Phase**
  - **Budget**
  - **Forecast**
  - **Variance**
  - **Claim**
  - **Change Request**
  - **RFI**
  - **Subcontract**
  - **Compliance**
  - **Audit**
  - **Safety**
  - **Incident**
  - **Training**
  - **Maintenance**
  - **Calibration**
  - **Meter Reading**
  - **Log**
  - **Alert**
  - **Escalation**
  - **Knowledge Base**
  - **Forum**
  - **Poll**
  - **Survey**
  - **Event**
  - **Goal**
  - **Key Result**
  - **OKR**
  - **Scorecard**
  - **Dashboard**
  - **Report**
  - **Analytics**
  - **Forecast**
  - **Trend**
  - **Benchmark**
  - **KPI**
  - **Metric**
  - **Signal**
  - **Insight**
  - **Recommendation**
  - **Automation**
  - **Integration**
  - **API**
  - **Webhook**
  - **Mobile App**
  - **Desktop App**
  - **Web App**

Use action names and parameters as needed.

## Working with Jobnimbus

This skill uses the Membrane CLI to interact with Jobnimbus. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Jobnimbus

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "https://www.jobnimbus.com/" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    - `"provide-input"` — more information is needed (e.g. which app to connect to).
  - `clientAction.description` — human-readable explanation of what's needed.
  - `clientAction.uiUrl` (optional) — URL to a pre-built UI where the user can complete the action. Show this to the user when present.
  - `clientAction.agentInstructions` (optional) — instructions for the AI agent on how to proceed programmatically.

  After the user completes the action (e.g. authenticates in the browser), poll again with `membrane connection get <id> --json` to check if the state moved to `READY`.

- **`CONFIGURATION_ERROR`** or **`SETUP_FAILED`** — something went wrong. Check the `error` field for details.

### Searching for actions

Search using a natural language description of what you want to do:

```bash
membrane action list --connectionId=CONNECTION_ID --intent "QUERY" --limit 10 --json
```

You should always search for actions in the context of a specific connection.

Each result includes `id`, `name`, `description`, `inputSchema` (what parameters the action accepts), and `outputSchema` (what it returns).

## Popular actions

| Name | Key | Description |
|---|---|---|
| List Contacts | list-contacts | Retrieve a list of contacts from JobNimbus with optional filtering and pagination |
| List Jobs | list-jobs | Retrieve a list of jobs from JobNimbus with optional filtering and pagination |
| List Tasks | list-tasks | Retrieve a list of tasks from JobNimbus with optional filtering and pagination |
| List Activities | list-activities | Retrieve a list of activities (notes/logs) from JobNimbus |
| List Estimates | list-estimates | Retrieve a list of estimates from JobNimbus |
| List Invoices | list-invoices | Retrieve a list of invoices from JobNimbus |
| List Payments | list-payments | Retrieve a list of payments from JobNimbus |
| List Files | list-files | Retrieve a list of files/attachments from JobNimbus |
| Get Contact | get-contact | Retrieve a single contact by its JobNimbus ID |
| Get Job | get-job | Retrieve a single job by its JobNimbus ID |
| Get Task | get-task | Retrieve a single task by its JobNimbus ID |
| Get Activity | get-activity | Retrieve a single activity by its JobNimbus ID |
| Get Estimate | get-estimate | Retrieve a single estimate by its JobNimbus ID |
| Get Invoice | get-invoice | Retrieve a single invoice by its JobNimbus ID |
| Get File | get-file | Retrieve file metadata by its JobNimbus ID |
| Create Contact | create-contact | Create a new contact in JobNimbus |
| Create Job | create-job | Create a new job in JobNimbus |
| Create Task | create-task | Create a new task in JobNimbus |
| Update Contact | update-contact | Update an existing contact in JobNimbus |
| Update Job | update-job | Update an existing job in JobNimbus |

### Running actions

```bash
membrane action run <actionId> --connectionId=CONNECTION_ID --json
```

To pass JSON parameters:

```bash
membrane action run <actionId> --connectionId=CONNECTION_ID --input '{"key": "value"}' --json
```

The result is in the `output` field of the response.


### Proxy requests

When the available actions don't cover your use case, you can send requests directly to the Jobnimbus API through Membrane's proxy. Membrane automatically appends the base URL t