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 updates a specific option of a select attribute belonging to either an object or a list in the Attio system. It allows users to modify properties of an existing select option, such as its title or archival status.
Common scenarios where this node is beneficial include:
- Renaming or updating the label of a select option used in custom attributes.
- Archiving or unarchiving options to control their availability without deleting them.
- Managing dynamic attribute options programmatically as part of data workflows.
For example, if you have a "Priority" attribute with options like "Low", "Medium", and "High", you can use this node to rename "Medium" to "Normal" or archive the "Low" option.
Properties
| Name | Meaning |
|---|---|
| Target | Specifies whether the attribute belongs to an "Objects" or "Lists". |
| Identifier | A UUID or slug identifying the specific object or list that owns the select attribute. |
| Attribute | A UUID or slug identifying the select attribute whose option you want to update. |
| Option | A UUID or the title of the select option to update. |
| Data | JSON object containing the fields to update for the select option. Typically includes: - title: The new title of the option.- is_archived: Boolean indicating if the option is archived. |
Output
The node outputs the JSON response returned by the Attio API after updating the select option. This JSON typically contains the updated details of the select option, reflecting changes such as the new title or archival status.
If the API supports binary data for this operation (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node sends authenticated HTTP PATCH requests to the Attio API endpoint corresponding to the target, identifier, attribute, and option specified.
- No additional external dependencies are required beyond network access to the Attio API.
Troubleshooting
- Invalid Identifier or Attribute: If the provided UUID or slug for the object/list or attribute is incorrect, the API will likely return a 404 error. Verify these identifiers carefully.
- Option Not Found: Specifying an option that does not exist will cause an error. Ensure the option UUID or title matches an existing select option.
- Malformed JSON in Data: The
Dataproperty must be valid JSON. Invalid JSON syntax will cause parsing errors before the request is sent. - Authentication Errors: Missing or invalid API credentials will result in authorization failures. Confirm the API key is correctly configured.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems. Implement retry logic or check network status.
Links and References
- Attio API Documentation — For detailed information on endpoints and data models.
- n8n Documentation — For general guidance on using n8n nodes and handling credentials.