Create ConnectWise Ticket Time Entry (API)
The Create ConnectWise Ticket Time Entry action records work against an existing ConnectWise Manage service ticket.
When to Use This Action
Use this action when you know the ticket and member IDs and need to record a specific time range or duration. Do not use it to add billing options or deductions because this action does not configure those fields.
How It Works
- The action validates IDs and requires UTC date and time values in
YYYY-MM-DD HH:MM:SSformat. - You provide either End Time or Duration in Minutes, but not both.
- The action calculates the missing end time or duration and sends one request to ConnectWise.
- The action stores the created time-entry object when ConnectWise succeeds.
Configuration
| Field | Description |
|---|---|
| ConnectWise Connection | Select the connection to use, or leave it blank to use the default. |
| Ticket ID | Keep the field locked to search ConnectWise tickets by ID or summary. Unlock it to enter a positive numeric ID or text expression. |
| Member ID | Keep the field locked to search ConnectWise members. Unlock it to enter a positive numeric ID or text expression. |
| Start Time | Required UTC date and time in YYYY-MM-DD HH:MM:SS format, such as 2026-09-18 01:12:00. |
| End Time | Optional UTC date and time in YYYY-MM-DD HH:MM:SS format. Supply this or Duration in Minutes. It must occur after Start Time. |
| Duration in Minutes | Optional positive number. Supply this or End Time. |
| Work Role ID | Keep the field locked to search ConnectWise work roles. Unlock it to enter a positive numeric ID or text expression. |
| Work Type ID | Keep the field locked to search ConnectWise work types. Unlock it to enter a positive numeric ID or text expression. |
| Notes | Optional customer-facing notes. Supports text expressions. |
| Internal Notes | Optional internal notes. Supports text expressions. |
| Error Handling | Choose what happens if ConnectWise rejects the request. |
For overnight work, set End Time to the following calendar date. The action rejects an end timestamp that is equal to or earlier than the start timestamp.
Returned Variables
When you configure Store the results in Variable, the created time entry can include:
| Property | Type | Description |
|---|---|---|
id | number | Created time-entry ID |
chargeToId | number | Service ticket ID |
chargeToType | string | ConnectWise charge target type |
member | object | Member reference |
timeStart | string | UTC start timestamp |
timeEnd | string | UTC end timestamp |
actualHours | number | Calculated duration in hours |
workRole | object | Work role reference, when returned |
workType | object | Work type reference, when returned |
notes | string or null | Customer-facing notes |
internalNotes | string or null | Internal notes |
status | string or null | Provider status |
FAQs
Which timezone does the action use?
The action treats every Start Time and End Time value as UTC. Enter both values in YYYY-MM-DD HH:MM:SS format without a timezone suffix.
Can I provide both an end time and a duration?
No. Supply exactly one so the action can calculate the other value consistently.