n8n Import
Import existing n8n workflows into AgentLed. Preview the import to see how nodes map to AgentLed steps, then convert and enhance with AI capabilities.
What Gets Imported
The importer converts supported n8n node types to equivalent AgentLed steps. Unsupported nodes are flagged with remediation hints so you know exactly what to fix manually.
| n8n node | AgentLed equivalent |
|---|---|
| Manual Trigger | Manual workflow trigger |
| Schedule Trigger | Scheduled trigger (cron) |
| Webhook | Webhook trigger |
| HTTP Request | HTTP Request step (custom action) |
| Code / Function | Code step (JavaScript, sandboxed VM) |
| Set / Wait | Data transformation / delay step |
| Respond to Webhook | Webhook response step |
| If / Switch | Requires manual setup as entry conditions |
| Merge / SplitInBatches | Requires manual setup as batch steps or loops |
Import Process
Step 1In n8n, open the workflow and export it as JSON (⋯ → Download).
Step 2Preview — Run preview_n8n_import (or dashboard Import → Preview) to see the mapping confidence score, unsupported nodes, and any warnings. No workflow is created yet.
Step 3Import — Run import_n8n_workflow (or click Import in the dashboard). A draft workflow is created.
Step 4Review & fix — Work through the post-import checklist below before publishing.
Via MCP
// 1. Preview (dry-run, no workflow created)
preview_n8n_import({ workflowJson: "<paste n8n JSON>" })
// Returns: { confidence: 0.85, warnings: [...], unsupportedNodes: [...] }
// 2. Import (creates a draft workflow)
import_n8n_workflow({ workflowJson: "<paste n8n JSON>", name: "My Workflow" })
// Returns: { workflowId: "wf_...", draftId: "..." }Max payload: 2.5 MB. A confidence score of 1.0 means all nodes mapped successfully; below 1.0 means some nodes require manual remediation.
Post-Import Checklist
1. Re-connect credentials
n8n credentials are not imported. Open each app action step and connect your AgentLed integration (OAuth or API key) via the step configuration panel.
2. Update variable syntax
n8n uses {{$json.field}}. AgentLed uses {{steps.stepId.field}}. The importer converts known patterns, but check Code steps for raw n8n variable references.
3. Convert AI logic to AI steps
If n8n Code steps contain LLM API calls, consider converting them to AgentLed AI steps with proper prompt templates and structured response schemas.
4. Wire up branches manually
If / Switch nodes become entry conditions on downstream steps. Add entryConditions with the equivalent criteria and onCriteriaFail: skip to replicate branching.
5. Test with sample input
Run the draft with a small sample before publishing. Check execution logs step-by-step for failures or unexpected outputs.
Next Steps
- Custom Actions — HTTP Request steps imported from n8n
- Loops & Conditionals — Replace n8n If / Switch nodes with entry conditions
- AI Steps — Upgrade Code nodes that call LLM APIs