Migration Guide
Migrate from n8n Cron Workflows
No server to maintain. Proper failure alerting. AI diagnostics.
Step by step
Export your n8n workflows
In n8n, go to each workflow → Export → Download as JSON. Or use the n8n API: GET /api/v1/workflows.
curl -H "X-N8N-API-KEY: YOUR_KEY" http://your-n8n.com/api/v1/workflows
Identify schedule-triggered workflows
Filter for workflows where the trigger node is "Schedule" or "Cron". Note the cron expression and the HTTP endpoint the workflow calls.
Extract HTTP endpoints
For each schedule workflow that calls an HTTP endpoint (via HTTP Request node), note the URL, method, and headers.
Import to JustRun
Create JustRun jobs for each extracted endpoint + schedule. Use the JSON importer for bulk creation.
[
{
"name": "n8n: Sync contacts",
"url": "https://myapp.com/api/sync",
"cron_expression": "0 * * * *",
"method": "POST"
}
]Deactivate n8n workflows
Once JustRun jobs are verified, deactivate the corresponding n8n workflows. Keep n8n for complex multi-node workflows.
Common questions
What about n8n workflows with multiple steps?
If the workflow only calls an HTTP endpoint, move it to JustRun. If it has multiple integration steps (Slack + database + email), keep it in n8n and call the n8n webhook URL from JustRun instead.
Can JustRun trigger n8n workflows?
Yes — change the n8n trigger from "Schedule" to "Webhook". Create a JustRun job that calls the webhook URL on your schedule. This gives you JustRun's alerting and retry policies while keeping n8n's workflow logic.