Actions7
Overview
The "Redirect Member to Node" operation in the Bot API resource of this WOZTELL node allows redirecting a chatbot user (member) to a specific node within a chatbot tree. This is useful for dynamically controlling the flow of conversations by programmatically sending users to different parts of the chatbot based on logic or external triggers.
Common scenarios include:
- Redirecting a user to a specific part of a conversation after an external event.
- Jumping to a particular node to handle special cases or errors.
- Controlling chatbot navigation without user input.
For example, if a user needs to be redirected to a troubleshooting node after reporting an issue, this operation can send them directly there.
Properties
| Name | Meaning |
|---|---|
| Channel | The communication channel in WOZTELL where the member exists (e.g., WhatsApp, Facebook Messenger). Can be selected from a list or specified by ID. |
| Recipient ID | The unique identifier of the recipient/member in the integration, such as a phone number with country code for WhatsApp or PSID for Facebook Messenger. |
| Chatbot Tree | The target chatbot tree to which the member should be redirected. Can be selected by ID or from a list of available trees. |
| Chatbot Node Composite ID | The specific node within the chatbot tree to redirect the member to. Loaded dynamically based on the selected tree. |
| Run Pre Action | Boolean flag indicating whether to execute pre-actions configured on the target node after redirection. |
| Send Response | Boolean flag indicating whether to send a response message after redirection. |
| Run Post Action | Boolean flag indicating whether to execute post-actions configured on the target node after redirection. |
| Metadata | Optional key-value pairs of metadata to pass along with the redirection. This metadata can be accessed in the target node during execution via this.agendaMeta. Multiple metadata entries can be added. |
Output
The node outputs JSON data representing the result of the redirection request. This typically includes confirmation of the redirect action and any relevant status or error messages returned by the WOZTELL API.
If the node supports binary data output, it would represent files or media related to the chatbot interaction, but this operation primarily deals with JSON responses confirming the redirect.
Dependencies
- Requires an active WOZTELL API credential (an API key or token) configured in n8n to authenticate requests.
- Depends on WOZTELL's backend services for channels, chatbot trees, and nodes.
- Uses internal methods to search and load options for channels, trees, and nodes dynamically.
Troubleshooting
- Invalid Recipient ID: If the recipient ID is malformed or missing country code (for phone numbers), the API may reject the request. Ensure the recipient ID is correctly formatted without spaces or special characters.
- Node or Tree Not Found: Selecting a non-existent tree or node composite ID will cause errors. Use the dynamic lists to select valid options.
- Permission Errors: Missing or invalid API credentials will prevent successful calls. Verify that the WOZTELL API credential is correctly set up.
- Pre/Post Actions Failures: If pre or post actions are enabled but misconfigured in the chatbot, the redirect might not behave as expected.
- Metadata Format Issues: Metadata keys and values must be strings; incorrect types may cause unexpected behavior.
Links and References
- WOZTELL Official Documentation (general reference for API and chatbot configuration)
- WOZTELL API Reference (for detailed API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes