Create Contact

syncro.create_contact
ActionBusiness appsconnection required

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

Add a contact person under an existing 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

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

FieldTypeRequiredDefaultConstraintsExample
customer_id
The customer this record belongs to; syncro.list_customers emits it as 'id'.
numberYes—≥ 11
name
The contact's full name, as Syncro stores it in one field.
stringNo——Grace Hopper
email
The contact's email address; Syncro rejects one it cannot parse.
stringNo—email formatgrace@acme.com
phone
The contact's phone number.
stringNo——+1 555 0100
mobile
The contact's mobile number.
stringNo——+1 555 0101
address1
The first line of the contact's street address.
stringNo——1 Market Street
city
The contact's city.
stringNo——Ely
state
The contact's state, province or region.
stringNo——Cambridgeshire
zip
The contact's postal or ZIP code.
stringNo——CB7 4DL
notes
Free-text notes to store on the contact record.
stringNo——Prefers a phone call before any on-site visit.
enable_portal_user
True invites the contact to the Syncro customer portal.
booleanNo———

Example configuration

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

{
  "address1": "1 Market Street",
  "city": "Ely",
  "customer_id": 1,
  "email": "grace@acme.com",
  "mobile": "+1 555 0101",
  "name": "Grace Hopper",
  "notes": "Prefers a phone call before any on-site visit.",
  "phone": "+1 555 0100",
  "state": "Cambridgeshire",
  "zip": "CB7 4DL"
}

Output

One shape.

result

FieldTypeExample
id
The contact id.
number—
name
The contact's full name.
string—
email
The contact's email address.
string—
phone
The contact's phone number.
string—
mobile
The contact's mobile number.
string—
customer_id
The customer this contact belongs to.
number—
created_at
When the contact was created, as ISO-8601.
string—
{
  "created_at": "",
  "customer_id": 0,
  "email": "",
  "id": 0,
  "mobile": "",
  "name": "",
  "phone": ""
}

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