Get Ticket

syncro.get_ticket
ActionBusiness appsconnection required

Calls the Syncro MSP API with the connection's credentials.

Read one ticket in full, with its comments and line items.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Syncro MSP
Secret shape
the API token, or {"api_key": "…"}
Config it needs
subdomain, base_url
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.

FieldTypeRequiredDefaultConstraintsExample
ticket_id
The Syncro ticket id, which every ticket node emits as 'id'.
numberYes—≥ 144050842

Example configuration

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

{
  "ticket_id": 44050842
}

Output

One shape.

result

FieldTypeExample
id
The ticket id, which the other ticket nodes take.
number—
number
The human-facing ticket number shown in Syncro.
number—
subject
The ticket's subject line.
string—
status
The ticket's current status, e.g. 'New' or 'Resolved'.
string—
priority
The ticket's priority, or null when none is set.
string—
problem_type
The problem type recorded on the ticket.
string—
customer_id
The customer the ticket belongs to.
number—
contact_id
The contact on the ticket, or null.
number—
user_id
The technician the ticket is assigned to, or null.
number—
due_date
When the ticket is due, as an ISO-8601 timestamp.
string—
resolved_at
When the ticket was resolved, or null.
string—
created_at
When the ticket was created, as an ISO-8601 timestamp.
string—
updated_at
When the ticket last changed, as an ISO-8601 timestamp.
string—
comments
The ticket's comments, as Syncro returned them.
array—
attachments
The ticket's attachments, as Syncro returned them.
array—
line_items
The ticket's billable line items.
array—
customer
The full customer record the ticket belongs to.
object—
{
  "attachments": [],
  "comments": [],
  "contact_id": 0,
  "created_at": "",
  "customer": {},
  "customer_id": 0,
  "due_date": "",
  "id": 0,
  "line_items": [],
  "number": 0,
  "priority": "",
  "problem_type": "",
  "resolved_at": "",
  "status": "",
  "subject": "",
  "updated_at": "",
  "user_id": 0
}

See Get Ticket run in a workflow.

In a technical demo we add the Syncro MSP connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.