Create Contact
xero.create_contact
ActionCRM & salesconnection required
Calls the Xero API with the connection's credentials.
Create one customer or supplier from a Xero contact object.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Xero
- Secret shape
- {"client_id": "…", "client_secret": "…", "refresh_token": "…"}
- Config it needs
- tenant_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
fields The Xero Contact object to send, in Xero's PascalCase, e.g. {"Name": "Acme Ltd", "EmailAddress": "ap@acme.io"}. | object | Yes | — | ≥ 1 characters | {"EmailAddress":"ap@acme.io","Name":"Acme Ltd"} |
tenant_id Xero organisation (tenant) id for this call; overrides the connection's. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"fields": {
"EmailAddress": "ap@acme.io",
"Name": "Acme Ltd"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
contact The contact as Xero returned it, in PascalCase. | object | — |
contact_id The Xero identifier of the contact. | string | — |
validation_errors Messages Xero attached to the record; empty when it was accepted. | array | — |
{
"contact": {},
"contact_id": "",
"validation_errors": []
}Notes
- Name is required and must be unique within the Xero organisation.
See Create Contact run in a workflow.
In a technical demo we add the Xero connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.