Actions26
- Agent Actions
- Conversation Actions
- Knowledge Base Actions
- Phone Actions
- Voice Actions
Conversation → List
AI-generatedOverview
The "Conversation - List" operation in this node allows users to retrieve a list of conversations from the ElevenLabs Conversational AI platform. This is useful for scenarios where you want to monitor, analyze, or process multiple conversation records programmatically. For example, you might use it to fetch recent conversations handled by a specific agent, filter conversations based on call success status, or aggregate conversation data for reporting.
Practical examples include:
- Fetching all conversations handled by a particular agent to review performance.
- Retrieving only successful calls for quality assurance.
- Limiting the number of conversations returned to avoid processing large datasets at once.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching conversations or limit the results to a specified maximum. |
| Limit | The maximum number of conversation records to return (applicable if "Return All" is false). |
| Filters | Collection of filters to narrow down the list of conversations: |
| Agent ID | Filter conversations by the specific agent's ID. |
| Call Successful | Filter conversations by call success status with options: Success, Failure, Unknown. |
Output
The output is an array of JSON objects representing conversation records. Each object contains details about a single conversation as returned by the ElevenLabs Conversational AI API. The exact structure depends on the API response but typically includes identifiers, timestamps, agent info, call status, and other metadata related to each conversation.
This operation does not output binary data.
Dependencies
- Requires an active connection to the ElevenLabs Conversational AI API.
- Requires an API key credential configured in n8n for authentication.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Exceeding API rate limits when requesting too many conversations at once.
- Providing invalid agent IDs in filters may result in empty responses.
- Setting "Limit" outside the allowed range (1-100) will likely cause validation errors.
Error messages:
- Errors related to authentication usually indicate missing or invalid API credentials.
- Validation errors occur if input parameters like "Limit" are out of bounds.
- Network or API errors may happen if the ElevenLabs service is unreachable.
To resolve these:
- Ensure your API key credential is correctly set up.
- Use valid agent IDs and correct filter values.
- Respect the allowed range for numeric inputs.
- Check network connectivity and ElevenLabs service status.
Links and References
- ElevenLabs Conversational AI API Documentation
- n8n Documentation on Creating Custom Nodes
- ElevenLabs Dashboard (for managing agents, voices, and API keys)