Update Contact

messagebird.update_contact
ActionVoice & SMSconnection required

Calls the MessageBird API with the connection's credentials.

Change the fields you name on an existing contact and leave the rest as they were.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
MessageBird
Secret shape
the access key, or {"access_key": "…"}
Config it needs
originator, base_url
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
contact_id
The MessageBird id of the contact to change.
stringYes———
msisdn
A new phone number for the contact, in international format.
stringNo——+31612345678
first_name
A new given name.
stringNo———
last_name
A new family name.
stringNo———
custom_fields
Custom values to overwrite, as a JSON object using only custom1 to custom4.
objectNo———
  • At least one of msisdn, first_name, last_name, custom_fields must be set.

Example configuration

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

{
  "msisdn": "+31612345678"
}

Output

One shape.

result

The provider's response object, as returned.

Extra keys beyond the ones listed can appear.

{}

See Update Contact run in a workflow.

In a technical demo we add the MessageBird connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.