Attio icon

Attio

Interact with Attio API

Overview

This node interacts with the Attio API to retrieve threads based on specified filters such as record ID, object type, entry ID, and list ID. It supports pagination through limit and offset parameters. This node is useful for scenarios where users need to fetch conversation threads or related discussions linked to specific records or entries within the Attio platform, enabling integration of communication data into workflows.

Use Case Examples

  1. Fetch threads related to a specific person record by providing the record ID and object type 'people'.
  2. Retrieve threads associated with a particular list entry by specifying the list and entry IDs.
  3. Paginate through threads by adjusting the limit and offset parameters to manage large datasets.

Properties

Name Meaning
Record Id Filter threads to those related to a specific record. Must be used with the 'Object' parameter.
Object Filter threads to those related to a specific record type, identified by slug or ID. Must be used with 'Record Id'.
Entry Id Filter threads to those related to a specific entry. Must be used with the 'List' parameter.
List Filter threads to those related to a specific list, identified by slug or ID. Must be used with 'Entry Id'.
Limit Maximum number of thread results to return, defaulting to 10 with a maximum of 50.
Offset Number of thread results to skip before returning, defaulting to 0 for pagination.

Output

JSON

  • json - The JSON response from the Attio API containing the list of threads matching the specified filters and pagination parameters.

Dependencies

  • Requires an API key credential for authentication with the Attio API.

Troubleshooting

  • Ensure that when using 'Record Id', the 'Object' parameter is also provided, and similarly, when using 'Entry Id', the 'List' parameter must be provided to avoid API errors.
  • Check that the 'Limit' parameter does not exceed the maximum allowed value of 50 to prevent request failures.
  • Verify that the API key credential is correctly configured and has the necessary permissions to access thread data.
  • If the node returns an error related to missing operation configuration, confirm that the selected operation is supported and correctly spelled.

Links

Discussion