Actions26
- Agent Actions
- Conversation Actions
- Knowledge Base Actions
- Phone Actions
- Voice Actions
Conversation → Get Signed URL
AI-generatedOverview
This node integrates with the ElevenLabs Conversational AI API, enabling users to interact programmatically with various resources such as agents, conversations, voices, knowledge bases, and phone calls. Specifically, for the Conversation resource and the Get Signed URL operation, the node retrieves a signed URL associated with a conversation for a given agent. This signed URL can be used to securely access or share conversation data externally.
Common scenarios include:
- Generating secure links to share conversation recordings or transcripts with clients or team members.
- Integrating conversation data into external dashboards or applications that require authenticated access.
- Automating workflows where conversation URLs need to be fetched dynamically based on agent context.
Example: A customer support platform might use this node to fetch a signed URL for a specific conversation handled by an agent, then send that URL via email to a supervisor for review.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent for whom the signed URL is requested. |
Note: The provided properties JSON shows "Agent ID" twice but effectively it is a single required string input specifying the agent's ID.
Output
The node outputs a JSON object containing the signed URL related to the specified conversation and agent. The exact structure depends on the underlying API response but typically includes fields such as:
signedUrl: A string representing the secure URL to access the conversation.- Possibly metadata about expiration time or permissions tied to the URL.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the ElevenLabs Conversational AI API.
- Needs an API authentication token credential configured in n8n (referred generically as "an API key credential").
- The node relies on internal services for handling conversation operations, specifically the ConversationService module.
Troubleshooting
- Missing or invalid Agent ID: Ensure the Agent ID is correctly provided and corresponds to an existing agent in ElevenLabs.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API errors: Check network connectivity and ElevenLabs service status.
- Permission denied or expired tokens: If the signed URL cannot be generated, confirm that the agent has rights to generate URLs and that any token duration settings are appropriate.
Common error messages may include:
"Agent not found"— check the Agent ID."Unauthorized"— verify API credentials."Failed to generate signed URL"— inspect API limits or permissions.
Links and References
- ElevenLabs Conversational AI API Documentation (generic placeholder link)
- n8n documentation on Creating Custom Nodes
- Best practices for managing API keys and credentials in n8n
This summary is based solely on static analysis of the provided source code and property definitions.