Actions20
Overview
This node integrates with the Tavus API to manage AI-driven video generation and related resources. Specifically, for the Persona - Get operation, it retrieves detailed information about a specific persona by its unique ID. This is useful when you want to fetch existing persona configurations, such as their system prompts, context, or other metadata, to use in workflows involving AI-generated conversations or videos.
Common scenarios:
- Fetching persona details to display or log them.
- Using persona data to customize AI interactions dynamically.
- Validating that a persona exists before creating conversations or replicas linked to it.
Example:
You have a persona ID from a previous step or external source, and you want to retrieve all associated data about this persona to decide how to proceed with generating AI-driven content or conversations.
Properties
| Name | Meaning |
|---|---|
| Persona ID | The unique identifier of the persona to retrieve. This is required to specify which persona's details to get. |
Output
The output is a JSON object representing the persona's full details as returned by the Tavus API. This typically includes fields such as:
id: The persona's unique identifier.persona_name: The name of the persona.system_prompt: The system prompt text defining the persona's behavior.pipeline_mode: The mode used for processing (e.g., "full" or "echo").context: Optional additional context for the persona.default_replica_id: The default replica associated with the persona.layers: Configuration layers as JSON.- Other metadata fields provided by the Tavus API.
The node outputs this data as an array of JSON objects (usually one object per execution item).
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Tavus API.
- Needs 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
- Error: "Properties must be valid JSON" — This error can occur if any JSON input fields (not applicable for this operation but relevant for others) are malformed. Ensure JSON inputs are correctly formatted.
- API request failures — If the persona ID does not exist or the API key is invalid, the node will throw an error. Verify the persona ID is correct and the API credentials are properly set.
- Network issues — Connectivity problems to the Tavus API endpoint will cause errors. Check network access and API availability.
- Permission errors — Insufficient permissions on the API key may prevent fetching persona data.
Links and References
- Tavus API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes (for understanding node development concepts)
If you need summaries for other operations or resources, feel free to ask!