BackendBench
Coffee

Home › Convert › Apache Airflow to node-cron

Apache Airflow → node-cron

Convert Apache Airflow cron to node-cron

Apache Airflow expressions look similar to node-cron, but the differences matter. Paste yours below; the result is checked against the original run times.

Result

    What changes from Apache Airflow to node-cron

    Worked examples

    ScheduleApache Airflownode-cron
    every minute* * * * ** * * * *
    every 5 minutes*/5 * * * **/5 * * * *
    every 10 minutes*/10 * * * **/10 * * * *
    every 15 minutes*/15 * * * **/15 * * * *
    every 30 minutes*/30 * * * **/30 * * * *
    every hour0 * * * *0 * * * *
    every 2 hours0 */2 * * *0 */2 * * *
    every 3 hours0 */3 * * *0 */3 * * *

    Field layout and time zones

    Apache Airflow

    minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    Airflow defaults to UTC. On a time-zone-aware DAG a cron schedule follows wall-clock time, so a daily 00:00 US/Eastern run moves between 04:00 and 05:00 UTC across daylight saving changes.

    node-cron

    second (0-59), minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).

    node-cron uses the server time zone unless you pass { timezone: "Asia/Kolkata" }. Its documentation advises timezone: "UTC" for jobs that must not skip or repeat when clocks change.

    Go the other way

    Convert node-cron to Apache Airflow, or open the Apache Airflow builder or the node-cron builder.

    Frequently asked questions

    How do I convert a Apache Airflow cron expression to node-cron?

    Paste it into the converter above with Apache Airflow as the source and node-cron as the target. For example, * * * * * becomes * * * * *.

    Is every Apache Airflow expression convertible to node-cron?

    Yes for the common schedules we tested (30 of 30), though unusual expressions with special characters might need manual review.

    Does node-cron run in the same time zone as Apache Airflow?

    Not necessarily. Conversion changes the syntax, not the time zone. Check where each system evaluates the schedule before you rely on the same clock times.

    More tools you might need