Update Contact
monica.update_contact
ActionCRM & salesconnection required
Calls the Monica API with the connection's credentials.
Replace a contact's details. Monica requires the whole record on an update, so a field left blank here is cleared on the contact.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- Monica
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
9 fields, 2 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 |
|---|---|---|---|---|---|
contact_id The contact this applies to, as the numeric id Monica returns. | string | Yes | — | — | 1 |
first_name The contact's first name; Monica requires it on every update. | string | Yes | — | — | Ada |
last_name The contact's last name. | string | No | — | — | Lovelace |
nickname The name you actually call the contact. | string | No | — | — | — |
description A short note about who the contact is, shown under their name in Monica. | string | No | — | — | — |
gender_id The numeric id of a gender defined on the Monica account. | string | No | — | — | 1 |
is_birthdate_known Whether Monica should record that the contact's birthdate is known. Monica requires this on every write, so leaving it off records it as unknown. | boolean | No | false | — | — |
is_deceased Whether the contact has died. Monica requires this on every write, so leaving it off records the contact as living. | boolean | No | false | — | — |
is_deceased_date_known Whether the date of death is known. Monica requires this on every write, so leaving it off records it as unknown. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact_id": "1",
"first_name": "Ada",
"gender_id": "1",
"is_birthdate_known": false,
"is_deceased": false,
"is_deceased_date_known": false,
"last_name": "Lovelace"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id Monica's numeric id for the contact. | number | — |
uuid The contact's UUID. | string | — |
object The record type, which is always 'contact'. | string | — |
hash_id The obfuscated id Monica uses in its own URLs. | string | — |
first_name The contact's first name. | string | — |
last_name The contact's last name, when one is set. | string | — |
nickname The contact's nickname, when one is set. | string | — |
complete_name The contact's full name as Monica renders it. | string | — |
description The short note recorded about the contact. | string | — |
gender The name of the contact's gender, when one is set. | string | — |
is_starred True when the contact is starred. | boolean | — |
is_partial True when the record is a partial contact. | boolean | — |
is_dead True when the contact is recorded as deceased. | boolean | — |
information Nested detail: relationships, dates, career and avatar. | object | — |
tags The tags on the contact. | array | — |
created_at When the contact was created. | string | — |
updated_at When the contact was last changed. | string | — |
{
"complete_name": "",
"created_at": "",
"description": "",
"first_name": "",
"gender": "",
"hash_id": "",
"id": 0,
"information": {},
"is_dead": false,
"is_partial": false,
"is_starred": false,
"last_name": "",
"nickname": "",
"object": "",
"tags": [],
"updated_at": "",
"uuid": ""
}See Update Contact run in a workflow.
In a technical demo we add the Monica connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.