Skip to main content

Update Halo Ticket

The Update Halo Ticket action updates an existing ticket in Halo PSA. Only the fields you specify will be updated; other fields remain unchanged.

Single API Call Action

This is a single API call action. You must supply the Ticket ID directly. If you need the system to detect a ticket number from an email and update it automatically, use Update Halo Ticket from Email instead. Learn more about the difference between workflow actions and single API call actions.

When to Use This Action

Use this action when:

  • You already have the ticket ID from a previous query or create action
  • You want to update specific fields on an existing ticket without adding email content
  • You need precise control over which fields are changed

Don't use this action for:

Configuration

Connection

FieldDescription
Halo ConnectionSelect the Halo connection to use for this action.

Ticket

FieldDescription
Ticket IDThe ID of the ticket to update. Required. Supports text expressions with {{variable}} syntax.

Content (Optional)

FieldDescription
SummaryUpdated ticket summary/title. Leave empty to keep the current value.
DetailsUpdated ticket description/details. Leave empty to keep the current value.

Classification (Optional)

FieldDescription
StatusUpdated ticket status. Leave empty to keep the current status.
PriorityUpdated ticket priority. Leave empty to keep the current priority.

Assignment (Optional)

FieldDescription
AgentUpdated assigned agent. Leave empty to keep the current assignment.
TeamUpdated assigned team. Leave empty to keep the current assignment.

Error Handling

FieldDescription
Error HandlingAction to take if the ticket update fails.
OptionBehavior
ExceptionHalt processing and report the error
BounceReturn the email/item to the sender
ContinueContinue to the next action
StopStop this rule but allow other rules to process
Stop AllStop all processing for this message

Returned Variables

When you configure Store the results in Variable, the result is an array containing the updated ticket. Access properties using index syntax.

Example usage: {{custom.myVariable[0].id}}

VariableTypeDescription
[0].idnumberThe ticket ID
[0].summarystringThe updated ticket summary
[0].detailsstringThe updated ticket details
[0].client_idnumberThe client ID
[0].client_namestringThe client name
[0].user_idnumberThe user/contact ID
[0].user_namestringThe user/contact name
[0].site_idnumberThe site ID
[0].site_namestringThe site name
[0].tickettype_idnumberThe ticket type ID
[0].status_idnumberThe status ID
[0].status_namestringThe status name
[0].priority_idnumberThe priority ID
[0].priority_namestringThe priority name
[0].agent_idnumberThe assigned agent ID
[0].agent_namestringThe assigned agent name
[0].team_idnumberThe assigned team ID
[0].team_namestringThe assigned team name
[0].datecreatedstringThe creation timestamp
[0].datelastupdatedstringThe last update timestamp

Example Use Cases

Close a Ticket After Processing

SettingValue
Ticket ID{{custom.ticket.id}}
StatusClosed

Escalate a Ticket's Priority

SettingValue
Ticket ID{{custom.ticket.id}}
PriorityHigh
TeamEscalations

Update Summary from Parsed Data

SettingValue
Ticket ID{{custom.existingTicket[0].id}}
Summary[Escalated] {{custom.existingTicket[0].summary}}

FAQs

Do I need to populate all fields when updating?

No. Only specify the fields you want to change. Any field left empty retains its current value.

What if the Ticket ID doesn't exist?

The action fails with an error. Configure Error Handling to control what happens next.

Why does the result use array index syntax?

The Halo API returns ticket data as an array even for single-ticket responses. Access the ticket at index [0].