Start free
ActionBrevoUpdated June 2026

How do I remove a Brevo contact from a list?

Short answer: You can remove contact from list in Brevo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Brevo Remove Contact from List action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this actionAll 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.

FieldTypeRequiredDescription
List ID
list_id
stringRequiredList ID. Example: 2
Email Addresses
emails
arrayRequiredList of contact emails to remove from the list. Each email is a separate entry — do NOT comma-separate them inside one value.
Sample request
{
  "list_id": "e.g. 2",
  "emails": "[\"john@example.com\", \"jane@example.com\"]"
}
Returns
{
  "contacts": {
    "failure": [],
    "success": [
      "john@example.com"
    ]
  }
}

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

Triggered by

Apps that pair well as the trigger for Remove Contact from List.

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

Gmail → Brevo
1 Gmail triggers
Slack → Brevo
13 Slack triggers
Google Sheets → Brevo
2 Google Sheets triggers
HubSpot → Brevo
18 HubSpot triggers
FAQ

Questions about Remove Contact from List.

What does the Remove Contact from List action do in Brevo?
Removes a contact from a specific list while preserving the contact record overall. Useful for "campaign ended → remove from the campaign list" lifecycle hygiene workflows.
What inputs does Remove Contact from List require?
Required: List ID, Email Addresses. 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 Remove Contact from List support batch operations?
Yes. Run Remove Contact from List inside a Loop node to process arrays. TinyCommand handles Brevo's rate limits automatically so you don't have to throttle manually.
More actions

Other Brevo actions.

Action
Add Contact to List
Adds an existing contact to a specific Brevo list. If the contact isn't in the account, this fails — use Create Contact first or the upsert pattern. List membership drives campaign targeting.
Action
Create Contact
Creates or upserts (when updateEnabled=true) a contact with email, attributes, and initial list memberships. The base hook for "form submission → push to Brevo" sync workflows.
Action
Delete Contact
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.
Action
Get Contact
Returns the contact by email or ID with all attributes and list memberships. The standard lookup for enrichment workflows or for resolving "is this email in Brevo already" before downstream decisions.
Action
List Contacts
Paginated contacts with filters by list, segment, modified date. For sync workflows that mirror Brevo into a warehouse, paginate with the modifiedSince filter to incrementally pull only touched records.
Action
List Brevo Lists
Returns every list in the connected account with name, contact count, folder. Useful for populating list-pickers at workflow setup or for inventorying audience structure.