Convert n8n workflows to FlowDot
Paste a workflow you exported from another platform. You get a FlowDot workflow and a report with one entry for every node: converted, converted with changes, or not supported and why. Nothing is run while it is converted.
Convert a workflow
How to move a workflow from n8n to FlowDot
Export the workflow from n8n, convert it here, read the report, then create it in your FlowDot account. Nothing is run while it is converted.
Get the workflow out of n8n
Open the workflow in n8n. In the canvas header, open the workflow menu (the three dots) and choose Download. n8n saves the workflow as a JSON file.
n8n's own documentation says an exported file includes credential names and ids, and can include authentication headers in HTTP Request nodes that were imported from cURL. Look through the file before you paste it anywhere.
How the pieces correspond
- A workflow in n8n is a workflow in FlowDot: nodes on a canvas, joined by connections.
- An n8n node becomes a FlowDot node when FlowDot has one that does the same job. The table lists each one.
- An n8n trigger does not become a node. FlowDot has no start node. A workflow starts when you run it, when a schedule runs it, or when its inbound URL is called.
- An n8n expression is kept as written. Where a FlowDot input needs its value, the converter adds a small Code node that returns the value and wires it in.
- An n8n app node, such as Google Sheets, corresponds to a tool in a FlowDot toolkit for that app. When such a toolkit exists the report names it, and you install it and connect your own account before the workflow runs. No app node converts today.
- A FlowDot recipe is a different thing: a list of steps an agent follows. The converter does not make recipes.
What converts today
Each n8n node type the converter has an entry for. Any other node type is reported as not supported, by name, and is never left out of the report.
| Node | Versions | In FlowDot | What to know |
|---|---|---|---|
| AI Agent | 1.6, 1.7, 1.8, 1.9, 2, 2.1, 2.2, 3, 3.1 | AI Agent node. | The prompt, the system message and attached HTTP Request tools are kept. The model is not: set a provider and model on the agent. |
| Code | 2 | Code node. | JavaScript is kept as written. Python is not supported. |
| Google Sheets | every version | Not converted. | It needs a FlowDot toolkit for the same app, and none exists yet. |
| HTTP Request, as a node and as an agent tool | 4.1, 4.2, 4.3, 4.4, 4.5 | HTTP Request node. | The method, URL, query parameters, timeout and a JSON, raw or name-and-value body are kept. Header values are removed. File, multipart and URL-encoded bodies are not supported. |
| If | 2, 2.1, 2.2, 2.3 | Conditional Branch (If) node. | The conditions, how they are combined and both outputs are kept. |
| Manual Trigger | 1 | No node. A FlowDot workflow starts when you run it. | |
| OpenAI Chat Model | 1, 1.1, 1.2, 1.3 | Part of the AI Agent node it is attached to. | The model name and its options are not carried over. |
| Schedule Trigger | 1.2, 1.3 | A FlowDot schedule, kept outside the workflow. | Converted when the rule is a five-field cron expression or an interval in minutes. Other rules are reported as not supported. |
| Sticky Note | 1 | Thought Bubble node. | The text and the size are kept. |
| Webhook | every version | Not converted yet. | FlowDot can start a workflow from a URL. Set up an inbound URL for the workflow in FlowDot. |
What you set yourself after converting
- Credentials do not move. The converter reads none of them. Add your own key or account in FlowDot for each service.
- Header values are removed, apart from a few that hold no secret, such as Content-Type. Add an Authorization header again in FlowDot.
- A secret typed straight into a URL or a request body in n8n is carried over as written. The converter cannot tell it from other text. Check those nodes.
- An AI Agent is left on the default provider and model. Set a provider and model on the agent before you run it from the editor.
- A schedule is kept outside the workflow. On a plan with scheduling it is created turned off, and you turn it on from the Schedules page. On a plan without scheduling it is listed in the report and not created.
- A converted node that reads the incoming item runs once and reads the first item. The report marks each node where that applies.