Migrating from n8n
FluidGrids imports n8n workflow exports directly. The import converts what it can into FluidGrids nodes, keeps everything else as disabled placeholders so the shape of the workflow is kept, and shows a report of what needs your attention before anything is saved. The result is an ordinary FluidGrids workflow.
Import a workflow
- In n8n, download the workflow as JSON, or copy it.
- In FluidGrids, open My Workflows and select Import. Choose the file with Choose JSON file, or paste the JSON into Workflow JSON.
- FluidGrids recognises an n8n export automatically and shows n8n workflow detected with the import report: how many nodes convert directly, how many become placeholders, and how many connections you need to set up. Nothing is saved yet.
- Check the name (it is filled in from the export), then select Import workflow. The workflow is created as a draft; it does not run until you activate a version.
Importing needs permission to create workflows in the workspace, and the new workflow counts toward your plan's workflow limit. An export can have up to 1000 nodes, and node names must be unique, as they are in n8n.
The import report
| Section | What it lists |
|---|---|
| Summary | N of M nodes convert directly, the number of placeholders and the number of connections to set up |
| Placeholders | Nodes kept as disabled No-op nodes, each with the reason |
| Connections to create | Each node that needs a connection, with the FluidGrids connection type and the n8n credential it used (was … in n8n) |
| Expressions and conditions to review | Expressions and conditions that were kept as written or could not be converted, with the reason |
| Notes | Everything else worth knowing: store nodes to install, settings that were not carried over, pinned test data that was left out, and connections that were dropped or adjusted |
The same report is available through the API: previewN8nImport(workflowJson) returns the converted definition and the report without saving anything, and importWorkflow accepts the n8n export as its definitionJson, converts it and returns the report as n8nReport. See API reference.
From the CLI
The FluidGrids CLI (@fluidgrids/cli 2026.1113.1 or later) runs the same import from a terminal or a CI job. Sign in first with fluidgrids auth login, or set FLUIDGRIDS_TOKEN.
fluidgrids import my-n8n-workflow.json --from n8n --preview # the report only; nothing is saved
fluidgrids import my-n8n-workflow.json --from n8n --key my-flow
--preview prints the counts (n8n nodes, nodes that convert directly, placeholders, expressions to review and connections to set up) and each report item, and saves nothing. Without it, the workflow is created as a draft, as in the Import dialog. --key, --name and --description set the new workflow's key, name and description, and --allow-missing-nodes creates it even when it uses store nodes that are not installed yet. With --output json, the command prints one JSON object with the counts and the report items as diagnostics, for scripts.
What maps
| n8n | FluidGrids |
|---|---|
| Manual, Schedule, Webhook, Form, Error and Execute Workflow triggers | The matching built-in triggers |
| IF, Filter, Switch, Merge, Loop Over Items (Split in Batches), Edit Fields (Set), Code (JavaScript), HTTP Request, Wait, No Operation, Stop and Error, Execute Workflow, Respond to Webhook, Split Out, Limit, Sort and Remove Duplicates | The matching built-in nodes |
| Sticky notes | Canvas sticky notes, with their size and colour |
| The AI Agent node, with its chat model (OpenAI, Anthropic, Google Gemini, Groq, Mistral), memory (window buffer, Postgres) and HTTP Request or Code tools | The AI Agent node with the matching chat model, memory and tool nodes on its ports |
| Integration nodes for Airtable, Anthropic, Asana, Cloudflare, Discord, GitHub, GitLab, Gmail, Google Calendar, Google Sheets, HubSpot, Jira, Linear, LinkedIn, Mailchimp, Microsoft Teams, MongoDB, MySQL, Notion, OpenAI, PayPal, Pipedrive, Postgres, Redis, Salesforce, SendGrid, Shopify, Slack, Stripe, Telegram, Trello, Twilio, X (Twitter), WhatsApp and WooCommerce, including their AI-tool variants | The matching store node and operation |
| Any other node | A placeholder |
Store nodes must be installed in the workspace before the workflow can run. The report's Notes list each one to install from the Node Store. If the import says that the workflow uses nodes that are not installed in this workspace, install them and import again.
Some workflow settings carry over: the n8n execution timeout becomes the workflow timeout, and the save-execution-data settings become the workflow's data-saving settings. The error workflow setting is not carried over; choose the error workflow again in the workflow's settings.
Placeholders
A node FluidGrids cannot convert becomes a disabled No-op node with the original name. Its notes say that it was imported from n8n as a placeholder, give the n8n node type and the reason, and keep the original n8n parameters (without credentials), so you can rebuild it. Common reasons are a node FluidGrids has no equivalent for yet, a Python Code node (rewrite it in JavaScript), an integration node that is not available in your workspace, or an operation that does not exist on the FluidGrids node.
Expressions
FluidGrids uses the same {{ … }} syntax, so most expressions work after the import. The import rewrites node references to the converted nodes:
$('Node name'),$items('Node name')and$node["Node name"]point at the converted node;.item.json,.first().jsonand.last().jsondrop the trailing.json, and$node["Node name"].jsonbecomes$('…').item;$jsonand node reads are adjusted for nodes whose output is nested in FluidGrids, such as the HTTP Request body.
Expressions that cannot be converted are kept as written and listed under Expressions and conditions to review: n8n built-ins that FluidGrids expressions do not have (for example $prevNode, $runIndex, $itemIndex, $parameter, $binary and $secrets), references to nodes that are not in the workflow, and conditions that could not be imported. See Expressions.
Credentials
Credentials are never imported. Each node that needs one is listed under Connections to create, with the FluidGrids connection type and the n8n credential it used. Create those connections under Credentials, then select them on the nodes.
Finishing the migration
- Install the store nodes the report lists, create the connections and select them on their nodes.
- Replace each placeholder with a FluidGrids node, or remove it.
- Check the expressions and conditions the report listed.
- Run the workflow in test mode, then activate it.