Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node operation updates an existing entry in a specified list by completely overwriting its data. It is useful when you want to replace all the values of a list entry with new information, ensuring that the entry reflects the latest state without retaining any previous data.

Common scenarios include:

  • Synchronizing updated contact or customer information in a CRM list.
  • Replacing outdated or incorrect data in a mailing list entry.
  • Overwriting multi-select or complex attribute values for a specific list item.

For example, if you have a list of users and want to update a user's profile details entirely, this operation allows you to specify the new data JSON object that will replace the current entry's content.

Properties

Name Meaning
List The UUID or slug identifier of the list to which the entry belongs.
Entry Id The UUID of the specific list entry that you want to update.
Data A JSON object containing the new data for the entry. This should include all fields to overwrite the existing entry values. Example structure: {"entry_values": {"attribute_id": "value", "multiselect_attribute": ["option1", "option2"]}}

Output

The node outputs a JSON object representing the updated entry as returned by the API after the overwrite operation. This typically includes the full details of the entry post-update, reflecting the new data values.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Attio API.
  • The node makes HTTP PUT requests to the Attio API endpoint corresponding to the list entry update.
  • Proper configuration of the API authentication token in n8n credentials is necessary.

Troubleshooting

  • Invalid UUID or Slug: If the provided List or Entry Id is incorrect or does not exist, the API will return an error indicating the resource was not found. Verify the identifiers are correct.
  • Malformed JSON in Data: The Data property must be valid JSON. Parsing errors will occur if the JSON is malformed. Use proper JSON formatting.
  • Insufficient Permissions: If the API key lacks permissions to update entries, authorization errors will occur. Ensure the API key has write access to the target list.
  • Empty or Missing Required Fields: Omitting required properties like List or Entry Id will cause the node to throw an error before making the request.
  • API Rate Limits: Frequent updates may hit rate limits imposed by the API. Implement retry logic or reduce request frequency if needed.

Links and References

Discussion