# ConnectWise PSA

> Run your MSP's ConnectWise PSA from workflows: create, update and search service tickets and their notes, add companies and contacts, log time, start projects, and start a workflow when a ticket is created, changes status or closes, or when a company, contact, time entry, project, opportunity or activity is added.

App · 25 actions. Web page: https://docs.lodol.com/docs/integrations/connectwise-psa

## Actions

### Add project phase

Add a phase to a project, to hold its project tickets.

**Inputs**

- Project ID (`project_id`, text, required): The project's id, from 'Create project' or a trigger.
- Phase name (`phase_name`, text, required): Such as Planning, up to 100 characters.
- Notes (`notes`, text): Notes about the phase.
- Budget hours (`budget_hours`, number): Hours budgeted, such as 1.5. From 0 to 10000.

**Outputs**

- `phase` (object): The phase

**Example output**

```json
{
  "phase": {
    "budget_hours": 8.0,
    "id": 3301,
    "name": "Planning",
    "notes": "Agree the cut-over date.",
    "project_id": 812,
    "status": "Open",
    "wbs_code": "1"
  }
}
```

### Add ticket note

Add a discussion, internal or resolution note to a ticket.

**Inputs**

- Ticket number (`ticket_id`, text, required): The ticket's number, from 'Search tickets', 'Create ticket' or a trigger. A link to the ticket works too.
- Note (`text`, text, required): What the note says.
- Note type (`note_type`, text): Discussion notes can be seen by the customer; internal analysis is for staff. One of: `discussion` (Discussion, which the customer can see (default)), `internal` (Internal analysis, for staff only), `resolution`. Default: `discussion`.
- Send notifications (`notify`, true/false): Let ConnectWise send the emails its workflow rules set up for a new note. Default: `true`.

**Outputs**

- `note` (object): The note

**Example output**

```json
{
  "note": {
    "contact": "",
    "created_at": "2026-10-28T14:05:12Z",
    "created_by": "jsmith",
    "id": 902114,
    "member": "Jordan Smith",
    "note_type": "internal",
    "text": "Power cycled the printer; it is back online.",
    "ticket_id": 48211
  }
}
```

### Create activity

Schedule a sales activity, such as a call or meeting, for a member, about a company, contact, opportunity or ticket.

**Inputs**

- Subject (`name`, text, required): What the activity is, up to 100 characters.
- Assign to (`assign_to`, text, required): The member who will do it. Pick one, or give a member id or identifier.
- Type (`activity_type`, text): Such as Call or Meeting.
- Status (`status`, text): Such as Open.
- Company (`company`, text): The company it is about. Pick one, or give its id or short ID.
- Contact ID (`contact_id`, text): The contact's id, from 'Search contacts', 'Create contact' or a trigger.
- Opportunity ID (`opportunity_id`, text): The opportunity it is about.
- Ticket number (`ticket_id`, text): The ticket it is about.
- Starts (`starts_at`, date and time): When it starts.
- Ends (`ends_at`, date and time): When it ends.
- Notes (`notes`, text): Notes for the member.

**Outputs**

- `activity` (object): The activity

**Example output**

```json
{
  "activity": {
    "assigned_to": "Jordan Smith",
    "assigned_to_id": 145,
    "company": "Acme Corporation",
    "company_id": 250,
    "contact": "Ana Lopez",
    "created_at": "2026-10-28T16:00:00Z",
    "email": "ana.lopez@acme.example",
    "ends_at": "2026-11-03T15:30:00Z",
    "id": 9921,
    "name": "Call Ana about the renewal",
    "notes": "Ask about adding two seats.",
    "opportunity_id": 615,
    "phone": "8135551234",
    "starts_at": "2026-11-03T15:00:00Z",
    "status": "Open",
    "ticket_id": 0,
    "type": "Call",
    "updated_at": "2026-10-28T16:00:00Z"
  }
}
```

### Create company

Add a company (a client, prospect or vendor) with its address and phone number.

**Inputs**

- Name (`name`, text, required): The company's name, up to 50 characters.
- Identifier (`identifier`, text): Its short ID in ConnectWise, such as AcmeCorp: up to 30 letters or digits, no spaces. Left empty, it is made from the name.
- Types (`company_types`, list): Such as Client or Prospect. Left empty, the default company type is used.
- Status (`status`, text): Such as Active.
- Address (`address_line1`, text): Street address.
- Address line 2 (`address_line2`, text): Suite, floor or building.
- City (`city`, text): City. Give at least one address field.
- State (`state`, text): State or region, such as FL.
- ZIP code (`zip_code`, text): ZIP or postal code.
- Phone (`phone`, text): Main phone number.
- Website (`website`, text): Website address.
- Site name (`site_name`, text): The name of the company's first site. Defaults to Main.

**Outputs**

- `company` (object): The company

**Example output**

```json
{
  "company": {
    "address_line1": "140 S. Village Ave.",
    "address_line2": "8th Floor",
    "city": "Tampa",
    "country": "United States",
    "created_at": "2024-02-14T16:30:00Z",
    "default_contact": "Ana Lopez",
    "default_contact_id": 3120,
    "deleted": false,
    "id": 250,
    "identifier": "AcmeCorp",
    "name": "Acme Corporation",
    "phone": "8135550100",
    "state": "FL",
    "status": "Active",
    "territory": "Tampa Office",
    "types": [
      "Client"
    ],
    "updated_at": "2026-10-20T09:12:44Z",
    "website": "www.acme.example",
    "zip": "33880"
  }
}
```

### Create contact

Add a contact, at a company or on their own, with an email address and phone number.

**Inputs**

- First name (`first_name`, text, required): Up to 30 characters.
- Last name (`last_name`, text): Up to 30 characters.
- Company (`company`, text): The company they work at. Pick one, or give its id or short ID.
- Job title (`title`, text): Such as Office Manager.
- Email (`email`, text): Their email address.
- Phone (`phone`, text): Their phone number.

**Outputs**

- `contact` (object): The contact

**Example output**

```json
{
  "contact": {
    "company": "Acme Corporation",
    "company_id": 250,
    "created_at": "2024-02-14T16:35:00Z",
    "email": "ana.lopez@acme.example",
    "first_name": "Ana",
    "id": 3120,
    "inactive": false,
    "last_name": "Lopez",
    "name": "Ana Lopez",
    "phone": "8135551234",
    "title": "Office Manager",
    "types": [
      "End User"
    ],
    "updated_at": "2026-10-21T11:00:00Z"
  }
}
```

### Create project

Start a project for a company on a project board, with its dates, billing method and manager.

**Inputs**

- Name (`name`, text, required): The project's name, up to 100 characters.
- Company (`company`, text, required): Pick one, or give its id or short ID (such as AcmeCorp).
- Project board (`board`, text, required): Pick one, or give its id or name.
- Estimated start (`estimated_start`, date, required): When the project should start.
- Estimated end (`estimated_end`, date, required): When it should finish.
- Billing method (`billing_method`, text): How the project is billed. One of: `ActualRates` (Actual rates (default)), `FixedFee` (Fixed fee), `NotToExceed` (Not to exceed), `OverrideRate` (Override rate). Default: `ActualRates`.
- Manager (`manager`, text): The project manager. Pick one, or give a member id or identifier.
- Contact ID (`contact_id`, text): The contact's id, from 'Search contacts', 'Create contact' or a trigger.
- Description (`description`, text): What the project is for.
- Budget hours (`budget_hours`, number): Hours budgeted, such as 1.5. From 0 to 10000.

**Outputs**

- `project` (object): The project

**Example output**

```json
{
  "project": {
    "actual_end": "",
    "actual_hours": 0.0,
    "actual_start": "",
    "billing_method": "ActualRates",
    "board": "Professional Services",
    "board_id": 12,
    "budget_hours": 40.0,
    "closed": false,
    "company": "Acme Corporation",
    "company_id": 250,
    "contact": "Ana Lopez",
    "created_at": "2026-10-28T15:00:00Z",
    "description": "Move Acme's mailboxes to Office 365.",
    "estimated_end": "2026-11-30T00:00:00Z",
    "estimated_start": "2026-11-02T00:00:00Z",
    "id": 812,
    "manager": "Jordan Smith",
    "name": "Office 365 migration",
    "percent_complete": 0.0,
    "status": "Open",
    "type": "Migration",
    "updated_at": "2026-10-28T15:00:00Z"
  }
}
```

### Create project ticket

Add a ticket to a phase of a project.

**Inputs**

- Project ID (`project_id`, text, required): The project's id, from 'Create project' or a trigger.
- Phase ID (`phase_id`, text, required): The phase's id, from 'Add project phase'.
- Summary (`summary`, text, required): A short title, up to 100 characters.
- Description (`description`, text): What needs doing.
- Priority (`priority`, text): Pick one, or give its id or name.
- Owner (`owner`, text): The member who owns it. Pick one, or give a member id or identifier such as jsmith.
- Budget hours (`budget_hours`, number): Hours budgeted, such as 1.5. From 0 to 10000.

**Outputs**

- `project_ticket` (object): The project ticket

**Example output**

```json
{
  "project_ticket": {
    "actual_hours": 0.0,
    "board": "Professional Services",
    "budget_hours": 4.0,
    "closed": false,
    "company": "Acme Corporation",
    "company_id": 250,
    "contact": "Ana Lopez",
    "created_at": "2026-10-28T15:02:00Z",
    "id": 48230,
    "owner": "Jordan Smith",
    "phase": "Planning",
    "phase_id": 3301,
    "priority": "Priority 3 - Normal Response",
    "project": "Office 365 migration",
    "project_id": 812,
    "status": "Open",
    "summary": "Inventory mailboxes",
    "updated_at": "2026-10-28T15:02:00Z",
    "wbs_code": "1.1"
  }
}
```

### Create ticket

Open a service ticket for a company, on a board, with a description, priority, owner and due date.

**Inputs**

- Summary (`summary`, text, required): A short title, up to 100 characters.
- Company (`company`, text, required): Pick one, or give its id or short ID (such as AcmeCorp).
- Board (`board`, text): The service board. Pick one, or give its id or name. Leave empty for the default board.
- Status (`status`, text): Pick a board to see its statuses, or type a status name such as In Progress.
- Type (`ticket_type`, text): The ticket type. Pick a board to see its types, or give an id or name.
- Contact ID (`contact_id`, text): The contact's id, from 'Search contacts', 'Create contact' or a trigger.
- Priority (`priority`, text): Pick one, or give its id or name.
- Owner (`owner`, text): The member who owns it. Pick one, or give a member id or identifier such as jsmith.
- Description (`description`, text): The first discussion note: what the customer needs.
- Internal analysis (`internal_analysis`, text): A first note for staff only.
- Severity (`severity`, text): How serious it is for the customer. One of: `Low`, `Medium`, `High`.
- Impact (`impact`, text): How widely it affects the customer. One of: `Low`, `Medium`, `High`.
- Due date (`required_date`, date and time): When it must be done by.
- Budget hours (`budget_hours`, number): Hours budgeted, such as 1.5. From 0 to 10000.

**Outputs**

- `ticket` (object): The ticket

**Example output**

```json
{
  "ticket": {
    "actual_hours": 0.5,
    "board": "Help Desk",
    "board_id": 1,
    "budget_hours": 1.5,
    "closed": false,
    "closed_at": "",
    "closed_by": "",
    "company": "Acme Corporation",
    "company_id": 250,
    "company_identifier": "AcmeCorp",
    "contact": "Ana Lopez",
    "contact_email": "ana.lopez@acme.example",
    "contact_id": 3120,
    "contact_phone": "8135551234",
    "created_at": "2026-10-28T13:58:40Z",
    "created_by": "Email Connector",
    "id": 48211,
    "impact": "Medium",
    "item": "Offline",
    "owner": "Jordan Smith",
    "owner_id": 145,
    "priority": "Priority 3 - Normal Response",
    "priority_id": 4,
    "record_type": "ServiceTicket",
    "required_date": "2026-11-02T17:00:00Z",
    "resources": "jsmith",
    "severity": "Medium",
    "source": "Phone",
    "status": "New",
    "status_id": 16,
    "subtype": "Printer",
    "summary": "Printer on 2nd floor offline",
    "team": "Tier 1",
    "type": "Hardware",
    "updated_at": "2026-10-28T14:05:12Z",
    "updated_by": "jsmith"
  }
}
```

### Delete record

Delete a ticket, project ticket, project, company, contact, time entry or activity for good.

**Inputs**

- Record type (`record_type`, text, required): What kind of record to delete. Check it matches the id. One of: `service_ticket` (Service ticket), `project_ticket` (Project ticket), `project`, `company`, `contact`, `time_entry` (Time entry), `activity`.
- Record ID (`record_id`, text, required): The record's id (a ticket's number), from an earlier step or a trigger.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `record_id` (number): The deleted record's id
- `record_type` (text): The kind of record deleted

**Example output**

```json
{
  "deleted": true,
  "record_id": 48211,
  "record_type": "service_ticket"
}
```

### Get company

Get a company by its id or short ID, with address, status and types.

**Inputs**

- Company (`company`, text, required): Pick one, or give its id or short ID (such as AcmeCorp).

**Outputs**

- `company` (object): The company

**Example output**

```json
{
  "company": {
    "address_line1": "140 S. Village Ave.",
    "address_line2": "8th Floor",
    "city": "Tampa",
    "country": "United States",
    "created_at": "2024-02-14T16:30:00Z",
    "default_contact": "Ana Lopez",
    "default_contact_id": 3120,
    "deleted": false,
    "id": 250,
    "identifier": "AcmeCorp",
    "name": "Acme Corporation",
    "phone": "8135550100",
    "state": "FL",
    "status": "Active",
    "territory": "Tampa Office",
    "types": [
      "Client"
    ],
    "updated_at": "2026-10-20T09:12:44Z",
    "website": "www.acme.example",
    "zip": "33880"
  }
}
```

### Get contact

Get a contact with their company, email address and phone number.

**Inputs**

- Contact ID (`contact_id`, text, required): The contact's id, from 'Search contacts', 'Create contact' or a trigger.

**Outputs**

- `contact` (object): The contact

**Example output**

```json
{
  "contact": {
    "company": "Acme Corporation",
    "company_id": 250,
    "created_at": "2024-02-14T16:35:00Z",
    "email": "ana.lopez@acme.example",
    "first_name": "Ana",
    "id": 3120,
    "inactive": false,
    "last_name": "Lopez",
    "name": "Ana Lopez",
    "phone": "8135551234",
    "title": "Office Manager",
    "types": [
      "End User"
    ],
    "updated_at": "2026-10-21T11:00:00Z"
  }
}
```

### Get project

Get a project's status, company, manager, dates, hours and progress.

**Inputs**

- Project ID (`project_id`, text, required): The project's id, from 'Create project' or a trigger.

**Outputs**

- `project` (object): The project

**Example output**

```json
{
  "project": {
    "actual_end": "",
    "actual_hours": 0.0,
    "actual_start": "",
    "billing_method": "ActualRates",
    "board": "Professional Services",
    "board_id": 12,
    "budget_hours": 40.0,
    "closed": false,
    "company": "Acme Corporation",
    "company_id": 250,
    "contact": "Ana Lopez",
    "created_at": "2026-10-28T15:00:00Z",
    "description": "Move Acme's mailboxes to Office 365.",
    "estimated_end": "2026-11-30T00:00:00Z",
    "estimated_start": "2026-11-02T00:00:00Z",
    "id": 812,
    "manager": "Jordan Smith",
    "name": "Office 365 migration",
    "percent_complete": 0.0,
    "status": "Open",
    "type": "Migration",
    "updated_at": "2026-10-28T15:00:00Z"
  }
}
```

### Get ticket

Get a service ticket's summary, status, company, contact, owner, priority and dates.

**Inputs**

- Ticket number (`ticket_id`, text, required): The ticket's number, from 'Search tickets', 'Create ticket' or a trigger. A link to the ticket works too.

**Outputs**

- `ticket` (object): The ticket

**Example output**

```json
{
  "ticket": {
    "actual_hours": 0.5,
    "board": "Help Desk",
    "board_id": 1,
    "budget_hours": 1.5,
    "closed": false,
    "closed_at": "",
    "closed_by": "",
    "company": "Acme Corporation",
    "company_id": 250,
    "company_identifier": "AcmeCorp",
    "contact": "Ana Lopez",
    "contact_email": "ana.lopez@acme.example",
    "contact_id": 3120,
    "contact_phone": "8135551234",
    "created_at": "2026-10-28T13:58:40Z",
    "created_by": "Email Connector",
    "id": 48211,
    "impact": "Medium",
    "item": "Offline",
    "owner": "Jordan Smith",
    "owner_id": 145,
    "priority": "Priority 3 - Normal Response",
    "priority_id": 4,
    "record_type": "ServiceTicket",
    "required_date": "2026-11-02T17:00:00Z",
    "resources": "jsmith",
    "severity": "Medium",
    "source": "Phone",
    "status": "New",
    "status_id": 16,
    "subtype": "Printer",
    "summary": "Printer on 2nd floor offline",
    "team": "Tier 1",
    "type": "Hardware",
    "updated_at": "2026-10-28T14:05:12Z",
    "updated_by": "jsmith"
  }
}
```

### List board statuses

List a board's ticket statuses in board order, marking the closed ones.

**Inputs**

- Board (`board`, text, required): Pick one, or give its id or name.
- Include inactive (`include_inactive`, true/false): Also list inactive statuses. Default: `false`.

**Outputs**

- `count` (number): How many are returned
- `statuses` (list): The board's statuses

**Example output**

```json
{
  "count": 1,
  "statuses": [
    {
      "board_id": 1,
      "closed": false,
      "default": true,
      "id": 16,
      "inactive": false,
      "name": "New",
      "sort_order": 0,
      "time_entry_not_allowed": false
    }
  ]
}
```

### List boards

List the service boards tickets are worked on, or the project boards.

**Inputs**

- Boards (`board_kind`, text): Service boards, project boards, or both. One of: `service` (Service boards (default)), `project` (Project boards), `all` (Every board). Default: `service`.
- Include inactive (`include_inactive`, true/false): Also list inactive boards. Default: `false`.

**Outputs**

- `boards` (list): The boards
- `count` (number): How many are returned

**Example output**

```json
{
  "boards": [
    {
      "department": "Service",
      "id": 1,
      "inactive": false,
      "location": "Tampa Office",
      "name": "Help Desk",
      "project_board": false
    }
  ],
  "count": 1
}
```

### List configurations

List the devices and assets (configurations) recorded for a company, with serial numbers, IP addresses and warranty dates.

**Inputs**

- Company (`company`, text): Only this company's. Pick one, or give its id or short ID.
- Type (`configuration_type`, text): Only this configuration type, such as Server.
- Name contains (`name_contains`, text): Only configurations whose name contains this.
- Active only (`active_only`, true/false): Leave out inactive configurations. Default: `true`.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `configurations` (list): The configurations
- `count` (number): How many are returned

**Example output**

```json
{
  "configurations": [
    {
      "active": true,
      "company": "Acme Corporation",
      "company_id": 250,
      "contact": "Ana Lopez",
      "id": 5521,
      "installation_date": "2022-07-01T00:00:00Z",
      "ip_address": "10.0.0.12",
      "last_login_name": "ACME\\administrator",
      "mac_address": "00:1A:2B:3C:4D:5E",
      "manufacturer": "HPE",
      "model_number": "ProLiant DL380 Gen10",
      "name": "ACME-FS01",
      "os_type": "Windows Server 2022",
      "serial_number": "CZJ1234ABC",
      "status": "Active",
      "tag_number": "A-0042",
      "type": "Server",
      "updated_at": "2026-10-01T08:00:00Z",
      "warranty_expiration": "2027-06-30T00:00:00Z"
    }
  ],
  "count": 1
}
```

### List members

List the people who sign in to ConnectWise PSA, with their identifiers and email addresses.

**Inputs**

- Include inactive (`include_inactive`, true/false): Also list inactive members. Default: `false`.
- Include API members (`include_api_members`, true/false): Also list API members, which hold integrations' keys. Default: `false`.

**Outputs**

- `count` (number): How many are returned
- `members` (list): The members

**Example output**

```json
{
  "count": 1,
  "members": [
    {
      "email": "jordan.smith@msp.example",
      "first_name": "Jordan",
      "id": 145,
      "identifier": "jsmith",
      "inactive": false,
      "last_name": "Smith",
      "license": "Full",
      "name": "Jordan Smith",
      "title": "Service Technician"
    }
  ]
}
```

### List opportunities

List sales opportunities by status, company or sales rep.

**Inputs**

- Status (`status`, text): Only this status, such as Open.
- Company (`company`, text): Only this company's. Pick one, or give its id or short ID.
- Sales rep (`sales_rep`, text): Only this member's opportunities.
- Name contains (`name_contains`, text): Only opportunities whose name contains this.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `count` (number): How many are returned
- `opportunities` (list): The opportunities

**Example output**

```json
{
  "count": 1,
  "opportunities": [
    {
      "closed_date": "",
      "company": "Acme Corporation",
      "company_id": 250,
      "contact": "Ana Lopez",
      "created_at": "2026-10-27T10:00:00Z",
      "expected_close_date": "2026-12-15T00:00:00Z",
      "id": 615,
      "name": "Managed services renewal",
      "notes": "Renewal of the 2025 agreement.",
      "primary_sales_rep": "Jordan Smith",
      "primary_sales_rep_id": 145,
      "priority": "Clear Flag",
      "probability": "50",
      "rating": "Hot",
      "source": "Partner referral",
      "stage": "3.Quote",
      "status": "Open",
      "type": "Managed Services",
      "updated_at": "2026-10-27T10:00:00Z"
    }
  ]
}
```

### List ticket notes

List a ticket's notes with who wrote each and when.

**Inputs**

- Ticket number (`ticket_id`, text, required): The ticket's number, from 'Search tickets', 'Create ticket' or a trigger. A link to the ticket works too.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `count` (number): How many are returned
- `notes` (list): The ticket's notes

**Example output**

```json
{
  "count": 1,
  "notes": [
    {
      "contact": "",
      "created_at": "2026-10-28T14:05:12Z",
      "created_by": "jsmith",
      "id": 902114,
      "member": "Jordan Smith",
      "note_type": "internal",
      "text": "Power cycled the printer; it is back online.",
      "ticket_id": 48211
    }
  ]
}
```

### List time entries

List time logged on a ticket or by a member, between two dates.

**Inputs**

- Charged to (`charge_to_type`, text): Only time charged to this kind of record. One of: `ServiceTicket` (Service ticket (default)), `ProjectTicket` (Project ticket), `Activity`, `ChargeCode` (Charge code), `Company`.
- Charged to ID (`charge_to_id`, text): Only time on this ticket number (or activity or charge code id).
- Member (`member`, text): Only this member's time.
- From (`from_date`, date): Only time starting on or after this day.
- To (`to_date`, date): Only time starting on or before this day.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `count` (number): How many are returned
- `time_entries` (list): The time entries

**Example output**

```json
{
  "count": 1,
  "time_entries": [
    {
      "actual_hours": 0.5,
      "billable_option": "Billable",
      "charge_to_id": 48211,
      "charge_to_type": "ServiceTicket",
      "company": "Acme Corporation",
      "company_id": 250,
      "created_at": "2026-10-28T14:31:02Z",
      "id": 77120,
      "internal_notes": "",
      "member": "Jordan Smith",
      "member_id": 145,
      "notes": "Power cycled the printer.",
      "project_id": 0,
      "status": "Open",
      "ticket_id": 48211,
      "time_end": "2026-10-28T14:30:00Z",
      "time_start": "2026-10-28T14:00:00Z",
      "updated_at": "2026-10-28T14:31:02Z",
      "work_role": "Technician",
      "work_type": "Remote Support"
    }
  ]
}
```

### Log time

Log time a member worked on a ticket, project ticket, activity, charge code or company.

**Inputs**

- Member (`member`, text, required): The member who did the work. Pick one, or give a member id or identifier.
- Start (`time_start`, date and time, required): When the work started.
- Charge to (`charge_to_type`, text): What the time is for. One of: `ServiceTicket` (Service ticket (default)), `ProjectTicket` (Project ticket), `Activity`, `ChargeCode` (Charge code), `Company`. Default: `ServiceTicket`.
- Charge to ID (`charge_to_id`, text): The ticket number (or activity or charge code id) the time is for. Not needed for a company.
- Company (`company`, text): The company, when the time is charged to a company.
- End (`time_end`, date and time): When the work ended.
- Hours (`actual_hours`, number): Hours worked, when there is no end time, such as 0.5. From 0 to 10000.
- Notes (`notes`, text): What was done.
- Internal notes (`internal_notes`, text): Notes for staff only.
- Work type (`work_type`, text): Such as Remote Support. Pick one, or give its id or name.
- Billing (`billable_option`, text): Whether the time is billed. Left empty, the work type decides. One of: `Billable`, `DoNotBill` (Do not bill), `NoCharge` (No charge), `NoDefault` (No default).
- Add notes to the ticket (`add_to`, text): Also add the notes to the ticket as this kind of note. One of: `none` (Don't add it (default)), `discussion`, `internal` (Internal analysis), `resolution`. Default: `none`.

**Outputs**

- `time_entry` (object): The time entry

**Example output**

```json
{
  "time_entry": {
    "actual_hours": 0.5,
    "billable_option": "Billable",
    "charge_to_id": 48211,
    "charge_to_type": "ServiceTicket",
    "company": "Acme Corporation",
    "company_id": 250,
    "created_at": "2026-10-28T14:31:02Z",
    "id": 77120,
    "internal_notes": "",
    "member": "Jordan Smith",
    "member_id": 145,
    "notes": "Power cycled the printer.",
    "project_id": 0,
    "status": "Open",
    "ticket_id": 48211,
    "time_end": "2026-10-28T14:30:00Z",
    "time_start": "2026-10-28T14:00:00Z",
    "updated_at": "2026-10-28T14:31:02Z",
    "work_role": "Technician",
    "work_type": "Remote Support"
  }
}
```

### Search companies

Find companies by name, short ID or status.

**Inputs**

- Name contains (`name_contains`, text): Only companies whose name contains this.
- Identifier (`identifier`, text): Only the company with this short ID.
- Status (`status`, text): Only this status.
- Include deleted (`include_deleted`, true/false): Also return companies marked deleted. Default: `false`.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `companies` (list): The matching companies
- `count` (number): How many are returned

**Example output**

```json
{
  "companies": [
    {
      "address_line1": "140 S. Village Ave.",
      "address_line2": "8th Floor",
      "city": "Tampa",
      "country": "United States",
      "created_at": "2024-02-14T16:30:00Z",
      "default_contact": "Ana Lopez",
      "default_contact_id": 3120,
      "deleted": false,
      "id": 250,
      "identifier": "AcmeCorp",
      "name": "Acme Corporation",
      "phone": "8135550100",
      "state": "FL",
      "status": "Active",
      "territory": "Tampa Office",
      "types": [
        "Client"
      ],
      "updated_at": "2026-10-20T09:12:44Z",
      "website": "www.acme.example",
      "zip": "33880"
    }
  ],
  "count": 1
}
```

### Search contacts

Find contacts by name, company or email address. Inactive contacts are left out unless asked for.

**Inputs**

- Name contains (`name_contains`, text): Only contacts whose first or last name contains this.
- Company (`company`, text): Only this company's. Pick one, or give its id or short ID.
- Email (`email`, text): Only the contact with this email address.
- Include inactive (`include_inactive`, true/false): Also return inactive contacts. Default: `false`.
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `contacts` (list): The matching contacts
- `count` (number): How many are returned

**Example output**

```json
{
  "contacts": [
    {
      "company": "Acme Corporation",
      "company_id": 250,
      "created_at": "2024-02-14T16:35:00Z",
      "email": "ana.lopez@acme.example",
      "first_name": "Ana",
      "id": 3120,
      "inactive": false,
      "last_name": "Lopez",
      "name": "Ana Lopez",
      "phone": "8135551234",
      "title": "Office Manager",
      "types": [
        "End User"
      ],
      "updated_at": "2026-10-21T11:00:00Z"
    }
  ],
  "count": 1
}
```

### Search tickets

Find service tickets by board, status, company, owner, priority, summary or date, open ones by default.

**Inputs**

- Board (`board`, text): Only tickets on this board. Pick one, or give its id or name.
- Status (`status`, text): Only tickets in this status. Pick a board to see its statuses, or type a status name to match it on every board.
- Company (`company`, text): Only this company's. Pick one, or give its id or short ID.
- Owner (`owner`, text): Only tickets this member owns.
- Priority (`priority`, text): Only this priority.
- Open or closed (`state`, text): Open tickets, closed ones, or both. One of: `open` (Open tickets (default)), `closed` (Closed tickets), `all` (Open and closed tickets). Default: `open`.
- Summary contains (`summary_contains`, text): Only tickets whose summary contains this text.
- Created after (`created_after`, date and time): Only tickets entered at or after this time.
- Updated after (`updated_after`, date and time): Only tickets changed at or after this time.
- More conditions (`extra_conditions`, text): Anything else, in ConnectWise's conditions syntax, such as severity = "High".
- Order (`order`, text): Newest or oldest first. One of: `newest` (Newest first (default)), `oldest` (Oldest first). Default: `newest`.
- Most to return (`limit`, number): How many to return, 1 to 1000. Defaults to 50. From 1 to 1000.

**Outputs**

- `count` (number): How many are returned
- `tickets` (list): The matching tickets

**Example output**

```json
{
  "count": 1,
  "tickets": [
    {
      "actual_hours": 0.5,
      "board": "Help Desk",
      "board_id": 1,
      "budget_hours": 1.5,
      "closed": false,
      "closed_at": "",
      "closed_by": "",
      "company": "Acme Corporation",
      "company_id": 250,
      "company_identifier": "AcmeCorp",
      "contact": "Ana Lopez",
      "contact_email": "ana.lopez@acme.example",
      "contact_id": 3120,
      "contact_phone": "8135551234",
      "created_at": "2026-10-28T13:58:40Z",
      "created_by": "Email Connector",
      "id": 48211,
      "impact": "Medium",
      "item": "Offline",
      "owner": "Jordan Smith",
      "owner_id": 145,
      "priority": "Priority 3 - Normal Response",
      "priority_id": 4,
      "record_type": "ServiceTicket",
      "required_date": "2026-11-02T17:00:00Z",
      "resources": "jsmith",
      "severity": "Medium",
      "source": "Phone",
      "status": "New",
      "status_id": 16,
      "subtype": "Printer",
      "summary": "Printer on 2nd floor offline",
      "team": "Tier 1",
      "type": "Hardware",
      "updated_at": "2026-10-28T14:05:12Z",
      "updated_by": "jsmith"
    }
  ]
}
```

### Update ticket

Change a ticket's summary, board, status, priority, owner, contact, severity, impact, due date or budget. Fields left empty keep their values.

**Inputs**

- Ticket number (`ticket_id`, text, required): The ticket's number, from 'Search tickets', 'Create ticket' or a trigger. A link to the ticket works too.
- Summary (`summary`, text): A new title, up to 100 characters.
- Board (`board`, text): Move it to this board. Pick one, or give its id or name.
- Status (`status`, text): The new status. Pick a board to see its statuses, or type a status name, which is looked up on the ticket's board.
- Priority (`priority`, text): Pick one, or give its id or name.
- Owner (`owner`, text): The member who owns it. Pick one, or give a member id or identifier such as jsmith.
- Contact ID (`contact_id`, text): The contact's id, from 'Search contacts', 'Create contact' or a trigger.
- Severity (`severity`, text): How serious it is for the customer. One of: `Low`, `Medium`, `High`.
- Impact (`impact`, text): How widely it affects the customer. One of: `Low`, `Medium`, `High`.
- Due date (`required_date`, date and time): When it must be done by.
- Budget hours (`budget_hours`, number): Hours budgeted, such as 1.5. From 0 to 10000.

**Outputs**

- `ticket` (object): The ticket

**Example output**

```json
{
  "ticket": {
    "actual_hours": 0.5,
    "board": "Help Desk",
    "board_id": 1,
    "budget_hours": 1.5,
    "closed": false,
    "closed_at": "",
    "closed_by": "",
    "company": "Acme Corporation",
    "company_id": 250,
    "company_identifier": "AcmeCorp",
    "contact": "Ana Lopez",
    "contact_email": "ana.lopez@acme.example",
    "contact_id": 3120,
    "contact_phone": "8135551234",
    "created_at": "2026-10-28T13:58:40Z",
    "created_by": "Email Connector",
    "id": 48211,
    "impact": "Medium",
    "item": "Offline",
    "owner": "Jordan Smith",
    "owner_id": 145,
    "priority": "Priority 3 - Normal Response",
    "priority_id": 4,
    "record_type": "ServiceTicket",
    "required_date": "2026-11-02T17:00:00Z",
    "resources": "jsmith",
    "severity": "Medium",
    "source": "Phone",
    "status": "New",
    "status_id": 16,
    "subtype": "Printer",
    "summary": "Printer on 2nd floor offline",
    "team": "Tier 1",
    "type": "Hardware",
    "updated_at": "2026-10-28T14:05:12Z",
    "updated_by": "jsmith"
  }
}
```
