Actions20
Overview
This node integrates with the Tavus API to manage and interact with AI-driven personas, among other resources. Specifically, the Persona - List operation retrieves a paginated list of personas from the Tavus platform. This is useful for workflows that need to display, filter, or process multiple personas, such as managing AI characters for video generation or conversational agents.
Common scenarios include:
- Fetching a list of available personas to select one for further operations.
- Filtering personas by type (user-created or system-generated) to organize or audit them.
- Paginating through large sets of personas when building dashboards or reports.
Example: A user wants to retrieve 20 personas of type "User" on page 2 to display in an application interface.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of personas to return per page. Minimum 1, maximum 100. |
| Page | The page number to return, starting at 1. |
| Persona Type | Filter the personas by type. Options: User or System. If empty, no filtering applied. |
Output
The output is a JSON array where each item represents a persona object returned by the Tavus API. The exact structure depends on the API response but typically includes persona details such as ID, name, type, prompts, and configuration.
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 REST endpoints.
Troubleshooting
- Invalid JSON error: When providing JSON input properties (not applicable here for list), ensure valid JSON format to avoid parsing errors.
- API request failures: Could be due to invalid or missing API credentials, network issues, or incorrect parameter values.
- Pagination issues: Requesting a page number beyond available pages may return empty results.
- Filtering: Providing an invalid persona type value will likely result in no matches or an error.
To resolve:
- Verify API credentials are correctly set up.
- Check network connectivity.
- Confirm parameter values are within allowed ranges.
- Review API documentation for any changes in endpoint behavior.
Links and References
- Tavus API Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General REST API pagination concepts: https://swagger.io/docs/specification/2-0/describing-parameters/#pagination