This guide shows you how to migrate real cron jobs to n8n with exact workflow configurations and code where needed.<\/p>\n\n\n\n
What n8n Gives You That Cron Does Not<\/h2>\n\n\n\n
Cron runs a command at a scheduled time. That is all it does. n8n does the same thing and adds:<\/p>\n\n\n\n
Execution logs<\/strong> – every run is recorded with start time, end time, status, and full input\/output data. You can see exactly what happened and when.<\/p>\n\n\n\n Error alerts<\/strong> – when a workflow fails, n8n sends you an email or Slack message immediately. Cron just moves on silently.<\/p>\n\n\n\n Retry logic<\/strong> – you can configure n8n to retry failed steps automatically before marking the run as failed.<\/p>\n\n\n\n No SSH required<\/strong> – you change schedules and logic from a browser. No editing crontab files on the server.<\/p>\n\n\n\n Conditional logic<\/strong> – you can run different actions based on what the scheduled task returns. Cron cannot do this without chaining shell scripts.<\/p>\n\n\n\n External triggers<\/strong> – you can combine a schedule with a webhook, so the same workflow runs on a timer and on demand.<\/p>\n\n\n\n In n8n, the Schedule Trigger node replaces the cron timing expression. It supports three modes:<\/p>\n\n\n\n Interval<\/strong> – runs every X minutes, hours, or days. Use this for simple recurring tasks.<\/p>\n\n\n\n Cron expression<\/strong> – accepts standard cron syntax for precise timing control. Use this when you are migrating existing cron jobs directly.<\/p>\n\n\n\n Specific time<\/strong> – runs once at a set date and time. Use this for one-off scheduled actions.<\/p>\n\n\n\n The cron expression format in n8n is identical to standard Unix cron:<\/p>\n\n\n\n Common cron expressions and their n8n equivalents:<\/p>\n\n\n\n Paste any of these directly into the Cron Expression field of the Schedule Trigger node.<\/p>\n\n\n\n Old cron job:<\/strong><\/p>\n\n\n\n This runs a MySQL dump every night at 2 AM and saves it to a local file. No confirmation, no alert if it fails, no way to know if the backup file is actually valid.<\/p>\n\n\n\n n8n equivalent:<\/strong><\/p>\n\n\n\n Build a workflow with four nodes:<\/p>\n\n\n\n Schedule Trigger \u2192 Execute Command \u2192 IF \u2192 Send Email<\/p>\n\n\n\n Configure the Schedule Trigger with cron expression Add an Execute Command node with this command:<\/p>\n\n\n\n Add an IF node that checks whether the output contains “success”. Connect the true branch to a Send Email node that confirms the backup. Connect the false branch to a different Send Email node that alerts you to the failure.<\/p>\n\n\n\n You now have a daily backup with success confirmation and failure alerting something the original cron job never had.<\/p>\n\n\n\n Old cron job:<\/strong><\/p>\n\n\n\n This runs a Python script every hour, appends output to a log file, and redirects errors to the same file. Reading that log later requires SSH and grep.<\/p>\n\n\n\n n8n equivalent:<\/strong><\/p>\n\n\n\n Build a workflow with these nodes: Replace the Python script with an HTTP Request node pointed at your API endpoint. Set the method, add authentication headers, and configure the response format. n8n handles the request without any script file.<\/p>\n\n\n\n If you need to transform the response data before storing it, add a Code node:<\/p>\n\n\n\n Connect the output to a Google Sheets node, a database node, or an HTTP Request node that posts to your storage API. The execution history in n8n stores every run with the full API response no log files, no SSH.<\/p>\n\n\n\n Old cron job:<\/strong><\/p>\n\n\n\n This runs every Monday at 8 AM, generates a report, and emails it. If the script fails, the email never sends and nobody knows.<\/p>\n\n\n\n n8n equivalent:<\/strong><\/p>\n\n\n\n Build this workflow: Add a Code node to format the data into an HTML email body:<\/p>\n\n\n\n Connect to a Send Email node. Configure the subject and HTML body from the Code node output using expressions: Every Monday at 8 AM, the report runs, formats, and sends automatically. If anything fails, n8n logs the error and you can add an error workflow to alert you.<\/p>\n\n\n\n Old cron job:<\/strong><\/p>\n\n\n\n This deletes files older than 7 days from a temp folder every night at 3 AM.<\/p>\n\n\n\n n8n equivalent:<\/strong><\/p>\n\n\n\n Schedule Trigger \u2192 Execute Command \u2192 IF \u2192 Send Email Use an IF node to check the output and send an alert if it fails. You can also extend this to log the number of deleted files:<\/p>\n\n\n\n This gives you a count of deleted files in each execution log useful for spotting unusual spikes.<\/p>\n\n\n\n Old cron job:<\/strong><\/p>\n\n\n\n This checks your app every 5 minutes and emails if it’s down. It works, but the email formatting is basic and there is no escalation logic.<\/p>\n\n\n\n n8n equivalent:<\/strong><\/p>\n\n\n\n Schedule Trigger \u2192 HTTP Request \u2192 IF \u2192 Send Email Connect the true branch (not 200) to a Send Email or Slack node. Add the response body and timestamp to the message so you get context immediately:<\/p>\n\n\n\n You can extend this by adding a second IF that checks how long the app has been down and sends a Slack escalation after 3 consecutive failures something impossible to do cleanly with a cron job.<\/p>\n\n\n\n Let\u2019s take a real-world cron job and convert it into an n8n workflow so you understand exactly how migration works.<\/p>\n\n\n\n Send a daily report email at 9 AM.<\/p>\n\n\n\n Add Node: Schedule Trigger This replaces:<\/p>\n\n\n\n Add Node: HTTP RequestUnderstanding the Schedule Trigger Node<\/h2>\n\n\n\n
* * * * *\n\u2502 \u2502 \u2502 \u2502 \u2502\n\u2502 \u2502 \u2502 \u2502 \u2514\u2500\u2500 Day of week (0\u20137, 0 and 7 = Sunday)\n\u2502 \u2502 \u2502 \u2514\u2500\u2500\u2500\u2500 Month (1\u201312)\n\u2502 \u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500 Day of month (1\u201331)\n\u2502 \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 Hour (0\u201323)\n\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 Minute (0\u201359)<\/code><\/pre>\n\n\n\nEvery 5 minutes: *\/5 * * * *\nEvery day at midnight: 0 0 * * *\nEvery Monday at 9 AM: 0 9 * * 1\nEvery hour: 0 * * * *\nFirst day of month: 0 0 1 * *\nEvery weekday at 8 AM: 0 8 * * 1-5<\/code><\/pre>\n\n\n\n![\"cron](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/04\/cron-jobs-1024x576.webp\")
<\/figure>\n\n\n\nMigration 1 – Daily Database Backup<\/h2>\n\n\n\n
0 2 * * * \/usr\/bin\/mysqldump -u root -pPASSWORD mydb > \/backups\/mydb_$(date +%Y%m%d).sql<\/code><\/pre>\n\n\n\n0 2 * * *<\/code>.<\/p>\n\n\n\nmysqldump -u root -pPASSWORD mydb > \/backups\/mydb_$(date +%Y%m%d).sql && echo \"success\" || echo \"failed\"<\/code><\/pre>\n\n\n\nMigration 2 – Hourly API Data Pull<\/h2>\n\n\n\n
0 * * * * \/usr\/bin\/python3 \/scripts\/fetch_data.py >> \/logs\/fetch.log 2>&1<\/code><\/pre>\n\n\n\n
Schedule Trigger \u2192 HTTP Request \u2192 Code \u2192 Google Sheets (or database)
Configure the Schedule Trigger with 0 * * * *<\/code>.<\/p>\n\n\n\nconst items = $input.all();\nreturn items.map(item => ({\n json: {\n id: item.json.id,\n name: item.json.name,\n timestamp: new Date().toISOString(),\n value: item.json.metrics?.total || 0\n }\n}));<\/code><\/pre>\n\n\n\nMigration 3 – Weekly Report Email<\/h2>\n\n\n\n
0 8 * * 1 \/usr\/bin\/python3 \/scripts\/weekly_report.py<\/code><\/pre>\n\n\n\n
Schedule Trigger \u2192 HTTP Request (or database query) \u2192 Code \u2192 Send Email
Configure the Schedule Trigger with 0 8 * * 1<\/code>.
Pull your report data with an HTTP Request node or a Postgres\/MySQL node using a query like:<\/p>\n\n\n\nSELECT category, COUNT(*) as total, SUM(amount) as revenue\nFROM orders\nWHERE created_at >= NOW() - INTERVAL '7 days'\nGROUP BY category\nORDER BY revenue DESC;<\/code><\/pre>\n\n\n\nconst rows = $input.all();\nlet table = '<table border=\"1\" cellpadding=\"6\"><tr><th>Category<\/th><th>Orders<\/th><th>Revenue<\/th><\/tr>';\n\nrows.forEach(row => {\n table += `<tr>\n <td>${row.json.category}<\/td>\n <td>${row.json.total}<\/td>\n <td>$${parseFloat(row.json.revenue).toFixed(2)}<\/td>\n <\/tr>`;\n});\n\ntable += '<\/table>';\n\nreturn [{\n json: {\n subject: `Weekly Report \u2014 ${new Date().toDateString()}`,\n html: `<h2>Weekly Sales Summary<\/h2>${table}`\n }\n}];<\/code><\/pre>\n\n\n\n{{ $json.subject }}<\/code> and {{ $json.html }}<\/code>.<\/p>\n\n\n\nMigration 4 – File Cleanup Task<\/h2>\n\n\n\n
0 3 * * * find \/tmp\/uploads -mtime +7 -delete<\/code><\/pre>\n\n\n\n
Set cron expression to 0 3 * * *<\/code>.
Configure the Execute Command node:<\/p>\n\n\n\nfind \/tmp\/uploads -mtime +7 -delete && echo \"Cleanup done: $(date)\" || echo \"Cleanup failed: $(date)\"<\/code><\/pre>\n\n\n\ncount=$(find \/tmp\/uploads -mtime +7 | wc -l) && find \/tmp\/uploads -mtime +7 -delete && echo \"Deleted $count files\"<\/code><\/pre>\n\n\n\nMigration 5 – Health Check Ping<\/h2>\n\n\n\n
*\/5 * * * * curl -s https:\/\/yourapp.com\/health | grep -q \"ok\" || echo \"DOWN\" | mail -s \"App Down\" admin@yourdomain.com<\/code><\/pre>\n\n\n\n
Set cron expression to *\/5 * * * *<\/code>.
Configure the HTTP Request node to GET your health endpoint. Set the response to include the status code.
In the IF node, check the HTTP status code:<\/p>\n\n\n\nValue 1: {{ $json.statusCode }}\nOperation: not equal\nValue 2: 200<\/code><\/pre>\n\n\n\nSubject: App Health Check Failed\nBody: Status: {{ $json.statusCode }}\n Time: {{ $now }}\n Response: {{ $json.body }}<\/code><\/pre>\n\n\n\n![\"cron](\"https:\/\/www.ucartz.com\/blog\/wp-content\/uploads\/2026\/04\/cron-mivgration-1024x576.webp\")
<\/figure>\n\n\n\nExample: Cron Script \u2192 n8n Workflow (Step-by-Step Migration)<\/strong><\/h2>\n\n\n\n
Use Case<\/h3>\n\n\n\n
Cron Job<\/h3>\n\n\n\n
0 9 * * * \/usr\/bin\/python3 \/home\/user\/send_report.py<\/pre>\n\n\n\n
Python Script (Simplified)<\/h3>\n\n\n\n
import requests
import smtplib# Fetch data
data = requests.get(\"https:\/\/api.example.com\/report\").json()# Prepare email
message = f\"Daily Report:\\n{data}\"# Send email
server = smtplib.SMTP(\"smtp.gmail.com\", 587)
server.starttls()
server.login(\"you@gmail.com\", \"password\")
server.sendmail(\"you@gmail.com\", \"team@example.com\", message)
server.quit()<\/pre>\n\n\n\nProblems with This Setup<\/strong><\/h3>\n\n\n\n
\n
Step 1: Replace Cron with n8n Schedule Trigger<\/strong><\/h3>\n\n\n\n
Configure:<\/p>\n\n\n\n\n
0 9 * * *<\/pre>\n\n\n\n
Step 2: Replace API Call (Python \u2192 HTTP Node)<\/strong><\/h3>\n\n\n\n
Configure:<\/p>\n\n\n\n