Get Ticket
halopsa.get_ticket
ActionBusiness appsconnection required
Calls the HaloPSA API with the connection's credentials.
Read one ticket by its Halo id.
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
1 field, 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 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"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 Get 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.