Migrate from n8n

The Floogos importer takes an n8n workflow’s JSON export and converts it into a native Floogos workflow: it maps the nodes, wires the connections, translates the expressions and leaves you an editable draft with a summary of what to review.

Not 1:1

n8n and Floogos are different engines: the import is a starting point, not an exact copy. The importer saves you most of the work, but review each node before activating the workflow in production.

Step by step

1. Export the workflow from n8n. Open the workflow → three-dot menu (top right) → Download. A .json file with the nodes and connections is downloaded.

2. Open the importer in Floogos. Go to Workflows → New Workflow → Import from n8n or Make (or the Import button on the workflow list).

3. Load the JSON. Drop the .json file into the dashed area, click to pick it, or paste the content into the text box. The format is detected automatically (n8n or Make).

4. Review the import report. Before creating the workflow, the importer shows a summary: how many nodes were mapped, how many need review, how many are unmapped, the coverage and the credentials to fill.

5. Create the draft and open the editor. Click Create draft and open. The editor opens with the imported flow, a summary note on the canvas and a comment on the workflow listing the pending actions.

6. Complete and activate. Review the flagged nodes, fill in credentials and placeholder URLs, and test the workflow with Run before activating.

Node statuses in the report

Status	Meaning
mapped	The node has a direct equivalent in Floogos and its config was imported.
review	Mapped to a real node, but something needs adjusting: an expression, the operation, or credentials.
unmapped	No clean equivalent in Floogos. A placeholder executescript node is left with the original parameters as reference.
note	Sticky note or grouping: kept as a visual, non-executable element.

What gets mapped automatically

• Triggers. Webhook, Form Trigger and Chat Trigger are recognized as entry points. Scheduled triggers (schedule/cron) become start. If a flow enters via webhook and returns no response, a webresponse node is added at the end.
• Decisions. IF and Switch → Decision node with the condition translated to JavaScript ({{data.field}} === 0).
• AI agents. LangChain nodes (model, tools, memory, output parser, vector store, embeddings, document loaders, text splitters) fold into the native aiAgent node. RAG uses the native store on pgvector.
• Integrations with a native node. Salesforce, Monday, ClickUp, Supabase, Microsoft Outlook/Teams/Excel, Google Sheets/Drive/Calendar and more are routed to the matching Floogos node by operation.
• Integrations without a native node. Facebook, YouTube, LinkedIn, Twitter/X, Twilio, Spotify, Zendesk, GitHub, Google Docs and others map to an HTTP node with the API base URL pre-filled and the method by operation.
• Expressions. {{ $json.field }} → {{ data.field }}.
• Loops. Floogos doesn’t run cyclic graphs: if the workflow had a loop (pagination do-while, Split In Batches return), the importer breaks the back edge and flags it so you rebuild it with an iterator node.

Always review

• Credentials. n8n credentials are not imported (for security). Create/link Floogos credentials on each node that needs them.
• Placeholder URLs and endpoints. HTTP nodes and generic integrations come with a base URL; complete the exact endpoint and the authentication.
• Translated expressions. Complex expressions may need tweaks (the importer flags nodes with expressions to review).
• Decision condition. Check that the branch logic is what you expect.

Known limitations

• Non-HTTP nodes (MongoDB, SSH, FTP) have no equivalent and stay as placeholders.
• Execute Command (running shell commands) is not imported: running arbitrary shell is not safe on the platform.
• Files (reading/converting local binaries) are partially mapped by operation.

Note

When a node has no equivalent, you can ask Floo (Floogos’ AI) to help you rebuild that part of the flow.