Attio icon

Attio

Interact with Attio API
Join our community

Actions52

Overview

This node interacts with the Attio API to list notes associated with a specified parent object and record. It is useful for workflows that need to retrieve and process notes linked to entities such as people, companies, or other objects within Attio.

Common scenarios include:

  • Fetching recent notes related to a contact or client for further automation.
  • Aggregating notes data for reporting or analysis.
  • Integrating note information into other systems or notifications.

For example, you could use this node to get the latest 10 notes attached to a specific person in your CRM and then send a summary email or update another database.

Properties

Name Meaning
Limit The maximum number of notes to return. Default is 10, maximum allowed is 50. Controls pagination size.
Offset The number of notes to skip before starting to return results. Default is 5. Useful for paginating through large result sets.
Parent Object The slug or ID identifying the type of parent object the notes belong to (e.g., "people").
Parent Record Id The unique identifier of the specific parent record whose notes are being listed.

Output

The node outputs an array of JSON objects, each representing a note retrieved from the Attio API. Each item contains the full note data as returned by the API under the json property.

No binary data output is produced by this operation.

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/v2/notes.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key will cause authentication errors.
    • Providing incorrect parent_object or parent_record_id values may result in empty responses or errors.
    • Exceeding the maximum limit (over 50) might be rejected by the API.

  • Error messages:

    • "Operation ... not found for resource ..." indicates a misconfiguration or unsupported operation/resource combination.
    • Network or request errors typically indicate connectivity or credential problems.

  • Resolutions:

    • Verify the API key is correctly set and has sufficient permissions.
    • Double-check the parent object slug and record ID for correctness.
    • Use pagination parameters (limit and offset) within allowed ranges.

Links and References

Discussion