Create Ticket

halopsa.create_ticket
ActionBusiness appsconnection required

Calls the HaloPSA API with the connection's credentials.

Raise a new ticket on the service desk.

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

8 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
summary
One-line summary of the ticket, shown as its title.
stringYes——Printer on floor 2 is offline
details
The ticket's full description.
stringNo———
tickettype_id
Numeric id of the Halo ticket type to raise this ticket as.
stringNo——1
client_id
Only return records belonging to this client, by the client's numeric id.
stringNo——12
site_id
Numeric id of the site the ticket belongs to.
stringNo——7
user_id
Numeric id of the end user who raised the ticket.
stringNo——42
agent_id
Numeric id of the agent to assign the ticket to.
stringNo——3
fields
Any further ticket properties to set, as a JSON object using Halo's own field names; merged over the fields above.
objectNo——{"priority_id":2}

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "agent_id": "3",
  "client_id": "12",
  "fields": {
    "priority_id": 2
  },
  "site_id": "7",
  "summary": "Printer on floor 2 is offline",
  "tickettype_id": "1",
  "user_id": "42"
}

Output

One shape.

result

FieldTypeExample
ticket
The ticket record Halo returned, in full.
object—
id
The ticket's Halo id.
number—
{
  "id": 0,
  "ticket": {}
}

See Create 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.