ActionBrevoUpdated May 2026

How do I delete a Brevo contact?

Short answer: Drop the "Brevo → Delete Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 9 Brevo actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Email or Contact ID identifier	string	Required	The email address or numeric ID of the contact to delete

Sample request

{
  "identifier": "user@example.com"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Delete Contact.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Brevo

2 Google Sheets triggers

HubSpot → Brevo

18 HubSpot triggers

FAQ

Questions about Delete Contact.

What does the Delete Contact action do in Brevo?

Hard-deletes the contact and history. Irreversible — for GDPR right-to-erasure compliance workflows. For soft removal that preserves engagement history, unsubscribe or move to a suppression list instead.

What inputs does Delete Contact require?

Required: Email or Contact ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Brevo returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Delete Contact support batch operations?

Yes. Run Delete Contact inside a Loop node to process arrays. Tiny Command handles Brevo's rate limits automatically so you don't have to throttle manually.

More actions