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 updates an existing attribute on either an object or a list within the Attio platform. Attributes define metadata fields that can be attached to objects or lists, such as custom properties or data points relevant to your records.
Typical use cases include:
- Modifying the configuration of an attribute, for example changing its title, description, or validation rules.
- Updating whether an attribute is required or unique.
- Changing default values or other advanced settings like currency display or record references.
Practical example:
- You have a "Customer" object with an attribute "Loyalty Points". You want to update this attribute to make it required and set a new default value dynamically based on the current user.
Properties
| Name | Meaning |
|---|---|
| Target | Specifies whether the attribute belongs to an "Objects" resource or a "Lists" resource. Options: Objects, Lists. |
| Identifier | A UUID or slug identifying the specific object or list to which the attribute belongs. |
| Attribute | A UUID or slug identifying the attribute to update. |
| Data | JSON object containing the updated attribute data. This includes fields such as: - title: The name/title of the attribute.- description: Description text.- api_slug: API identifier.- is_required: Boolean indicating if the attribute is mandatory.- is_unique: Boolean indicating uniqueness.- default_value: Object defining default value type and template.- config: Additional configuration such as currency settings or allowed referenced objects.- is_archived: Boolean indicating if the attribute is archived. |
Output
The node outputs the JSON response from the Attio API representing the updated attribute object. This JSON contains all details of the attribute after the update, including any changes made.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node makes HTTP PATCH requests to the Attio API endpoint corresponding to the target (object or list), identifier, and attribute.
- The base URL used is
https://api.attio.com.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Incorrect UUID or slug in
IdentifierorAttributefields may result in "not found" errors. - Malformed JSON in the
Dataproperty can cause request failures. - Trying to update attributes on non-existent objects or lists will fail.
Error messages:
"Operation configuration not found": Indicates the selected operation is not properly configured; ensure you select the correct resource and operation."Operation ... not found for resource ...": Means the combination of resource and operation is invalid.- API errors returned from Attio will be passed through; check the error message for details such as permission issues or validation errors.
Resolution tips:
- Verify API credentials are valid and have sufficient permissions.
- Double-check UUIDs/slugs for correctness.
- Validate JSON syntax before inputting into the
Datafield. - Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.
Links and References
- Attio API Documentation — Official API docs for understanding attribute structure and update operations.
- n8n Documentation — For general guidance on using n8n nodes and handling credentials.