Create Contact Attribute
brevo.create_attribute
ActionEmailconnection required
Calls the Brevo API with the connection's credentials.
Create a contact attribute so contacts can carry it. A contact attribute must exist before any contact can be given a value for it.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Brevo
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- sender_email, sender_name, sms_sender
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
category Which kind of attribute to create. 'normal' is the usual choice for contact data. | string | No | normal | one of "normal", "transactional", "category", "calculated", "global" | — |
name Name of the attribute, conventionally in capitals, e.g. FIRSTNAME. | string | Yes | — | — | PLAN_TIER |
attribute_type Value type of the attribute. Only meaningful for the normal, category and transactional categories. | string | No | — | one of "text", "date", "float", "boolean", "id", "category", "multiple-choice", "user" | — |
value Calculation formula for a calculated or global attribute, e.g. COUNT[BLACKLISTED,BLACKLISTED,<,NOW()]. | string | No | — | — | — |
enumeration The values a 'category' attribute may take, as objects of {"value": 1, "label": "Women"}. | array | No | — | array of object | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"category": "normal",
"name": "PLAN_TIER"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
created True when Brevo accepted the new attribute. | boolean | — |
name The attribute name that was created. | string | — |
category The category the attribute was created in. | string | — |
{
"category": "",
"created": false,
"name": ""
}See Create Contact Attribute run in a workflow.
In a technical demo we add the Brevo connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.