> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Clio

The Clio connector lets your AI agent act in each user's Clio account. Each user signs in to Clio once, and Scalekit stores and refreshes their tokens, so your agent never handles credentials. It comes with 30 tools.

**Authentication:** OAuth 2.0
**Categories:** Productivity, CRM & Sales
**Tools:** 30: 15 read, 11 write, 4 destructive
**Users sign in with:** OAuth
**OAuth app:** Your own Clio app
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CLIO)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Clio connection

   In **AgentKit > Connections**, create a Clio connection and copy its redirect URI. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Register an OAuth app

   Clio connections use your own OAuth app. Register one with Clio and add the redirect URI you copied.

   Then enter the app's Client ID and Client Secret on the Clio connection.

5. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'clio'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Clio:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'clio_activities_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "clio"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Clio:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="clio_activities_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user signs in once. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'clio_activities_list',
  toolInput: {},
  connector: 'clio',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="clio_activities_list",
    tool_input={},
    connection_name="clio",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `clio_activities_list`

List Activities · Read-only

List time and expense entries, filtered by matter, user, type, status, date range or a search on the note.
Returns data[] of activities (type, date, hours, price, total, note, billed state, matter, user) and meta.paging.
Use clio_activities_list to review billable work. Use clio_activity_create to log time or an expense.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `end_date` (`string`, optional): Entries dated on or before this date (YYYY-MM-DD). Example: 2026-11-30
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at. Default: `id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only entries on this matter. Example: 1234567
- `order` (`string`, optional): Sort order, such as date(desc), id(asc) or total(desc). Example: date(desc)
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `query` (`string`, optional): Wildcard search over the entry note. Example: research
- `start_date` (`string`, optional): Entries dated on or after this date (YYYY-MM-DD). Example: 2026-11-01
- `status` (`string`, optional): billed, draft, unbilled, non_billable, billable or written_off. Example: unbilled. One of: `billed`, `draft`, `unbilled`, `non_billable`, `billable`, `written_off`.
- `type` (`string`, optional): TimeEntry, ExpenseEntry, HardCostEntry, SoftCostEntry or FixedFee. Example: TimeEntry. One of: `TimeEntry`, `ExpenseEntry`, `HardCostEntry`, `SoftCostEntry`, `FixedFee`.
- `user_id` (`integer`, optional): Only entries by this user. Example: 345678

Example input: `{}`

### `clio_bill_get`

Get Bill · Read-only

Get one bill.
Returns data with the requested bill fields.
Use clio_bill_get when you know the bill ID. Use clio_bills_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `bill_id` (`integer`, required): ID of the bill. Example: 1234567
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at. Default: `id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at`.

Example input: `{"bill_id":1234567}`

### `clio_bills_list`

List Bills · Read-only

List bills (invoices), filtered by client, matter, state, overdue status or issue and due dates.
Returns data[] of bills (number, state, issued and due dates, total, paid, balance, client, matters) and meta.paging.
Use clio_bills_list to check invoices and balances. Use clio_bill_get for one bill.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `client_id` (`integer`, optional): Only bills for this client contact. Example: 1234568
- `due_before` (`string`, optional): Due before this date (YYYY-MM-DD). Example: 2026-12-01
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at. Default: `id,etag,number,state,kind,issued_at,due_at,total,paid,balance,due,subject,client{id,name},matters{id,display_number},created_at,updated_at`.
- `issued_after` (`string`, optional): Issued after this date (YYYY-MM-DD). Example: 2026-10-01
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only bills for this matter. Example: 1234567
- `overdue_only` (`boolean`, optional): Only overdue bills. Example: true
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `state` (`string`, optional): draft, awaiting_approval, awaiting_payment, paid, void or deleted. Example: awaiting_payment. One of: `draft`, `awaiting_approval`, `awaiting_payment`, `paid`, `void`, `deleted`.

Example input: `{}`

### `clio_calendar_entries_list`

List Calendar Entries · Read-only

List calendar entries in a time range, optionally for one calendar or matter, with recurring events expanded.
Returns data[] of entries (summary, start_at, end_at, all_day, location, matter, calendar owner) and meta.paging.
Use clio_calendar_entries_list to check a schedule. Use clio_calendar_entry_create to add an event.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `calendar_id` (`integer`, optional): Only entries on this calendar. Example: 456789
- `expanded` (`boolean`, optional): Return each occurrence of recurring events. Example: true
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at. Default: `id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at`.
- `from` (`string`, optional): Entries ending on or after this ISO-8601 time. Example: 2026-11-15T00:00:00Z
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only entries for this matter. Example: 1234567
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `query` (`string`, optional): Wildcard search over calendar entries. Example: hearing
- `to` (`string`, optional): Entries starting on or before this ISO-8601 time. Example: 2026-11-22T23:59:59Z

Example input: `{}`

### `clio_calendars_list`

List Calendars · Read-only

List calendars the connected user can see.
Returns data[] of calendars with id, name, type (UserCalendar, AccountCalendar, AdhocCalendar), permission and visibility.
Use clio_calendars_list to get the calendar ID needed by clio_calendar_entry_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,type,permission,visible,color. Default: `id,etag,name,type,permission,visible,color`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `owner` (`boolean`, optional): Only calendars the user owns. Example: true
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `type` (`string`, optional): AccountCalendar, AdhocCalendar or UserCalendar. Example: UserCalendar. One of: `AccountCalendar`, `AdhocCalendar`, `UserCalendar`.
- `writeable` (`boolean`, optional): Only calendars the user can write to. Example: true

Example input: `{}`

### `clio_communications_list`

List Communications · Read-only

List logged emails and phone calls, filtered by matter, contact, user, type, date range or a search string.
Returns data[] of communications (type, subject, body, received_at, matter, senders, receivers) and meta.paging.
Use clio_communications_list to review client correspondence. Use clio_communication_create to log a call or email.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, optional): Only communications with this contact. Example: 1234568
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at. Default: `id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only communications on this matter. Example: 1234567
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `query` (`string`, optional): Wildcard search over communication body and subject. Example: settlement
- `received_before` (`string`, optional): On or before this date (ISO-8601). Example: 2026-11-30
- `received_since` (`string`, optional): On or after this date (ISO-8601). Example: 2026-11-01
- `type` (`string`, optional): EmailCommunication or PhoneCommunication. Example: PhoneCommunication. One of: `EmailCommunication`, `PhoneCommunication`.

Example input: `{}`

### `clio_contact_get`

Get Contact · Read-only

Get one contact.
Returns data with the requested contact fields.
Use clio_contact_get when you know the contact ID. Use clio_contacts_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): ID of the contact. Example: 1234567
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at. Default: `id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at`.

Example input: `{"contact_id":1234567}`

### `clio_contacts_list`

List Contacts · Read-only

List people and companies in Clio, filtered by a search string, type, client flag or update time.
Returns data[] of contacts (name, type, primary email and phone, is_client, company) and meta.paging.
Use clio_contacts_list to find a contact or client. Use clio_contact_get for one contact by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `client_only` (`boolean`, optional): Only contacts that are clients. Example: true
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at. Default: `id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `order` (`string`, optional): id(asc), id(desc), name(asc) or name(desc). Example: name(asc). One of: `id(asc)`, `id(desc)`, `name(asc)`, `name(desc)`, `shared_at(asc)`, `shared_at(desc)`.
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `query` (`string`, optional): Wildcard search over name, title, email, address, phone, web site, custom fields and related matter. Example: Smith
- `type` (`string`, optional): Person or Company. Example: Person. One of: `Person`, `Company`.
- `updated_since` (`string`, optional): Only records updated after this ISO-8601 time. Example: 2026-11-01T00:00:00Z

Example input: `{}`

### `clio_matter_get`

Get Matter · Read-only

Get one matter.
Returns data with the requested matter fields.
Use clio_matter_get when you know the matter ID. Use clio_matters_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `matter_id` (`integer`, required): ID of the matter. Example: 1234567
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at. Default: `id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at`.

Example input: `{"matter_id":1234567}`

### `clio_matters_list`

List Matters · Read-only

List matters, filtered by status, client, responsible attorney, practice area, update time or a search string.
Returns data[] of matters (display_number, description, status, dates, client, attorneys, practice area) and meta.paging.
Use clio_matters_list to find matters. Use clio_matter_get for one matter by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `billable` (`boolean`, optional): Only billable (true) or non-billable (false) matters. Example: true
- `client_id` (`integer`, optional): Only matters for this client contact. Example: 1234567
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at. Default: `id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `order` (`string`, optional): Sort order, such as display_number(asc), id(desc), open_date(desc) or updated_at(desc). Example: updated_at(desc)
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `practice_area_id` (`integer`, optional): Only matters in this practice area. Example: 98765
- `query` (`string`, optional): Wildcard search over display number, number, description and client name. Example: Smith
- `responsible_attorney_id` (`integer`, optional): Only matters with this responsible attorney (user ID). Example: 345678
- `status` (`string`, optional): Comma-separated statuses: open, pending, closed. Example: open,pending
- `updated_since` (`string`, optional): Only records updated after this ISO-8601 time. Example: 2026-11-01T00:00:00Z

Example input: `{}`

### `clio_notes_list`

List Notes · Read-only

List notes on matters or on contacts, filtered by matter, contact or a search string.
Returns data[] of notes (subject, detail, date, matter or contact, author) and meta.paging.
Use clio_notes_list to read case notes. Use clio_note_create to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `type` (`string`, required): Matter for matter notes, Contact for contact notes. Example: Matter. One of: `Matter`, `Contact`.
- `contact_id` (`integer`, optional): Only notes on this contact. Example: 1234568
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at. Default: `id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only notes on this matter. Example: 1234567
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `query` (`string`, optional): Wildcard search over note subject and detail. Example: settlement

Example input: `{"type":"Matter"}`

### `clio_task_get`

Get Task · Read-only

Get one task.
Returns data with the requested task fields.
Use clio_task_get when you know the task ID. Use clio_tasks_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`integer`, required): ID of the task. Example: 1234567
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at. Default: `id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at`.

Example input: `{"task_id":1234567}`

### `clio_tasks_list`

List Tasks · Read-only

List tasks, filtered by matter, assignee, status, priority, completion, due-date range or a search string.
Returns data[] of tasks (name, description, status, priority, due date, matter, assignee) and meta.paging.
Use clio_tasks_list to see open work. Use clio_task_get for one task.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `assignee_id` (`integer`, optional): Only tasks assigned to this user or contact; set assignee_type too. Example: 345678
- `assignee_type` (`string`, optional): user or contact; required with assignee_id. Example: user. One of: `user`, `contact`.
- `complete` (`boolean`, optional): true for completed tasks, false for open ones. Example: false
- `due_at_from` (`string`, optional): Due on or after this date (YYYY-MM-DD). Example: 2026-11-15
- `due_at_to` (`string`, optional): Due on or before this date (YYYY-MM-DD). Example: 2026-11-30
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at. Default: `id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `matter_id` (`integer`, optional): Only tasks on this matter. Example: 1234567
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `priority` (`string`, optional): high, normal or low. Example: high. One of: `high`, `normal`, `low`.
- `query` (`string`, optional): Wildcard search over task name and description. Example: discovery
- `status` (`string`, optional): pending, in_progress, in_review, complete or draft. Example: pending. One of: `pending`, `in_progress`, `in_review`, `complete`, `draft`.

Example input: `{}`

### `clio_users_list`

List Users · Read-only

List users in the Clio firm, filtered by name, role, subscription type or enabled state.
Returns data[] of users with the requested fields and meta.paging for the next page.
Use clio_users_list to find a user ID for matters, tasks or time entries. Use clio_who_am_i_get for the connected user.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `enabled` (`boolean`, optional): true for enabled users, false for disabled. Example: true
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id. Default: `id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id`.
- `limit` (`integer`, optional): Records per page, 1-200 (default 200). Example: 50
- `name` (`string`, optional): Only users with this name. Example: Jane Doe
- `page_token` (`string`, optional): Token for the next page, taken from meta.paging.next in the previous response. Example: BAh7BjoLb2Zmc2V0aQH6
- `role` (`string`, optional): Only users with this role: admin, accounts, billing or reports. Example: billing. One of: `admin`, `accounts`, `billing`, `reports`.
- `subscription_type` (`string`, optional): attorney or nonattorney. Example: attorney. One of: `attorney`, `nonattorney`.

Example input: `{}`

### `clio_who_am_i_get`

Get Current User · Read-only

Get the Clio user the connection belongs to.
Returns data with the user's id, name, email, roles, subscription type, time zone and default calendar ID.
Use clio_who_am_i_get to learn the connected user's ID and default calendar. Use clio_users_list for other firm users.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id. Default: `id,etag,name,first_name,last_name,email,enabled,roles,subscription_type,time_zone,default_calendar_id`.

Example input: `{}`

### `clio_activity_create`

Create Activity · Write

Log a time entry or an expense, usually against a matter.
Returns data with the new activity's id, total and the requested fields.
Use clio_activity_create to record billable time or costs. Use clio_activities_list to review entries.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `date` (`string`, required): Date the work was done (YYYY-MM-DD). Example: 2026-11-15
- `type` (`string`, required): TimeEntry, ExpenseEntry, HardCostEntry, SoftCostEntry or FixedFee. Example: TimeEntry. One of: `TimeEntry`, `ExpenseEntry`, `HardCostEntry`, `SoftCostEntry`, `FixedFee`.
- `activity_description_id` (`integer`, optional): Activity description (rate category) ID. Example: 22334
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at. Default: `id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter to log against. Example: 1234567
- `non_billable` (`boolean`, optional): Keep the entry off bills. Example: false
- `note` (`string`, optional): What the entry is for. Example: Drafted motion to dismiss
- `price` (`number`, optional): Hourly rate for a TimeEntry, or the amount for an expense. Example: 250
- `quantity` (`number`, optional): For TimeEntry, the time in seconds (4.0.4 and later); for ExpenseEntry and SoftCostEntry, the quantity. Example: 3600
- `user_id` (`integer`, optional): User who did the work; defaults to the connected user. Example: 345678

Example input: `{"date":"<date>","type":"TimeEntry"}`

### `clio_activity_update`

Update Activity · Write

Update an unbilled time or expense entry: date, quantity, rate, note, matter or billable flag.
Returns data with the updated activity fields.
Use clio_activity_update to correct an entry before it is billed.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `activity_id` (`integer`, required): ID of the activity. Example: 1234567
- `activity_description_id` (`integer`, optional): Activity description (rate category) ID. Example: 22334
- `date` (`string`, optional): New date (YYYY-MM-DD). Example: 2026-11-14
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at. Default: `id,etag,type,date,quantity_in_hours,price,total,note,billed,non_billable,matter{id,display_number},user{id,name},activity_description{id,name},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter to log against. Example: 1234567
- `non_billable` (`boolean`, optional): Keep the entry off bills. Example: false
- `note` (`string`, optional): What the entry is for. Example: Drafted motion to dismiss
- `price` (`number`, optional): Hourly rate for a TimeEntry, or the amount for an expense. Example: 250
- `quantity` (`number`, optional): For TimeEntry, the time in seconds (4.0.4 and later); for ExpenseEntry and SoftCostEntry, the quantity. Example: 3600
- `user_id` (`integer`, optional): User who did the work; defaults to the connected user. Example: 345678

Example input: `{"activity_id":1234567}`

### `clio_calendar_entry_create`

Create Calendar Entry · Write

Create an event on a Clio calendar, optionally linked to a matter.
Returns data with the new entry's id and the requested fields.
Use clio_calendar_entry_create to schedule a hearing or meeting. Get calendar_id from clio_calendars_list or clio_who_am_i_get (default_calendar_id).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `calendar_id` (`integer`, required): Calendar to put the entry on. Example: 456789
- `end_at` (`string`, required): End time (ISO-8601). Example: 2026-11-20T16:00:00Z
- `start_at` (`string`, required): Start time (ISO-8601). Example: 2026-11-20T15:00:00Z
- `summary` (`string`, required): Short title. Example: Hearing - Smith v. Jones
- `all_day` (`boolean`, optional): All-day event. Example: false
- `description` (`string`, optional): Details. Example: Courtroom 4B
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at. Default: `id,etag,summary,description,location,start_at,end_at,all_day,recurrence_rule,matter{id,display_number},calendar_owner{id,name},created_at,updated_at`.
- `location` (`string`, optional): Location. Example: 361 University Ave, Toronto
- `matter_id` (`integer`, optional): Matter to link. Example: 1234567
- `recurrence_rule` (`string`, optional): iCalendar RRULE for a repeating event. Example: FREQ=WEEKLY;COUNT=4

Example input: `{"calendar_id":456789,"end_at":"<end_at>","start_at":"<start_at>","summary":"<summary>"}`

### `clio_communication_create`

Log Communication · Write

Log a phone call or email in Clio, optionally on a matter with senders and receivers; nothing is sent.
Returns data with the new communication's id and the requested fields.
Use clio_communication_create to record correspondence on a matter.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): What was said or written. Example: Client confirmed documents will be sent Friday
- `received_at` (`string`, required): When it happened (ISO-8601 date-time). Example: 2026-11-15T14:30:00Z
- `subject` (`string`, required): Subject. Example: Call with client re discovery
- `type` (`string`, required): PhoneCommunication or EmailCommunication. Example: PhoneCommunication. One of: `PhoneCommunication`, `EmailCommunication`.
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at. Default: `id,etag,type,subject,body,date,received_at,matter{id,display_number},user{id,name},senders{id,name,type},receivers{id,name,type},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter to log it on. Example: 1234567
- `receivers` (`array`, optional): Receivers, each {"id": ..., "type": "User" or "Contact"}. Example: [{"id": 345678, "type": "User"}]
- `senders` (`array`, optional): Senders, each {"id": ..., "type": "User" or "Contact"}. Example: [{"id": 1234568, "type": "Contact"}]

Example input: `{"body":"<body>","received_at":"<received_at>","subject":"<subject>","type":"PhoneCommunication"}`

### `clio_contact_create`

Create Contact · Write

Create a person or company contact.
Returns data with the new contact's id and the requested fields.
Use clio_contact_create to add a client or other party. Use clio_contacts_list first to avoid duplicates.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Full name of the person, or the company name. Example: Jane Smith
- `type` (`string`, required): Person or Company. Example: Person. One of: `Person`, `Company`.
- `addresses` (`array`, optional): Addresses, each {name: Work, Home, Billing or Other, street, city, province, postal_code, country}. Example: [{"name": "Work", "street": "1 King St W", "city": "Toronto", "province": "ON", "postal_code": "M5H 1A1", "country": "Canada"}]
- `company_id` (`integer`, optional): Contact ID of the company this person works for. Example: 1234568
- `email_addresses` (`array`, optional): Email addresses, each {name: Work, Home or Other, address, default_email}. Example: [{"name": "Work", "address": "jane@example.com", "default_email": true}]
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at. Default: `id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at`.
- `first_name` (`string`, optional): First name (Person). Example: Jane
- `last_name` (`string`, optional): Last name (Person). Example: Smith
- `phone_numbers` (`array`, optional): Phone numbers, each {name: Work, Home, Mobile, Fax, Pager, Skype or Other, number, default_number}. Example: [{"name": "Work", "number": "555-0100", "default_number": true}]
- `title` (`string`, optional): Professional title. Example: General Counsel

Example input: `{"name":"<name>","type":"Person"}`

### `clio_contact_update`

Update Contact · Write

Update a contact's name, title, emails, phone numbers, addresses or company.
Returns data with the updated contact fields.
Use clio_contact_update to change contact details. Email, phone and address arrays add entries; include an id to change an existing one.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): ID of the contact. Example: 1234567
- `addresses` (`array`, optional): Addresses, each {name: Work, Home, Billing or Other, street, city, province, postal_code, country}. Example: [{"name": "Work", "street": "1 King St W", "city": "Toronto", "province": "ON", "postal_code": "M5H 1A1", "country": "Canada"}]
- `company_id` (`integer`, optional): Contact ID of the company this person works for. Example: 1234568
- `email_addresses` (`array`, optional): Email addresses, each {name: Work, Home or Other, address, default_email}. Example: [{"name": "Work", "address": "jane@example.com", "default_email": true}]
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at. Default: `id,etag,name,first_name,last_name,type,title,primary_email_address,primary_phone_number,is_client,company{id,name},created_at,updated_at`.
- `first_name` (`string`, optional): First name (Person). Example: Jane
- `last_name` (`string`, optional): Last name (Person). Example: Smith
- `name` (`string`, optional): New full name or company name. Example: Jane A. Smith
- `phone_numbers` (`array`, optional): Phone numbers, each {name: Work, Home, Mobile, Fax, Pager, Skype or Other, number, default_number}. Example: [{"name": "Work", "number": "555-0100", "default_number": true}]
- `title` (`string`, optional): Professional title. Example: General Counsel

Example input: `{"contact_id":1234567}`

### `clio_matter_create`

Create Matter · Write

Create a matter for a client contact.
Returns data with the new matter's id, display_number and the requested fields.
Use clio_matter_create to open a new case. Create or find the client with clio_contact_create or clio_contacts_list first.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `client_id` (`integer`, required): Contact ID of the client. Example: 1234567
- `description` (`string`, required): Description of the matter. Example: Smith v. Jones - contract dispute
- `billable` (`boolean`, optional): Whether the matter is billable. Example: true
- `client_reference` (`string`, optional): Client reference for your own use. Example: PO-4471
- `close_date` (`string`, optional): Close date (YYYY-MM-DD). Example: 2026-12-31
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at. Default: `id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at`.
- `location` (`string`, optional): Location of the matter. Example: Toronto
- `open_date` (`string`, optional): Open date (YYYY-MM-DD). Example: 2026-11-15
- `originating_attorney_id` (`integer`, optional): User ID of the originating attorney. Example: 345678
- `practice_area_id` (`integer`, optional): Practice area ID. Example: 98765
- `responsible_attorney_id` (`integer`, optional): User ID of the responsible attorney. Example: 345678
- `status` (`string`, optional): open, pending or closed. Example: open. One of: `open`, `pending`, `closed`.

Example input: `{"client_id":1234567,"description":"<description>"}`

### `clio_matter_update`

Update Matter · Write

Update a matter's description, status, dates, attorneys, practice area or billing flag.
Returns data with the updated matter fields.
Use clio_matter_update to change or close a matter. Use clio_matter_get first to see current values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `matter_id` (`integer`, required): ID of the matter. Example: 1234567
- `billable` (`boolean`, optional): Whether the matter is billable. Example: true
- `client_reference` (`string`, optional): Client reference for your own use. Example: PO-4471
- `close_date` (`string`, optional): Close date (YYYY-MM-DD). Example: 2026-12-31
- `description` (`string`, optional): New description. Example: Smith v. Jones - settled
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at. Default: `id,etag,display_number,description,status,open_date,close_date,pending_date,billable,client_reference,location,client{id,name},responsible_attorney{id,name},originating_attorney{id,name},practice_area{id,name},created_at,updated_at`.
- `location` (`string`, optional): Location of the matter. Example: Toronto
- `open_date` (`string`, optional): Open date (YYYY-MM-DD). Example: 2026-11-15
- `originating_attorney_id` (`integer`, optional): User ID of the originating attorney. Example: 345678
- `practice_area_id` (`integer`, optional): Practice area ID. Example: 98765
- `responsible_attorney_id` (`integer`, optional): User ID of the responsible attorney. Example: 345678
- `status` (`string`, optional): open, pending or closed. Example: open. One of: `open`, `pending`, `closed`.

Example input: `{"matter_id":1234567}`

### `clio_note_create`

Create Note · Write

Add a note to a matter or a contact.
Returns data with the new note's id and the requested fields.
Use clio_note_create to record case information. Set type Matter with matter_id, or type Contact with contact_id.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `type` (`string`, required): Matter or Contact. Example: Matter. One of: `Matter`, `Contact`.
- `contact_id` (`integer`, optional): Contact the note belongs to; required when type is Contact. Example: 1234568
- `date` (`string`, optional): Note date (YYYY-MM-DD). Example: 2026-11-15
- `detail` (`string`, optional): Note text. Example: Opposing counsel open to mediation in December
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at. Default: `id,etag,type,subject,detail,date,matter{id,display_number},contact{id,name},author{id,name},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter the note belongs to; required when type is Matter. Example: 1234567
- `subject` (`string`, optional): Note subject. Example: Settlement call

Example input: `{"type":"Matter"}`

### `clio_task_create`

Create Task · Write

Create a task, optionally on a matter and assigned to a user or contact.
Returns data with the new task's id and the requested fields.
Use clio_task_create to add a to-do. Use clio_task_update to complete or change it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `description` (`string`, required): Task description. Example: File with the court by end of day
- `name` (`string`, required): Task name. Example: File statement of claim
- `assignee` (`object`, optional): Who the task is for, as {"id": ..., "type": "User" or "Contact"}. Example: {"id": 345678, "type": "User"}
- `due_at` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at. Default: `id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter the task belongs to. Example: 1234567
- `notify_assignee` (`boolean`, optional): Email the assignee about the task. Example: false
- `priority` (`string`, optional): High, Normal or Low. Example: High. One of: `High`, `Normal`, `Low`.
- `status` (`string`, optional): pending, in_progress, in_review, complete or draft (without advanced tasks only pending or complete). Example: complete. One of: `pending`, `in_progress`, `in_review`, `complete`, `draft`.

Example input: `{"description":"<description>","name":"<name>"}`

### `clio_task_update`

Update Task · Write

Update a task: rename it, change due date, priority, status, matter or assignee, or mark it complete.
Returns data with the updated task fields.
Use clio_task_update with status complete to finish a task.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`integer`, required): ID of the task. Example: 1234567
- `assignee` (`object`, optional): Who the task is for, as {"id": ..., "type": "User" or "Contact"}. Example: {"id": 345678, "type": "User"}
- `description` (`string`, optional): New description. Example: Filed on 15 Nov
- `due_at` (`string`, optional): Due date (YYYY-MM-DD). Example: 2026-11-30
- `fields` (`string`, optional): Comma-separated fields to return; nested records use braces. Clio returns only id and etag when fields is empty, so a useful default is set. Example: id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at. Default: `id,etag,name,description,status,priority,due_at,completed_at,permission,matter{id,display_number},assignee{id,name,type},created_at,updated_at`.
- `matter_id` (`integer`, optional): Matter the task belongs to. Example: 1234567
- `name` (`string`, optional): New name. Example: File amended claim
- `notify_assignee` (`boolean`, optional): Email the assignee about the task. Example: false
- `priority` (`string`, optional): High, Normal or Low. Example: High. One of: `High`, `Normal`, `Low`.
- `status` (`string`, optional): pending, in_progress, in_review, complete or draft (without advanced tasks only pending or complete). Example: complete. One of: `pending`, `in_progress`, `in_review`, `complete`, `draft`.

Example input: `{"task_id":1234567}`

### `clio_activity_delete`

Delete Activity · Destructive

Delete an unbilled time or expense entry.
Returns no content (HTTP 204) when deleted.
Use clio_activity_delete to remove an entry logged by mistake; billed entries can't be deleted.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `activity_id` (`integer`, required): ID of the activity. Example: 1234567

Example input: `{"activity_id":1234567}`

### `clio_calendar_entry_delete`

Delete Calendar Entry · Destructive

Delete a calendar entry.
Returns no content (HTTP 204) when deleted.
Use clio_calendar_entry_delete with an ID from clio_calendar_entries_list.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `calendar_entry_id` (`integer`, required): ID of the calendar entry. Example: 1234567

Example input: `{"calendar_entry_id":1234567}`

### `clio_contact_delete`

Delete Contact · Destructive

Delete a contact.
Returns no content (HTTP 204) when deleted.
Use clio_contact_delete only to remove a contact for good; clients with matters can't be deleted.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`integer`, required): ID of the contact. Example: 1234567

Example input: `{"contact_id":1234567}`

### `clio_task_delete`

Delete Task · Destructive

Delete a task.
Returns no content (HTTP 204) when deleted.
Use clio_task_delete to remove a task; use clio_task_update with status complete to finish one instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`integer`, required): ID of the task. Example: 1234567

Example input: `{"task_id":1234567}`

## Related

Other Productivity connectors ([all 203](/agentkit/connectors/?category=productivity)):

- [Slack](/agentkit/connectors/slack/): Scalekit connector, OAuth, 96 tools
- [Notion](/agentkit/connectors/notion/): Scalekit connector, OAuth, 51 tools
- [Google Workspace (DWD)](/agentkit/connectors/googledwd/): Scalekit connector, Service account, 100 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
