Actions52
- Records Actions
- Comments Actions
- Objects Actions
- Attributes Actions
- List Attributes
- Create Attribute
- Get Attribute
- Update Attribute
- GET target/identifier/attributes/attribute/options
- POST target/identifier/attributes/attribute/options
- PATCH target/identifier/attributes/attribute/options/option
- GET target/identifier/attributes/attribute/statuses
- POST target/identifier/attributes/attribute/statuses
- PATCH target/identifier/attributes/attribute/statuses/status
- Lists Actions
- Entries Actions
- Workspace Members Actions
- Notes Actions
- Tasks Actions
- Webhooks Actions
- Threads Actions
Overview
This node operation retrieves threads from the Attio API, specifically fetching conversation threads related to records or entries within the system. It is useful for scenarios where you want to list or analyze communication threads linked to particular data objects such as people, companies, or other entities tracked in Attio.
Practical examples include:
- Fetching all discussion threads associated with a specific contact record.
- Retrieving threads tied to a particular entry in a list, such as notes or comments on a project task.
- Paginating through threads to display recent conversations in an external dashboard or CRM integration.
Properties
| Name | Meaning |
|---|---|
| Record Id | Filter threads to those associated with a specific record ID. Must be used together with the Object property. |
| Object | The type or slug of the object to filter threads by (e.g., "people"). Must be used together with the Record Id property. |
| Entry Id | Filter threads to those associated with a specific entry ID. Must be used together with the List property. |
| List | The list slug or ID to filter threads by. Must be used together with the Entry Id property. |
| Limit | Maximum number of thread results to return. Defaults to 10, maximum allowed is 50. Controls pagination size. |
| Offset | Number of thread results to skip before starting to return results. Defaults to 5. Used for pagination to fetch subsequent pages of threads. |
Output
The node outputs an array of JSON objects representing the retrieved threads. Each item corresponds to one thread and contains all the data fields returned by the Attio API for threads, such as thread ID, associated record or entry IDs, messages, timestamps, participants, and metadata.
If the API supports binary data in threads (e.g., attachments), this would be included in the output's binary field, but based on the static analysis, the primary output is JSON-formatted thread data.
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/threads. - Pagination parameters (
limitandoffset) are supported according to the API's pagination guide.
Troubleshooting
- Missing required parameters: The node requires either both
record_idandobjector bothentry_idandlistto filter threads properly. Omitting these pairs will likely cause errors or empty results. - Invalid IDs or slugs: Providing incorrect or non-existent record, object, entry, or list identifiers will result in no data or API errors.
- API authentication errors: Ensure the API key credential is valid and has sufficient permissions to access threads.
- Pagination issues: Using an offset beyond the available data range may return empty results; adjust
limitandoffsetaccordingly. - Network or API downtime: Standard HTTP request errors may occur if the Attio API is unreachable.
Common error messages typically relate to invalid parameters or authentication failures. To resolve, verify input values and credentials.