Update Contact Properties

mailjet.update_contact_data

ActionEmailconnection required

Calls the Mailjet API with the connection's credentials.

Set custom property values on one contact. Only the properties named are touched; the rest keep their current values.

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

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
properties The property values to set, as a JSON object, e.g. {"firstname": "Jane"}. Each key must already exist as a contact property in Mailjet.	object	No	—	—	{"firstname":"Jane"}
data Advanced: Mailjet's own array of {"Name", "Value"} entries, sent verbatim instead of 'properties'.	array	No	—	array of object	—

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

{
  "contact": "jane@example.com",
  "properties": {
    "firstname": "Jane"
  }
}

One shape.

Field	Type	Example
updated True when Mailjet applied the properties.	boolean	—
contact_id Mailjet's numeric id for the contact.	string	—
data The contact-data record Mailjet returned.	object	—

{
  "contact_id": "",
  "data": {},
  "updated": false
}

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.