Actions290
- Action Actions
- Agent Actions
- Appointment Actions
- Approval Process Actions
- Approval Process Rule Actions
- Asset Actions
- Attachment Actions
- Automation Actions
- Canned Text Actions
- Category Actions
- Client Actions
- Contract Actions
- Contract Rule Actions
- Contract Schedule Actions
- Contract Schedule Plan Actions
- Custom API Call Actions
- Feed Actions
- Field Info Actions
- Holiday Actions
- Invoice Actions
- Invoice Payment Actions
- Item Actions
- Knowledge Base Actions
- Lookup Actions
- Notification Actions
- Opportunity Actions
- Outcome Actions
- Product Branch Actions
- Product Component Actions
- Project Actions
- Purchase Order Actions
- Quotation Actions
- Raynet Actions
- Raynet Detail Actions
- Recurring Invoice Actions
- Release Actions
- Release Note Group Actions
- Reporting Actions
- Sales Order Actions
- Secure Secret Link Actions
- Security Check Actions
- Site Actions
- Supplier Actions
- Survey Actions
- Tag Actions
- Team Actions
- Ticket Actions
- Ticket Approval Actions
- Ticket Status Actions
- Ticket To-Do Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Top Level Actions
- Transcription Actions
- User Actions
- Webhook Actions
- Webhook Event Actions
Ticket → Update
AI-generatedSummary
Update a HaloPSA ticket by its ID, sending the selected fields and any dynamic JSON fields to the ticket update endpoint. Use this to change ticket ownership, status, details, priority, client or other supported fields in a workflow.
Inputs
- Ticket ID (required) — Numeric ID of the ticket to update.
- Update Fields — Optional fields to send, including assigned agent, categories, client, custom fields, details, estimate, flagged or on-hold state, priority, site, status, summary, team, and user. Agent, client, site, status, and user can be selected by name or ID; site and user choices depend on the selected client.
- Update Fields (JSON) — Optional JSON object for dynamic ticket fields. Values here override matching keys from Update Fields; expressions can be used.
Output shape
Not established by the provided source pack.
The execute implementation is shown only as a signature-level excerpt, so the response body and item handling cannot be determined.