Actions7
Overview
The VidNavigator node integrates with the VidNavigator API to perform various video-related operations such as searching videos, analyzing video content, retrieving transcripts, answering follow-up questions, transcribing non-YouTube videos, making custom HTTP requests, and dynamically running tools available in the VidNavigator MCP (Modular Command Platform).
Specifically, the "Run MCP Tool (Dynamic)" operation allows users to execute any tool exposed by the VidNavigator MCP by specifying the tool's name or ID along with JSON-formatted arguments. This flexibility enables advanced users to leverage custom or less common tools without needing dedicated node parameters for each.
Common scenarios:
- Automating video content analysis workflows.
- Extracting transcripts or summaries from videos.
- Running specialized video processing tools dynamically based on user needs.
- Integrating VidNavigator capabilities into broader automation pipelines.
Example:
A user wants to run a custom video enhancement tool available in VidNavigator MCP. They select the tool from the dynamic list and provide the required JSON arguments. The node executes the tool and returns the results for further processing.
Properties
| Name | Meaning |
|---|---|
| Tool Name or ID | Select a tool from the dynamically loaded list of available MCP tools or specify a tool ID via expression. |
| Arguments | JSON object containing the input arguments for the selected tool. |
Output
The node outputs an array of items where each item contains a json property holding the response from the VidNavigator API call.
- For the "Run MCP Tool (Dynamic)" operation, the
jsonfield contains the result of the executed tool call, typically structured as an object with the tool's output data. - If the response is not an object, it is wrapped inside a
dataproperty. - The node does not output binary data.
Example output structure:
{
"json": {
// Tool-specific response data here
}
}
Dependencies
- Requires an API key credential for VidNavigator API authentication.
- The node uses the base URL configured in the credentials to send JSON-RPC POST requests.
- No additional external dependencies beyond the VidNavigator API and n8n's HTTP request helper.
Troubleshooting
- No Tools Available: If the tool list is empty, ensure that the API credentials are correct and that the VidNavigator service has tools configured and accessible.
- Invalid JSON Arguments: When providing the "Arguments" property, ensure valid JSON syntax. Malformed JSON will cause parsing errors.
- API Authentication Errors: Verify that the API key credential is valid and has necessary permissions.
- Unsupported Operation Error: If an unsupported operation is selected or parameters are missing, the node returns an error object indicating the issue.
- Network Issues: Check connectivity to the VidNavigator API endpoint and firewall settings if requests fail.
Links and References
- VidNavigator API Documentation (hypothetical link for reference)
- n8n Expressions Documentation
- JSON-RPC Specification