# Workiz API and MCP server

> Workiz has an official REST API, but only on the Ultimate plan, and it covers jobs, leads, team members and time off (checked 11 Oct 2026). Estimates, invoices and clients have no endpoints.

Field service management software for home service businesses: jobs, scheduling and dispatch, estimates, invoices and payments.

## What is the Workiz API?

Cotlet's Workiz API exposes 15 endpoints for your own Workiz account: list jobs, get job, get schedule, list leads, list clients, list estimates, list invoices, create job, reschedule job, assign job, create estimate, send estimate, create invoice, send invoice and record payment. The list_jobs endpoint returns jobs by scheduled date, with status, client, address, assigned techs and amount due. Each endpoint takes simple JSON inputs like limit, job_id or status and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 15 (7 read, 8 write)
- **Updated:** 2026-10-11

Workiz has an official REST API, but only on the Ultimate plan, and it covers jobs, leads, team members and time off (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Workiz with 15 endpoints (7 read, 8 write): your AI agent signs in as you and does the work.

## Does Workiz have an official API?

Workiz has an official REST API, but only on the Ultimate plan, and it covers jobs, leads, team members and time off (checked 11 Oct 2026). Estimates, invoices and clients have no endpoints.

| Task | Workiz official | Cotlet |
|---|---|---|
| List and filter jobs | Yes: By start date and status, up to 100 per call, Ultimate plan only | Yes |
| Create and update jobs | Yes: Ultimate plan only | Yes |
| Assign a team member to a job | Yes: Ultimate plan only | Yes |
| List and convert leads | Yes: Ultimate plan only | Yes |
| Record a payment on a job | Partly: Cash, credit or check record, no card charge | Yes |
| See the schedule for a day | Partly: Jobs and team time off, no calendar view | Yes |
| Find a client and their history | No | Yes |
| Create and send estimates | No | Yes |
| Create and send invoices | No | Yes |

Sources: [Workiz API OpenAPI spec](https://developer.workiz.com/api.json), [Workiz pricing: Open API and Zapier on Ultimate](https://www.workiz.com/pricing/), [Workiz on Zapier: triggers and actions](https://zapier.com/apps/workiz/integrations), [Workiz Help: How to create and send estimates](https://help.workiz.com/hc/en-us/articles/18055912006417-How-to-create-and-send-estimates), [Workiz Help: Automatically creating invoices when jobs are done](https://help.workiz.com/hc/en-us/articles/22330473454353-Automatically-creating-invoices-when-jobs-are-done), [Workiz Help: Automated estimate follow-ups](https://help.workiz.com/hc/en-us/articles/18053178531985-Closing-more-deals-with-automated-estimate-follow-ups)

## For AI agents

```text
Workiz has an official REST API, but only on the Ultimate plan, and it covers jobs, leads, team members and time off (checked 11 Oct 2026). Estimates, invoices and clients have no endpoints.
Cotlet provides a hosted MCP server and REST API for Workiz: 15 tools (7 read, 8 write).
Access       Request access at https://cotlet.dev/app/signup?app=workiz; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/workiz
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_jobs, get_job, get_schedule, list_leads, list_clients, list_estimates, list_invoices, create_job, reschedule_job, assign_job, create_estimate, send_estimate, create_invoice, send_invoice, record_payment
Confirm      create_job, reschedule_job, send_estimate, send_invoice, record_payment (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/workiz-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=workiz (Workiz is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Workiz once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Workiz server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Workiz MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Workiz in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Workiz's terms; Cotlet is not affiliated with Workiz.
```

## What can an AI agent do in Workiz?

Cotlet is best for field service owners and office managers who want an AI agent to invoice jobs, chase estimates, log payments and book leads in Workiz without running or fixing a server.

- **[Invoice completed jobs](https://cotlet.dev/integrations/workiz-api-mcp-server/invoice-completed-jobs)** (runs: daily): "Invoice every job marked Done yesterday, skip any job that already has an invoice or has no line items, and email the invoices to the clients." → `list_jobs`, `list_invoices`, `get_job`, `create_invoice`, `send_invoice`
- **Follow up on unapproved estimates** (runs: weekly): "Which estimates from the last 30 days are still pending? Resend them by email." → `list_estimates`, `send_estimate`
- **[Log cash and check payments](https://cotlet.dev/integrations/workiz-api-mcp-server/record-job-payments)** (runs: daily): "Log today's checks against the right jobs: $240 check #1042 from Dana Whitfield, $615 check #877 from Ray Okafor, $180 cash from Lena Ortiz. Then show me what is still unpaid." → `list_jobs`, `get_job`, `record_payment`, `list_invoices`
- **[Cover a technician's day off](https://cotlet.dev/integrations/workiz-api-mcp-server/reschedule-jobs-for-a-day)**: "Dana is out sick today. Give her jobs to whoever is free at the same time, move the rest to tomorrow at the same times, and list the clients I need to call." → `list_jobs`, `get_schedule`, `assign_job`, `reschedule_job`, `get_job`
- **[Book jobs from new leads](https://cotlet.dev/integrations/workiz-api-mcp-server/book-jobs-from-new-leads)** (runs: daily): "Book every lead that came in since yesterday into the first free slot this week and assign it to Mike. Ask me about any lead without a job type." → `list_leads`, `list_clients`, `get_schedule`, `create_job`, `assign_job`

## Can Workiz automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Workiz connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to invoice completed jobs, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/workiz/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/workiz/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/workiz/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/workiz/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Workiz.

### list_jobs

Jobs by scheduled date, with status, client, address, assigned techs and amount due. Access: read. REST: `POST /api/v1/workiz/list_jobs`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | no | First scheduled date. Default: 14 days ago. |
| `to` | date | no | Last scheduled date. Default: today. |
| `status` | string[] | no | Job statuses to include, e.g. Submitted, In progress, Done, Canceled. |
| `tech_id` | string | no | Only jobs assigned to this team member. |
| `limit` | integer | no | 1 to 100. Default: 50. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns jobs in a date range, newest first, with status, client, address, assigned team members, total and amount due. Pages hold up to 100 jobs; pass next_cursor back as cursor for the next page. Filter by status or by team member to narrow the list.

Example response:

```json
{
  "jobs": [
    {
      "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
      "status": "Done",
      "job_type": "Water heater install",
      "scheduled_start": "2026-10-09T09:00:00-07:00",
      "client": {
        "client_id": "cl_5521",
        "name": "Dana Whitfield"
      },
      "address": "12 Oak St, Sacramento, CA",
      "techs": [
        "Mike R."
      ],
      "total": "480.00",
      "amount_due": "480.00"
    }
  ],
  "next_cursor": null
}
```

### get_job

Full job: client, address, time window, job type, notes, items, total, amount due and payments. Access: read. REST: `POST /api/v1/workiz/get_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job UUID from list_jobs. |

Returns one job with everything on its page: client, address, time window, job type, notes, line items, total, amount due and the payments recorded so far. Use it before invoicing or recording a payment.

Example response:

```json
{
  "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
  "status": "Done",
  "job_type": "Water heater install",
  "client": {
    "client_id": "cl_5521",
    "name": "Dana Whitfield",
    "phone": "(555) 010-2231"
  },
  "address": "12 Oak St, Sacramento, CA",
  "window": {
    "start": "2026-10-09T09:00:00-07:00",
    "end": "2026-10-09T11:00:00-07:00"
  },
  "notes": "Gas line on the left wall.",
  "items": [
    {
      "name": "40 gal water heater",
      "quantity": 1,
      "price": "380.00"
    },
    {
      "name": "Install labor",
      "quantity": 1,
      "price": "100.00"
    }
  ],
  "total": "480.00",
  "amount_due": "480.00",
  "payments": []
}
```

### get_schedule

Jobs and time off per technician for a day or range, as on the Workiz calendar. Access: read. REST: `POST /api/v1/workiz/get_schedule`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | date | yes | First day. |
| `to` | date | no | Last day. Default: same as from. |
| `tech_ids` | string[] | no | Limit to these team members. Default: everyone. |

Returns each team member with their jobs and time off for the days you ask, ordered by start time, so your agent can see who has open slots. Time off is the future time off set in Workiz.

Example response:

```json
{
  "days": [
    {
      "date": "2026-10-12",
      "techs": [
        {
          "tech_id": "u_204",
          "name": "Mike R.",
          "jobs": [
            {
              "job_id": "3a9d41f2-85c0-4b7e-b6d2-91e7f0a35c48",
              "start": "2026-10-12T09:00:00-07:00",
              "end": "2026-10-12T11:00:00-07:00",
              "job_type": "Drain cleaning"
            }
          ],
          "time_off": []
        }
      ]
    }
  ]
}
```

### list_leads

Leads with status, source, client details and assigned team member. Access: read. REST: `POST /api/v1/workiz/list_leads`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | open, converted or lost. Default: open. |
| `since` | date | no | Only leads created on or after this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns leads, newest first, with status, source, contact details and the assigned team member. Open is the default, so converted and lost leads appear only when you ask for them. Pages hold up to 100 leads.

Example response:

```json
{
  "leads": [
    {
      "lead_id": "ld_8841",
      "status": "open",
      "source": "Website",
      "name": "Priya Nair",
      "phone": "(555) 010-7714",
      "created_at": "2026-10-10T08:12:00-07:00",
      "assigned_to": null
    }
  ],
  "next_cursor": null
}
```

### list_clients

Search clients by name, phone, email or address, with past jobs and balance due. Access: read. REST: `POST /api/v1/workiz/list_clients`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, phone, email or address. |
| `limit` | integer | no | 1 to 100. Default: 25. |

Searches your Workiz clients and returns matches with contact details, their past jobs and the balance due. Use the client_id in create_job, create_estimate and the other tools.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_5521",
      "name": "Dana Whitfield",
      "phone": "(555) 010-2231",
      "email": "dana@example.com",
      "address": "12 Oak St, Sacramento, CA",
      "jobs": 3,
      "balance_due": "480.00"
    }
  ]
}
```

### list_estimates

Estimates with client, total, status and the date they were sent. Access: read. REST: `POST /api/v1/workiz/list_estimates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | draft, sent, approved or declined. Default: all. |
| `since` | date | no | Only estimates created on or after this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns estimates, newest first, with client, total, status and the date sent. Filter by status to find the ones still waiting for an answer. Pages hold up to 100 estimates.

Example response:

```json
{
  "estimates": [
    {
      "estimate_id": "est_1187",
      "client": "Priya Nair",
      "total": "1,250.00",
      "status": "sent",
      "sent_at": "2026-10-01T10:15:00-07:00"
    }
  ],
  "next_cursor": null
}
```

### list_invoices

Invoices with job, client, total, amount due and due date. Access: read. REST: `POST /api/v1/workiz/list_invoices`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | enum | no | unpaid, partially_paid or paid. Default: unpaid. |
| `since` | date | no | Only invoices created on or after this date. |
| `limit` | integer | no | 1 to 100. Default: 50. |

Returns invoices, newest first, with the job, client, total, amount due and due date. Unpaid is the default. Pages hold up to 100 invoices.

Example response:

```json
{
  "invoices": [
    {
      "invoice_id": "inv_30214",
      "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
      "client": "Dana Whitfield",
      "total": "480.00",
      "amount_due": "240.00",
      "due_date": "2026-10-23",
      "status": "partially_paid"
    }
  ],
  "next_cursor": null
}
```

### create_job

New job for an existing or new client, with job type, time window and notes. Access: write, asks the user first. REST: `POST /api/v1/workiz/create_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | no | Existing client from list_clients. Or pass client below. |
| `client` | object | no | New client: first_name, last_name, phone, email, address. |
| `job_type` | string | yes | One of your Workiz job types. |
| `start` | datetime | yes | ISO 8601 with time zone. |
| `end` | datetime | no | End of the time window. |
| `notes` | string | no | Job notes for the tech. |

Creates a job for an existing client (client_id) or a new one (client object). Job type must be one of your Workiz job types. The job books an appointment for the client at the time you give. Returns the new job_id. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "9e2b7d14-6c35-4a08-8f1d-3b5a0c7e92d6",
  "status": "Submitted",
  "job_type": "Water heater install",
  "client_id": "cl_5521",
  "start": "2026-10-16T09:00:00-07:00",
  "notes": "Gas line on the left wall."
}
```

### reschedule_job

Move a job to a new time window. Changes the client's appointment. Access: write, asks the user first. REST: `POST /api/v1/workiz/reschedule_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job UUID from list_jobs. |
| `start` | datetime | yes | New start, ISO 8601 with time zone. |
| `end` | datetime | no | New end. |

Moves one job to a new start and, if given, a new end. The job keeps its assigned team members and its status. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "3a9d41f2-85c0-4b7e-b6d2-91e7f0a35c48",
  "status": "Submitted",
  "start": "2026-10-13T09:00:00-07:00",
  "end": "2026-10-13T11:00:00-07:00",
  "previous_start": "2026-10-12T09:00:00-07:00"
}
```

### assign_job

Assign or unassign team members on a job. Access: write. REST: `POST /api/v1/workiz/assign_job`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job UUID from list_jobs. |
| `tech_ids` | string[] | yes | Team members to assign. |
| `replace` | boolean | no | Remove current assignees first. Default: false. |

Adds team members to a job, or replaces the current ones when replace is true. It runs without asking first: it sends nothing to the client and one more call changes the assignment back.

Example response:

```json
{
  "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
  "techs": [
    {
      "tech_id": "u_204",
      "name": "Mike R."
    }
  ]
}
```

### create_estimate

Draft estimate for a client with items from your Price Book. Nothing is sent yet. Access: write. REST: `POST /api/v1/workiz/create_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client from list_clients. |
| `items` | object | yes | List of {name, quantity, price}; names match Price Book items. |
| `notes` | string | no | Note shown to the client. |

Creates an estimate in Draft for one client. Item names match items in your Workiz Price Book. Nothing is sent to the client until send_estimate runs, so this call runs without asking.

Example response:

```json
{
  "estimate_id": "est_1192",
  "client_id": "cl_5521",
  "status": "draft",
  "items": [
    {
      "name": "Tankless water heater",
      "quantity": 1,
      "price": "1,250.00"
    }
  ],
  "total": "1,250.00"
}
```

### send_estimate

Email or text an estimate to the client, with a link to approve it. Access: write, asks the user first. REST: `POST /api/v1/workiz/send_estimate`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `estimate_id` | string | yes | Estimate from list_estimates or create_estimate. |
| `via` | enum | no | email, sms or both. Default: email. |

Sends the estimate by email, text or both, with a link to view and approve it in the Workiz client portal. An unsent estimate becomes Pending; approval in the portal moves it to Approved. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "estimate_id": "est_1187",
  "status": "pending",
  "sent_via": "email",
  "sent_at": "2026-10-11T09:00:00-07:00"
}
```

### create_invoice

Invoice for a job with its items and total. Nothing is sent yet. Access: write. REST: `POST /api/v1/workiz/create_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job UUID from list_jobs. |
| `due_date` | date | no | Payment due date. |

Creates an invoice from a job, with the job's items and total. Nothing is sent to the client until send_invoice runs, so this call runs without asking. Returns the invoice_id.

Example response:

```json
{
  "invoice_id": "inv_30214",
  "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
  "items": [
    {
      "name": "40 gal water heater",
      "quantity": 1,
      "price": "380.00"
    },
    {
      "name": "Install labor",
      "quantity": 1,
      "price": "100.00"
    }
  ],
  "total": "480.00",
  "amount_due": "480.00",
  "due_date": "2026-10-23",
  "status": "unsent"
}
```

### send_invoice

Email or text an invoice to the client, with a link to pay online. Access: write, asks the user first. REST: `POST /api/v1/workiz/send_invoice`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `invoice_id` | string | yes | Invoice from list_invoices or create_invoice. |
| `via` | enum | no | email, sms or both. Default: email. |

Sends the invoice by email, text or both, with a link to the Workiz client portal. The client sees the amount due there. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "invoice_id": "inv_30214",
  "status": "sent",
  "sent_via": "email",
  "amount_due": "480.00",
  "sent_at": "2026-10-11T18:00:00-07:00"
}
```

### record_payment

Record a payment you already received on a job. Does not charge a card. Access: write, asks the user first. REST: `POST /api/v1/workiz/record_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `job_id` | string | yes | Job UUID from list_jobs. |
| `amount` | string | yes | Amount, e.g. 240.00. |
| `method` | enum | yes | cash, check or credit. |
| `paid_at` | datetime | no | When it was paid. Default: now. |
| `reference` | string | no | Check number or confirmation number. |

Records a payment you already received on a job, as cash, check or credit, with an optional reference such as a check number. It does not charge a card. Returns the job total and the amount still due. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
  "payment_id": "pay_88213",
  "amount": "240.00",
  "method": "check",
  "reference": "1042",
  "job_total": "480.00",
  "amount_due": "240.00",
  "status": "recorded"
}
```

## How do I connect Workiz to Claude Code, Codex or Cursor?

Connecting Workiz takes three steps: request access, sign in to Workiz once, then add one MCP server or call the REST API with the same key.

### Connect Workiz to your agent.

1. **Create an account** Sign up and add Workiz in the console. Your API key is there too.

2. **Sign in to Workiz once** Open the connect page from the console and sign in to Workiz the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Workiz tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Invoice every job marked Done yesterday, skip any job that already has an invoice or has no line items, and email the invoices to the clients.
```

### Call Workiz from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/workiz/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/workiz/record_payment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"job_id":"7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17","amount":"240.00","method":"check","paid_at":"2026-10-09T15:30:00-07:00","reference":"1042"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "job_id": "7c1e5a90-2b4d-4f6e-9a31-0d8e2c4b6f17",
  "payment_id": "pay_88213",
  "amount": "240.00",
  "method": "check",
  "reference": "1042",
  "job_total": "480.00",
  "amount_due": "240.00",
  "status": "recorded"
}
```

## Why use Cotlet for Workiz?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Workiz yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Workiz changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Workiz MCP server on GitHub?

Yes. Community Workiz MCP servers exist on GitHub, usually maintained by one person. You deploy one yourself with your Developer API token and keep it running; it can only do what the official API does, so it gets jobs and leads but not estimates or invoices. Cotlet hosts and maintains the same kind of server for you, and adds the parts the API lacks.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Get an API token on the Ultimate plan, deploy the server, add it to each MCP client | Request access, sign in to Workiz once, add one MCP server or API key |
| Plan needed | Ultimate, the only plan with the Open API | Your current plan; tools follow what your role can do in Workiz |
| Estimates, invoices, clients | Not possible, the API has no endpoints for them | Read, create and send them; each send is confirmed by you |
| When Workiz changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Workiz access | A token that works until you revoke it, stored where you host the server | Your session, encrypted in an EU vault, revoked in one click; if Workiz logs you out, your agent gets a link to sign in again |
| Where it runs | Your own server, which you update and monitor | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free code, you pay for hosting and the Ultimate plan | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Workiz changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Workiz API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Workiz API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Workiz account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Workiz yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Workiz tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Workiz in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Workiz's terms:** You use your own Workiz account and stay responsible for following Workiz's terms. Cotlet is independent and not affiliated with Workiz. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Workiz. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Workiz once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Workiz session would leave my computer.**

Cotlet keeps your Workiz session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need the Ultimate plan?**

No. The Workiz Open API and Zapier integration are included only in the Ultimate plan (checked 11 Oct 2026), but Cotlet works in your own Workiz account on your current plan. What a tool can do follows your role in Workiz.

**Can it charge a customer's card?**

No. record_payment logs a cash, check or credit payment you already received. Clients pay online through the link in the invoice, in the Workiz client portal.

**Can my agent post or send messages in Workiz without asking me?**

No. Every call to create_job, reschedule_job, send_estimate, send_invoice or record_payment waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. assign_job, create_estimate, create_invoice runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Workiz API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/workiz/{tool} from the HTTP Request node.