Integration

Workiz integration

Workiz is field service management software for home service businesses (scheduling, dispatch, invoicing). An agent can list and read jobs and leads (schedule, status, client contact and address, job type and source, totals and amount due, assigned team), list the team members or read one, and read upcoming time off for the whole business or one user. This integration is read-only: every Workiz write route (create, update, assign, convert, mark lost, add payment) needs the account's API secret inside the request body, which this connection cannot inject, so none is exposed. Authentication is the API token from the Workiz account settings, which Workiz places in the URL path of every call.

Connect Workiz How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Workiz.Built from the 8 Workiz tools below, on the connection you add once.

What you can do with Workiz

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Job, 2 operations

get_jobGet jobGETGet one job by its UUID (from list_jobs): schedule, status, client contact and address, totals and amount due, notes and assigned team.
list_jobsList jobsGETList jobs, most recently scheduled first, 100 per page at most (page with offset and records; has_more says if more exist). By default only open jobs are listed.

Lead, 2 operations

get_leadGet leadGETGet one lead by its UUID (from list_leads): appointment time, status, client contact and address, job type, source and notes.
list_leadsList leadsGETList leads, most recently scheduled first, 100 per page at most (page with offset and records; has_more says if more exist). By default only open leads are listed.

Team member, 2 operations

get_userGet userGETGet one team member by id (from list_team_members): name, role, email, field technician flag, service areas, skills and whether active.
list_team_membersList team membersGETList the active team members of the account: id, name, role, whether a field technician, email, service areas and skills.

Time off, 2 operations

list_time_offList time offGETList upcoming time off: start, end and the user it belongs to. Set all=true to include every user and company-wide time off.
list_user_time_offList user time offGETList the upcoming time off of one user: start, end and user name.

Use Workiz from Claude Code, Cursor or Codex

Connect Workiz in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Workiz operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Workiz

Create your workspace
Sign up free. Nothing to install.
Connect Workiz once
Add your Workiz connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.