Actions15
- Assistant Actions
- Assistant Event Actions
- Chat Actions
- Conversation Actions
- Voice Actions
Overview
The "Conversation - Get Many" operation in the Telnyx AI node allows users to retrieve multiple conversation records from the Telnyx AI platform. This operation is useful for scenarios where you want to list or filter conversations based on various metadata attributes, such as agent targets, assistant IDs, call control IDs, conversation channels, creation dates, and more.
Practical examples include:
- Fetching all conversations handled by a specific agent.
- Retrieving conversations associated with a particular assistant.
- Listing conversations created after a certain date.
- Filtering conversations by their channel type (e.g., phone calls).
- Limiting the number of returned conversations for pagination or performance reasons.
This operation supports flexible filtering and ordering, enabling tailored queries to suit different reporting or integration needs.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters to narrow down the conversations retrieved. Each filter corresponds to a query parameter sent to the API. |
| - Agent Target | Filter conversations by the agent's target identifier (e.g., phone number). |
| - Assistant ID | Filter by assistant ID; can be selected from a list of assistants or entered manually. |
| - Call Control ID | Filter by call control identifier. |
| - Conversation Channel | Filter by the channel of the conversation (e.g., phone_call). |
| - Created At | Filter by the creation datetime of the conversation, supporting operators like greater than or equal (gte). |
| - End User Target | Filter by the end user's target identifier (e.g., phone number). |
| - ID | Filter by the unique conversation ID. |
| - Last Message At | Filter by the datetime of the last message in the conversation, supporting operators like less than or equal (lte). |
| - Limit | Maximum number of results to return. Default is 50. Minimum value is 1. |
| - Name | Filter by the name of the conversation, supporting pattern matching (e.g., name=like.Voice%). |
| - Or | Apply OR conditions using PostgREST syntax to combine multiple filters logically. |
| - Order | Specify the order of the results by one or more fields, e.g., order=created_at.desc to sort by creation date descending. |
Output
The output consists of JSON data representing the list of conversations that match the specified filters. Each item in the output array corresponds to a conversation object containing its properties as returned by the Telnyx AI API.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Telnyx AI API.
- The base URL for requests is
https://api.telnyx.com. - Proper configuration of the API key credential within n8n is necessary for successful operation.
Troubleshooting
- Empty Results: If no conversations are returned, verify that your filters are correct and that conversations matching those criteria exist.
- Invalid Filter Syntax: Using incorrect filter syntax (especially in the "Or" field) may cause API errors. Ensure filters follow the expected PostgREST query format.
- Authentication Errors: Ensure the API key credential is valid and has the necessary permissions.
- Limit Exceeded: Setting a very high limit might lead to performance issues or API rate limiting. Use reasonable limits and paginate if needed.
- Date Format Issues: Date filters must be in a proper ISO 8601 format (e.g.,
2025-01-01) to be accepted.
Links and References
- Telnyx AI API Documentation
- PostgREST Query Syntax (for filter expressions)
- n8n Documentation on Credentials