Actions7
Overview
The "Redirect Member to Node" operation in the Woztell Bot API 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 different conversation path after an external event.
- Jumping to a specific node to handle special cases or errors.
- Controlling chatbot navigation from external systems or workflows.
For example, if a user needs to be redirected to a troubleshooting node after reporting an issue, this operation can send them directly there without requiring manual input.
Properties
| Name | Meaning |
|---|---|
| Channel | The communication channel in Woztell where the member exists. Can be selected from a searchable list or specified by ID. |
| Recipient ID | The unique identifier of the recipient/member in the integration (e.g., WhatsApp phone number with country code, Facebook PSID). Phone numbers are sanitized to remove special characters and spaces before sending. |
| Chatbot Tree | The target chatbot tree to which the member should be redirected. Can be selected by ID or from a searchable list. |
| 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. Defaults to true. |
| Send Response | Boolean flag indicating whether to send a response message after redirection. Defaults to true. |
| Run Post Action | Boolean flag indicating whether to execute post-actions configured on the target node after redirection. Defaults to true. |
| Metadata | Optional key-value pairs of metadata to pass along with the redirect. This metadata can be accessed in the target node via this.agendaMeta. Multiple metadata entries can be added. |
Output
The node outputs JSON data representing the result of the redirect operation. This typically includes confirmation of the redirect action and any relevant response data from the Woztell API.
If the node supports binary data output, it would represent files or media related to the redirect operation, but based on the provided information, the output is primarily JSON structured data confirming the redirect.
Dependencies
- Requires an API key credential for authenticating with the Woztell API.
- Needs access to the Woztell platform's base URL endpoint.
- Uses internal methods to search and load options for channels, trees, and nodes dynamically.
- The node expects the environment to support HTTP POST requests with JSON payloads.
Troubleshooting
- Invalid Recipient ID: If the recipient ID is malformed or missing country code (for phone numbers), the redirect may fail. Ensure phone numbers include country codes and are properly formatted.
- Node or Tree Not Found: Selecting a non-existent tree or node composite ID will cause errors. Use the dynamic search lists to pick valid options.
- API Authentication Errors: Missing or invalid API credentials will prevent the request from succeeding. Verify that the API key credential is correctly configured.
- Pre/Post Actions Disabled: If pre or post actions are disabled but expected to run, the chatbot flow might not behave as intended.
- 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)
- n8n Documentation on Custom Nodes
- GraphQL Query Reference (used internally for loading nodes)
This summary is based solely on static analysis of the provided source code and property definitions.