Get Contact: Brevo action

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	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.

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 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 Get Contact support batch operations?

Yes. Run Get 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