Actions125
- Ticket Actions
- Ticket Note Actions
- Ticket Attachment Actions
- Company Actions
- Company Note Actions
- Company Attachment Actions
- Contact Actions
- Resource (Employee) Actions
- Contract Actions
- Contract Note Actions
- Project Actions
- Project Note Actions
- Task Actions
- Task Note Actions
- Time Entry Actions
- Configuration Item Actions
- Configuration Item Note Actions
- Product Actions
- Opportunity Actions
- Quote Actions
- Quote Item Actions
- Service Call Actions
- Invoice Actions
- Subscription Actions
- Inventory Item Actions
- Purchase Order Actions
- Purchase Order Item Actions
Ticket → Update Ticket
AI-generatedSummary
Update a Ticket in Autotask by specifying its numeric Ticket ID and providing a JSON payload containing the fields to update. The Ticket ID is merged into the payload as Autotask requires it within the PATCH request body rather than the URL.
Inputs
- Ticket ID (required) — Numeric ID of the ticket to update.
- Update Payload (JSON) (required) — JSON object containing the fields and corresponding values to update on the ticket. The Ticket ID from above is automatically merged into this payload.
- Header Overrides — Optional collection to override request headers, including impersonation by specifying a different numeric Autotask resource ID.
Output shape
a single updated Ticket record as a JSON object
Returns the updated ticket object. The output is a single record per input item. If the API returns a wrapped response, the node unwraps it to expose the ticket entity directly.