Create Customer
syncro.create_customer
ActionBusiness appsconnection required
Calls the Syncro MSP API with the connection's credentials.
Create a customer record for a company or a private person.
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
11 fields, none 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 |
|---|---|---|---|---|---|
business_name The company name; this alone is enough to create a business customer. | string | No | — | — | Acme Manufacturing |
firstname The person's first name, for a customer who is not a company. | string | No | — | — | Ada |
lastname The person's last name, for a customer who is not a company. | string | No | — | — | Lovelace |
email The customer's email address; Syncro rejects one it cannot parse. | string | No | — | email format | ada@acme.com |
phone The customer's main phone number. | string | No | — | — | +1 555 0100 |
mobile The customer's mobile number. | string | No | — | — | +1 555 0101 |
address The first line of the customer's street address. | string | No | — | — | 1 Market Street |
city The customer's city. | string | No | — | — | Ely |
state The customer's state, province or region. | string | No | — | — | Cambridgeshire |
zip The customer's postal or ZIP code. | string | No | — | — | CB7 4DL |
notes Free-text notes to store on the customer record. | string | No | — | — | Migrated from the old PSA. |
- At least one of business_name, firstname, lastname must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"address": "1 Market Street",
"business_name": "Acme Manufacturing",
"city": "Ely",
"email": "ada@acme.com",
"firstname": "Ada",
"lastname": "Lovelace",
"mobile": "+1 555 0101",
"notes": "Migrated from the old PSA.",
"phone": "+1 555 0100",
"state": "Cambridgeshire",
"zip": "CB7 4DL"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The customer id, which ticket and contact nodes take. | number | — |
business_name The company name, or null for a private person. | string | — |
firstname The customer's first name. | string | — |
lastname The customer's last name. | string | — |
fullname First and last name joined, as Syncro renders it. | string | — |
email The customer's email address. | string | — |
phone The customer's phone number. | string | — |
mobile The customer's mobile number. | string | — |
disabled True when the customer record is disabled. | boolean | — |
created_at When the customer was created, as ISO-8601. | string | — |
{
"business_name": "",
"created_at": "",
"disabled": false,
"email": "",
"firstname": "",
"fullname": "",
"id": 0,
"lastname": "",
"mobile": "",
"phone": ""
}Notes
- Syncro needs a name: a business_name on its own, or a firstname and lastname for a private person.
See Create Customer 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.