ActionBrevoUpdated September 2026
How do I fetch a Brevo contact?
Short answer: You can get contact in Brevo by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Brevo Get Contact action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 email | Required | The email address. Used as the recipient or identifier depending on context. |
Sample request
{"email": "e.g. user@example.com"}
Returns
{"id": 123,"email": "john@example.com","listIds": [1,2],"attributes": {"LASTNAME": "Doe","FIRSTNAME": "John"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Contact.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Contact.
What does the Get Contact action do in Brevo?
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.
What inputs does Get Contact require?
Required: Email. 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 run history shows the failed step with its input and the error message Brevo returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Contact support batch operations?
Run Get Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Brevo's rate limits.
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.
ActionCreate 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.
ActionDelete 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.
ActionList 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.
ActionList 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.
ActionRemove Contact from List
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.