Update Contact
mailjet.update_contact
ActionEmailconnection required
Calls the Mailjet API with the connection's credentials.
Change a contact's name or its campaign exclusion. Mailjet does not allow the email address itself to be edited.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Mailjet
- Secret shape
- {"username": "<public API key>", "password": "<private API key>"} (+ "sms_token" for the SMS API)
- Config it needs
- sender_email, sender_name, sms_from, contacts_list_id, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 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 The contact to act on: Mailjet's numeric contact id, or the contact's email address. | string | Yes | — | — | jane@example.com |
name New display name for the contact. | string | No | — | — | — |
is_excluded_from_campaigns Exclude the contact from campaigns, or put it back in them. | boolean | No | — | — | — |
- At least one of name, is_excluded_from_campaigns must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact": "jane@example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
updated True when Mailjet applied the change. | boolean | — |
contact The contact record as it now stands. | object | — |
{
"contact": {},
"updated": false
}See Update Contact run in a workflow.
In a technical demo we add the Mailjet connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.