Migrate from Make
Floogos imports a Make (Integromat) scenario blueprint and converts it into a native workflow: each module maps to a node, routers become branches and expressions are translated to Floogos syntax.
Step by step
Section titled “Step by step”-
Export the blueprint from Make. Open the scenario → menu (⋯) → Export Blueprint. A
.jsonfile is downloaded. -
Open the importer in Floogos. Workflows → New Workflow → Import from n8n or Make (or the Import button).
-
Load the JSON. Drop it, pick the file or paste the content. The importer detects it’s a Make blueprint automatically.
-
Review the report. You see how many modules were mapped, which need review and the coverage, just like with n8n.
-
Create the draft and open the editor. The flow opens with the summary note and the pending-actions comment.
-
Complete and activate. Adjust credentials, endpoints and expressions, test with Run and activate.
How Make concepts are translated
Section titled “How Make concepts are translated”| Make | Floogos |
|---|---|
| Module | A node (the equivalent by app/operation) |
| Router | Decision / branches |
| Route filter | Branch condition |
| Trigger (webhook, schedule, watch) | Webhook / start by type |
| Iterator / Array Aggregator | Iterator + grouping nodes |
| Data store | Native Floogos Data Store |
Mapping functions ({{...}}) | {{ data.field }} expressions |
What to review
Section titled “What to review”- Credentials (connections). Make connections are not imported: create/link the Floogos ones.
- Operations per module. Make groups many actions under a single app; verify the mapped operation is correct.
- Routers with filters. Check that each route’s conditions reflect the original filters.
- Expressions. Make functions (
formatDate,map, etc.) may need rewriting in Floogos syntax.
See also
Section titled “See also”- Migrate from n8n — the process is identical; only the source format changes.