whapi

Overview

This node acts as a generic router for executing various actions related to the "Default" resource and operation. It delegates the execution logic to an external router function, which handles the specific action based on the input parameters. This design allows flexible extension by adding new actions without modifying the core execute method.

Common scenarios include integrating with APIs or services where multiple operations are grouped under a single resource, and the exact operation is determined dynamically at runtime. For example, it could be used to route different API calls depending on user input or workflow context.

Properties

Output

The output structure depends on the routed action executed by the external router. The json field will contain the response data returned from the invoked action. Since the node delegates execution, the output format is dynamic and corresponds to the specific API or service response handled by the router.

If binary data is returned by any routed action, it would typically represent files or media content fetched or generated during execution.

Dependencies

• Requires an external router module that contains the logic for dispatching and handling different actions.
• Uses common descriptions imported from a shared definitions file.
• Needs an API key or access token credential for authentication, configured in n8n credentials.

Troubleshooting

• If the node fails to execute, verify that the external router module is correctly implemented and accessible.
• Ensure the provided authentication token is valid and has sufficient permissions.
• Common errors may include missing or invalid credentials, unsupported operations, or network issues when calling external APIs.
• Check that the input parameters match expected values required by the routed actions.

Links and References

• No direct links available from the source code.
• Refer to the documentation of the external router module and the API/service being integrated for detailed usage instructions.