Update Ticket
halopsa.update_ticket
ActionBusiness appsconnection required
Calls the HaloPSA API with the connection's credentials.
Change one or more properties of an existing ticket.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- HaloPSA
- Secret shape
- {"client_id": "…", "client_secret": "…"} or {"client_id": "…", "refresh_token": "…"}
- Config it needs
- base_url, auth_url, tenant, scope
- Resolved by
- config.connection_id, else node.connection_id
Configuration
7 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
ticket_id The ticket's numeric Halo id. | string | Yes | — | — | 1234 |
summary Replacement one-line summary for the ticket. | string | No | — | — | Printer on floor 2 is offline |
details Replacement description for the ticket. | string | No | — | — | — |
status_id Numeric id of the status to move the ticket to. | string | No | — | — | 9 |
agent_id Numeric id of the agent to reassign the ticket to. | string | No | — | — | 3 |
priority_id Numeric id of the priority to set on the ticket. | string | No | — | — | 2 |
fields Any further ticket properties to change, as a JSON object using Halo's own field names; merged over the fields above. | object | No | — | — | {"category_1":"Hardware"} |
- At least one of summary, details, status_id, agent_id, priority_id, fields must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"agent_id": "3",
"fields": {
"category_1": "Hardware"
},
"priority_id": "2",
"status_id": "9",
"summary": "Printer on floor 2 is offline",
"ticket_id": "1234"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ticket The ticket record Halo returned, in full. | object | — |
id The ticket's Halo id. | number | — |
{
"id": 0,
"ticket": {}
}See Update Ticket run in a workflow.
In a technical demo we add the HaloPSA connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.