Update Contact
egoi.update_contact
ActionEmailconnection required
Calls the E-goi API with the connection's credentials.
Change some columns of an existing contact; untouched fields stay.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- E-goi
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- list_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
14 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 |
|---|---|---|---|---|---|
contact_id The E-goi contact id, as returned by egoi.create_contact or a contact search. | string | Yes | — | — | 8f3a27ef26 |
list_id E-goi list to act on; leave blank to use the list named on the connection. | string | No | — | — | 12345 |
email Email address of the contact; E-goi uses it to detect duplicates in the list. | string | No | — | email format | jane@example.com |
first_name First name of the contact, available as a merge tag in campaigns. | string | No | — | — | — |
last_name Last name of the contact, available as a merge tag in campaigns. | string | No | — | — | — |
cellphone Mobile number as country code and number joined by a hyphen, e.g. 351-300404336. | string | No | — | matches ^\d{1,3}-\d{4,20}$ | 351-300404336 |
phone Landline number as country code and number joined by a hyphen, e.g. 351-300404336. | string | No | — | matches ^\d{1,3}-\d{4,20}$ | 351-300404336 |
status Subscription state of the contact across every channel. | string | No | — | one of "active", "inactive", "removed", "unconfirmed" | — |
email_status Whether the email channel of this contact may be sent to. | string | No | — | one of "active", "inactive" | — |
cellphone_status Whether the mobile channel of this contact may be sent to. | string | No | — | one of "active", "inactive" | — |
phone_status Whether the landline channel of this contact may be called. | string | No | — | one of "active", "inactive" | — |
birth_date Date of birth of the contact as an ISO-8601 calendar date, e.g. 1975-01-10. | string | No | — | — | 1975-01-10 |
language Language E-goi should address this contact in. | string | No | — | one of "en", "pt", "br", "es", "de", "hu", "fr" | — |
extra The account's custom fields, as rows of {"field_id": 1234, "value": "…"}. | array | No | — | array of string | — |
- At least one of email, first_name, last_name, cellphone, phone, status, email_status, birth_date, language, extra must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"birth_date": "1975-01-10",
"cellphone": "351-300404336",
"contact_id": "8f3a27ef26",
"email": "jane@example.com",
"list_id": "12345",
"phone": "351-300404336"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
contact_id The contact's E-goi id, ten hexadecimal characters. | string | — |
list_id The list the contact was written to. | string | — |
contact E-goi's own response object for the write. | object | — |
{
"contact": {},
"contact_id": "",
"list_id": ""
}Notes
- E-goi refuses a PATCH that carries nothing to change.
See Update Contact run in a workflow.
In a technical demo we add the E-goi connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.