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 operation allows you to create a new select option for an attribute on either an object or a list within the Attio platform. It is useful when you want to dynamically add options to a select-type attribute, enabling more flexible and customizable data categorization or tagging.
Common scenarios:
- Adding a new category or status option to a dropdown attribute on a contact list.
- Extending the choices available in a custom attribute on objects such as companies or projects.
- Automating the enrichment of attribute options based on external data sources.
Example:
You have a "Priority" attribute on a list of tasks, and you want to add a new option "Medium" programmatically via n8n. This operation lets you send the new option title and attach it to the specified attribute.
Properties
| Name | Meaning |
|---|---|
| Target | Whether the attribute belongs to an "Objects" resource or a "Lists" resource. |
| Identifier | A UUID or slug identifying the specific object or list that owns the attribute. |
| Attribute | A UUID or slug identifying the attribute to which you want to add a select option. |
| Data | JSON object containing the data for the new select option. Typically includes a "title" field. |
Output
The output is a JSON object representing the newly created select option on the attribute. It contains all details returned by the Attio API about the created option, such as its ID, title, and any other metadata.
No binary data is output by this node operation.
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 configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrect UUIDs or slugs for target, identifier, or attribute parameters will result in "not found" or similar API errors.
- Malformed JSON in the "Data" property can cause parsing errors before sending the request.
Error messages:
"Operation ... not found for resource ...": Indicates a misconfiguration or unsupported operation/resource combination.- API errors related to authorization or resource existence should be checked against the provided parameters and API key validity.
Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Double-check the UUIDs/slugs used for target, identifier, and attribute fields.
- Ensure the JSON in the "Data" field is valid and properly formatted.
Links and References
- Attio API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general usage of HTTP Request nodes and credential setup)