Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Brevo, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands.
All connector references · Connect an account · AI setup and shared results
Browse contacts in the connected Brevo account.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Brevo connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| Offset | number | Optional. How many items to skip. Omit for 0; use a whole number from 0 to 1,000,000. Increase by the returned item count for the next page. |
| Limit | number | Optional. Maximum items requested in this page. Omit for 25; use a whole number from 1 to 100. The provider may return fewer items. |
Result
Returns contacts and count. Increase Offset by the returned contact count to continue.
Example
Choose your Brevo Account and add List contacts. Set Offset = 0; Limit = 10. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check key permissions, configured contact attributes and verified sender. Existing emails can reject Create contact. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Create a Brevo contact with optional configured attributes.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Brevo connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| text | Required. Email address of a new contact. The command does not request an overwrite of an existing contact. Twidget text limit: 32,768 characters; provider-specific limits may be lower. | |
| Attributes | object | Optional. Object of configured Brevo attribute names and values, such as {"FIRSTNAME":"Alex","LASTNAME":"Demo"}. Omit for email only. Supply an object, not text containing an object; all inputs together must fit within 64 KiB. |
Result
Returns the creation receipt, normally id. An overwrite of an existing email is not requested.
Example
Choose your Brevo Account and add Create contact. Set Email = "alex@example.test". These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Check key permissions, configured contact attributes and verified sender. Existing emails can reject Create contact. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Send a plain text transactional email using a Brevo sender.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Brevo connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| From | text | Required. One email address configured as a valid Brevo sender. The sender object is added automatically. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| To | text | Required. One recipient email address. This command does not accept a recipient list. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Subject | text | Required. Subject line for the transactional email. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Body | text | Required. Plain text email body; HTML, templates and attachments are not supported. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
Result
Returns the send receipt, normally messageId. Acceptance is not confirmation that the recipient received it.
Example
Choose your Brevo Account and add Send transactional email. Set From = "sender@example.test"; To = "alex@example.test"; Subject = "Demo workflow message"; Body = "Hello from the demo workflow.". These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Check key permissions, configured contact attributes and verified sender. Existing emails can reject Create contact. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Isolated tests and live debugging do not call connected providers. Enable Use live data only when you intend to contact the account. Writes, messages and AI requests can change real data or incur provider charges. A successful connection check does not prove access to every action. These examples explain the command contract; they are not evidence of a completed live provider request.
Salesforce commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Salesforce, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [A...
Connector command reference
Find detailed inputs, results, examples and common errors for every command in the 56-app connector library. Open an action below or use its help button in the editor. [Business connector setup](/docs/commands/business-connectors) · [AI connector setup](/docs/commands/ai-connectors) - [Google Drive]...
Cohere commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Cohere, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All c...
Google Gemini commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Google Gemini, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands....
Google Docs commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Google Docs, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [...
