N8N Tools - Typebot API
Actions23
- Typebot Actions
- Chat Actions
- Result Actions
- Workspace Actions
Overview
This node operation duplicates an existing Typebot chatbot by creating a copy under a new name within the same workspace. It is useful when you want to create a similar chatbot without rebuilding it from scratch, for example, to experiment with variations or to deploy multiple versions of a bot with minor differences.
Practical examples:
- Quickly cloning a customer support chatbot to customize it for a different product line.
- Creating a backup copy of a chatbot before making major changes.
- Duplicating a chatbot template to use as a starting point for new bots.
Properties
| Name | Meaning |
|---|---|
| Typebot ID | The unique identifier of the existing Typebot to duplicate. |
| Typebot Name | The name for the new duplicated Typebot. |
| Additional Fields | Optional extra settings including: |
| - Stream Enabled | Enable streaming for real-time responses (boolean). |
| - Prefilled Variables | Variables to prefill in the Typebot; each variable has a name and value. |
| - Result ID | Existing result ID to continue conversation (string). |
| - Theme | Custom theme configuration as JSON. |
| - Settings | Custom settings as JSON. |
| - Icon | Typebot icon, either an emoji or URL string. |
| - Typebot JSON | Full Typebot configuration as JSON (for import/update). |
| - Export Format | Format for exporting results (CSV, JSON, Excel) - not relevant for duplication but part of additional fields. |
| - Filename | Custom filename for file uploads (not relevant here). |
| - File Size Limit MB | File size limit in megabytes (not relevant here). |
For this operation, only Typebot ID and Typebot Name are required. Additional fields can be provided but are optional.
Output
The output is a JSON object representing the response from the Typebot API after duplicating the Typebot. This typically includes details about the newly created Typebot such as its ID, name, workspace association, and other metadata returned by the API.
Example structure (simplified):
{
"id": "new-typebot-id",
"name": "Duplicated Typebot Name",
"workspaceId": "workspace-id",
"icon": "...",
"createdAt": "...",
"updatedAt": "..."
}
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Typebot API.
- Needs the base URL and authentication token configured in the node credentials.
- The node uses an external proxy service (
https://n8ntools.io/api/v1/proxy/typebot) to forward requests to the Typebot API. - Workspace ID is required and obtained from credentials to associate the duplicated Typebot correctly.
Troubleshooting
Error: Unknown typebot operation: duplicateTypebot
This indicates the operation parameter was not set correctly. Ensure the operation is exactly "duplicateTypebot".Authentication errors (e.g., 401 Unauthorized)
Verify that the API key and token credentials are correctly configured and valid.Invalid Typebot ID
If the provided Typebot ID does not exist or is incorrect, the API will return an error. Double-check the ID.Missing required parameters
Both Typebot ID and Typebot Name must be provided. Omitting these will cause errors.API Proxy issues
Since the request goes through an external proxy, network issues or proxy downtime may cause failures.
Links and References
- Typebot Official Website β For general information about Typebot.
- Typebot API Documentation β For detailed API endpoints and usage.
- n8n Documentation β For more on using the Typebot API node in n8n.