Actions52
- Records Actions
- Comments Actions
- Objects Actions
- Attributes Actions
- List Attributes
- Create Attribute
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- GET target/identifier/attributes/attribute/statuses
- POST target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Lists Actions
- Entries Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
Overview
This node allows you to create a new attribute on either an object or a list within the Attio platform. Attributes are custom fields that can be added to objects or lists to store additional structured data, such as text, numbers, references, or currency information.
Common scenarios where this node is useful include:
- Extending your CRM or database schema by adding new fields to contacts (objects) or groups (lists).
- Customizing data capture forms by defining required or unique attributes.
- Automating metadata enrichment by dynamically creating attributes with default values based on workflow context.
For example, you might use this node to add a "Customer Tier" attribute to a list of clients or a "Preferred Contact Method" attribute to individual contact objects.
Properties
| Name | Meaning |
|---|---|
| Target | Specifies whether the attribute should be created on an Objects or Lists resource. Options: Objects, Lists. |
| Identifier | A UUID or slug string identifying the specific object or list to which the attribute will be added. |
| Data | JSON object defining the attribute's details and configuration. This includes properties like: - title: The display name of the attribute.- description: Description of the attribute.- api_slug: API identifier.- type: Attribute data type (e.g., text).- is_required: Whether the attribute is mandatory.- is_unique: Whether the attribute value must be unique.- is_multiselect: If multiple selections are allowed.- default_value: Default value configuration, supports dynamic templates.- config: Additional settings depending on type, e.g., currency code or allowed referenced objects. |
Output
The node outputs the JSON response returned by the Attio API after creating the attribute. This typically includes the full representation of the newly created attribute, containing its ID, metadata, configuration, and status.
The output structure is:
{
"json": {
// Full attribute object as returned by the API
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node sends HTTP requests to the Attio REST API endpoint (
https://api.attio.com). - Proper permissions on the API key are necessary to create attributes on the specified target resource.
Troubleshooting
- Error: Operation configuration not found — This indicates the selected operation or resource combination is invalid or misconfigured. Verify that the Resource is set to "Attributes" and Operation to "Create Attribute".
- Authentication errors — Ensure the API key credential is valid and has sufficient permissions.
- Invalid Identifier — The UUID or slug provided in the Identifier property must correspond to an existing object or list; otherwise, the API will reject the request.
- Malformed JSON in Data — The Data property must be valid JSON. Use proper escaping if entering manually.
- API rate limits or network issues — May cause request failures; retry or check connectivity.
Links and References
- Attio API Documentation — Official reference for attribute creation endpoints and payloads.
- n8n Documentation — General guidance on using credentials and HTTP request nodes.