Delete Contact
brevo.delete_contact
ActionEmailconnection required
Calls the Brevo API with the connection's credentials.
Permanently delete a contact from the Brevo account. The contact is removed from every list it belongs to.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Brevo
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- sender_email, sender_name, sms_sender
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 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 |
|---|---|---|---|---|---|
identifier The contact to address — its email address by default, or the id, phone number or ext_id named by 'identifier_type'. | string | Yes | — | — | jane@example.com |
identifier_type How Brevo should read 'identifier'. Leave blank to let Brevo infer it from the value. | string | No | — | one of "email_id", "phone_id", "contact_id", "ext_id", "whatsapp_id", "landline_number_id" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"identifier": "jane@example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
deleted True when Brevo accepted the deletion. | boolean | — |
identifier The contact that was deleted. | string | — |
{
"deleted": false,
"identifier": ""
}See Delete Contact run in a workflow.
In a technical demo we add the Brevo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.