Actions23
- Typebot Actions
- Chat Actions
- Result Actions
- Workspace Actions
Overview
This node integrates with the Typebot.io API, a self-hosted chatbot builder platform that allows creating and managing chatbots with visual flows. Specifically, the "Continue Chat" operation under the "Chat" resource enables sending a message to an existing chat session identified by a session ID. This is useful for maintaining ongoing conversations with a chatbot, allowing users to continue interactions seamlessly.
Practical scenarios include:
- Continuing a customer support conversation where context from previous messages is preserved.
- Building multi-turn dialogues in automated workflows.
- Integrating chatbots into applications where users can resume chats without losing history.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the existing chat session to continue. |
| Message | The message text to send to the chatbot within the ongoing session. |
| Additional Fields | Optional extra parameters including: |
| - Stream Enabled | Enable streaming mode for real-time response updates (boolean). |
| - Prefilled Variables | Key-value pairs to prefill variables in the chatbot session. |
| - Result ID | An existing result ID to continue the conversation context. |
| - Theme | JSON object defining custom theme configuration for the chatbot UI. |
| - Settings | JSON object for custom settings to modify chatbot behavior or appearance. |
| - Icon | Emoji or URL string to set a custom icon for the chatbot. |
| - Typebot JSON | JSON configuration for importing or updating the chatbot definition. |
| - Export Format | Format for exporting results (CSV, JSON, Excel) — not directly relevant to Continue Chat. |
| - Filename | Custom filename for file uploads — not directly relevant here. |
| - File Size Limit MB | Maximum allowed file size for uploads in megabytes — not directly relevant here. |
Output
The node outputs a JSON object representing the response from the Typebot API after continuing the chat session. This typically includes updated chat state, bot responses, and any metadata related to the session continuation.
If streaming is enabled, the output may represent partial or incremental responses as they arrive in real time.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Typebot API.
- Needs the base API URL and an authentication token configured in the node credentials.
- The workspace ID is used internally to scope requests.
- The node sends HTTP requests via a proxy service hosted at
https://n8ntools.io/api/v1/proxy/typebot.
Troubleshooting
- Common issues:
- Invalid or expired session ID will cause errors when attempting to continue a chat.
- Missing or incorrect API credentials will prevent successful API calls.
- Malformed JSON in additional fields like theme or settings can cause parsing errors.
- Error messages:
"Unknown chat operation"indicates an unsupported operation was selected.- Network or authorization errors usually relate to invalid tokens or connectivity issues.
- Resolutions:
- Verify the session ID is correct and active.
- Ensure API credentials are properly configured and have necessary permissions.
- Validate JSON inputs before passing them to the node.