Create Ticket
syncro.create_ticket
ActionBusiness appsconnection required
Calls the Syncro MSP API with the connection's credentials.
Open a new ticket against a 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
10 fields, 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 |
|---|---|---|---|---|---|
customer_id The customer this record belongs to; syncro.list_customers emits it as 'id'. | number | Yes | — | ≥ 1 | 1 |
subject The ticket's subject line, which is what Syncro shows in every list. | string | No | — | — | Printer offline in reception |
status The status to open the ticket in; Syncro uses its default when blank. | string | No | — | — | New |
priority The ticket's priority; Syncro's stock scale runs '0 Urgent' to '3 Low'. | string | No | — | — | 2 Normal |
problem_type The problem type; Syncro's stock list is Virus, TuneUp, Hardware, Software and Other. | string | No | — | — | Hardware |
contact_id The contact to put on the ticket; syncro.create_contact emits it as 'id'. | number | No | — | ≥ 1 | 1 |
user_id The Syncro user to assign the ticket to. | number | No | — | ≥ 1 | 1 |
ticket_type_id The account's ticket type to open the ticket as. | number | No | — | ≥ 1 | 1 |
due_date When the ticket is due, as a date or an ISO-8601 timestamp. | string | No | — | — | 2026-03-01 |
properties Values for the account's custom ticket fields, keyed by the field's name. | object | No | — | — | {"Device Type":"Hard Drive"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": 1,
"customer_id": 1,
"due_date": "2026-03-01",
"priority": "2 Normal",
"problem_type": "Hardware",
"properties": {
"Device Type": "Hard Drive"
},
"status": "New",
"subject": "Printer offline in reception",
"ticket_type_id": 1,
"user_id": 1
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
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 | — |
{
"comments": [],
"contact_id": 0,
"created_at": "",
"customer_id": 0,
"due_date": "",
"id": 0,
"number": 0,
"priority": "",
"problem_type": "",
"resolved_at": "",
"status": "",
"subject": "",
"updated_at": "",
"user_id": 0
}Notes
- A Syncro ticket always belongs to a customer, so 'customer_id' is the one field this node cannot default.
See Create 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.