Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node integrates with the Attio API to update an existing record by appending new data to it. Specifically, the "Update Record (Append)" operation allows users to modify a record's attributes without overwriting the entire record, making it useful for incremental updates.

Common scenarios include:

  • Adding additional information or attributes to a contact or entity in a CRM system.
  • Appending tags, notes, or multi-select options to an existing record.
  • Updating records dynamically based on workflow outputs without losing previous data.

For example, you might append new selected options to a multi-select attribute of a person record or add textual notes to a customer profile.

Properties

Name Meaning
Object A UUID or slug identifying the object type the record belongs to (e.g., "people").
Record Id The UUID of the specific record to update.
Data JSON object containing the values to append to the record's attributes. Example structure:
```json
{
"values": {
"attribute_id_or_name": "Text value",
"multiselect_attribute": [
"Select option 1",
"Select option 2"
]
}
}
```

The Data property expects a JSON string that will be parsed and sent as the request body. It supports both single values and arrays for multi-select fields.

Output

The node outputs the JSON response from the Attio API after updating the record. The output contains the updated record data reflecting the appended changes.

The output structure is:

{
  "json": {
    // Updated record details as returned by the Attio API
  }
}

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Attio API.
  • The node sends HTTP PATCH requests to the Attio API endpoint for records.
  • The base URL used is https://api.attio.com.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Invalid or missing API credentials: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Malformed JSON in the Data property: The Data input must be valid JSON. Invalid JSON will cause parsing errors.
  • Record not found or invalid Record Id: Verify that the provided Record Id exists and is correct.
  • Object identifier issues: The Object property must be a valid UUID or slug corresponding to an existing object type.
  • API rate limits or network issues: Network failures or hitting API rate limits may cause errors; retry or check API usage.
  • Error messages from the API: The node surfaces error messages from the Attio API in the output JSON under an error field if continueOnFail is enabled.

Links and References

Discussion