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 update an existing record in a specified object within the Attio platform by completely overwriting its data. It is useful when you want to replace all current values of a record with new ones, ensuring the record reflects the latest information without retaining any previous data.
Common scenarios include:
- Correcting or updating contact details in a "people" object.
- Replacing product information in an inventory system.
- Overwriting entries in custom objects where full refresh of data is required.
For example, you might update a person's record by providing their unique record ID and supplying a new set of attribute values that fully replace the old ones.
Properties
| Name | Meaning |
|---|---|
| Object | The identifier (UUID or slug) of the object the record belongs to. Example: people. |
| Record Id | The UUID of the specific record to update. |
| Data | JSON object containing the new values for the record's attributes. This will overwrite existing data. Example structure: json { "values": { "attribute_id_or_key": "value", "multiselect_attribute": ["option1", "option2"] } } |
Output
The node outputs the updated record as a JSON object under the json field. This output contains the full representation of the record after the update operation, including all attributes and their new values.
If the API supports binary data for records (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data representing record attributes.
Dependencies
- Requires an API key credential for authenticating with the Attio API.
- The node makes HTTP requests to the Attio REST API endpoint
https://api.attio.com. - Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Invalid or missing record ID: Ensure the record ID provided exists and is correctly formatted as a UUID.
- Incorrect object identifier: Verify the object slug or UUID is correct and accessible.
- Malformed JSON in the Data property: The JSON must be valid and properly structured; otherwise, parsing errors may occur.
- Insufficient permissions: The API key used must have rights to update records in the specified object.
Error messages:
"Operation ... not found for resource ...": Indicates a mismatch between selected resource and operation; verify selections."Operation configuration not found for ...": Internal misconfiguration; ensure the node version is up to date.- API errors related to authorization or validation will be returned from the Attio API and surfaced in the node output if "Continue on Fail" is enabled.