Actions20
Overview
The node integrates with the Tavus API to create and manage AI-driven conversations involving replicas and personas. Specifically, the "Conversation - Create" operation allows users to initiate a new conversation by specifying which replica will join and which persona it will use. This is useful for scenarios where automated interactive sessions or dialogues are needed, such as virtual assistants, customer support bots, or personalized video interactions.
For example, you can start a conversation where a specific AI replica adopts a defined persona to interact with users, optionally customizing the greeting, context, and other properties. The node handles sending the creation request to the Tavus API and returns the resulting conversation data.
Properties
| Name | Meaning |
|---|---|
| Replica ID | The unique identifier for the replica that will join the conversation (required). |
| Persona ID | The unique identifier for the persona that the replica will use in the conversation (required). |
| Callback URL | A URL that will receive webhooks with updates regarding the conversation state (optional). |
| Conversation Name | A name for the conversation (optional). |
| Conversational Context | Optional additional context appended to any context provided in the persona (optional). |
| Custom Greeting | An optional custom greeting that the replica will give once a participant joins the conversation. |
| Properties | Optional JSON object with additional properties to customize the conversation (optional). |
Output
The output of this operation is a JSON object representing the newly created conversation as returned by the Tavus API. It typically includes details such as the conversation's unique ID, status, associated replica and persona IDs, timestamps, and any other metadata provided by the API.
No binary data is output by this node operation.
Dependencies
- Requires an active connection to the Tavus API.
- Requires an API authentication token configured in n8n credentials to authorize requests.
- The node uses internal helper functions to make HTTP requests to the Tavus API endpoints.
Troubleshooting
- Invalid JSON in Properties: If the "Properties" field contains invalid JSON, the node will throw an error stating "Properties must be valid JSON". Ensure that the JSON syntax is correct before running.
- Missing Required Fields: Omitting required fields like "Replica ID" or "Persona ID" will cause the API request to fail. Make sure these are provided.
- API Authentication Errors: If the API key or token is missing or invalid, requests will fail with authorization errors. Verify your API credentials configuration.
- Callback URL Issues: If a callback URL is provided but unreachable or incorrect, webhook updates may not be received properly.
- Network or API Downtime: Network issues or Tavus API downtime can cause request failures; check connectivity and service status.
Links and References
- Tavus API Documentation (for detailed API usage and parameters)
- n8n Documentation on Creating Custom Nodes