Add Ticket Comment

syncro.add_ticket_comment
ActionBusiness appsconnection required

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

Add a comment to a ticket, either internal or visible to the customer.

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

6 fields, 2 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
body
The comment text; Syncro refuses a blank comment body.
stringYes——Replaced the toner cartridge and reprinted the test page.
subject
The comment's subject line, shown above the body in Syncro.
stringNo——On-site visit
tech
The technician name to record against the comment.
stringNo——Ada Lovelace
hidden
True keeps the comment internal; false makes it visible to the customer.
booleanNo———
do_not_email
True adds the comment without emailing the customer about it.
booleanNo———

Example configuration

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

{
  "body": "Replaced the toner cartridge and reprinted the test page.",
  "subject": "On-site visit",
  "tech": "Ada Lovelace",
  "ticket_id": 44050842
}

Output

One shape.

result

FieldTypeExample
id
The comment id.
number—
ticket_id
The ticket the comment was added to.
number—
subject
The comment's subject line.
string—
body
The comment text, as Syncro stored it.
string—
tech
The technician recorded against the comment.
string—
hidden
True when the comment is internal only.
boolean—
created_at
When the comment was added, as ISO-8601.
string—
{
  "body": "",
  "created_at": "",
  "hidden": false,
  "id": 0,
  "subject": "",
  "tech": "",
  "ticket_id": 0
}

See Add Ticket Comment 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.