Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node interacts with the Attio API to update an existing entry in a specified list by appending new data to it. It is useful when you want to add or modify specific fields of a list entry without overwriting the entire entry. For example, you might append additional attribute values or update multi-select options for a contact or item stored in a list.

Typical use cases include:

  • Adding new tags or categories to an existing list entry.
  • Updating partial information such as notes or custom attributes on a record.
  • Incrementally building up data on entries without losing existing data.

Properties

Name Meaning
List The UUID or slug identifier of the list that contains the entry to be updated.
Entry Id The UUID of the specific list entry that you want to update.
Data JSON object containing the data to append to the entry. This typically includes entry_values which map attribute IDs or keys to their new values. Example structure:
json { "entry_values": { "attribute_id_or_key": "value", "multiselect_attribute": ["option1", "option2"] } }

Output

The node outputs the JSON response from the Attio API after updating the entry. This JSON typically contains the updated entry details reflecting the appended changes.

If the API supports binary data output, it is not indicated here; thus, the output is purely JSON representing the updated entry state.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends authenticated HTTP PATCH requests to the Attio API endpoint for list entries.
  • No other external dependencies are required beyond standard HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or expired API token: The node will fail to authenticate. Ensure your API key credential is valid and has necessary permissions.
    • Incorrect List or Entry Id: If the provided UUIDs or slugs do not exist or are mistyped, the API will return errors indicating resource not found.
    • Malformed JSON in the Data property: The data field must be valid JSON. Parsing errors will cause the node to fail.

  • Error messages:

    • "Operation configuration not found": Indicates the selected operation is not properly configured or supported.
    • "Operation ... not found for resource ...": Means the combination of resource and operation is invalid.
    • API error responses (e.g., 400 Bad Request, 401 Unauthorized) will be returned as error messages. Check credentials and input parameters.

  • Resolution tips:

    • Double-check all UUIDs and slugs for correctness.
    • Validate JSON syntax in the Data property before running.
    • Refresh or re-enter API credentials if authentication fails.
    • Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion