- \n
- You need a Node.js website on a web or cloud hosting plan that supports Node.js. Check the Node.js website limits in parameters and limits of hosting plans in Hostinger<\/a>.<\/li>\n
- Redeploy your Node.js website<\/a> first if it hasn’t been redeployed since August 2026. Older deployments use a different folder structure, so the paths in this article won’t match.<\/li>\n
- Test your script before scheduling it.<\/li>\n<\/ul>
Set up a Node.js cron job<\/h2>
Step 1 – Open Cron Jobs<\/h3>
Open the dashboard of your Node.js website and go to Advanced<\/b> → Cron Jobs<\/b>. The Node.js command is pre-filled in the command field. For general cron job settings, see how to set up a cron job at Hostinger<\/a>.<\/p>
Step 2 – Enter the Node.js command<\/h3>
A Node.js cron job command has three parts:<\/p>
- \n
- Node.js path<\/b>:
\/opt\/alt\/alt-nodejs20\/root\/bin\/node<\/code>. Replace20<\/code> with the Node.js version of your website:18<\/code>,20<\/code>,22<\/code> or24<\/code>. See how to select the Node.js version for your application<\/a>.<\/li>\n- Environment variables (optional)<\/b>:
--env-file=\/home\/u123456789\/domains\/domain.tld\/hbuilds\/config\/.env<\/code>. Add this only if your script uses environment variables.<\/li>\n- Script path<\/b>: the full path to your script inside the deployed website, for example
\/home\/u123456789\/domains\/domain.tld\/hbuilds\/current\/nodejs\/scripts\/job.js<\/code>.<\/li>\n<\/ul>A complete command looks like this:<\/p>
\/opt\/alt\/alt-nodejs20\/root\/bin\/node --env-file=\/home\/u123456789\/domains\/domain.tld\/hbuilds\/config\/.env \/home\/u123456789\/domains\/domain.tld\/hbuilds\/current\/nodejs\/scripts\/job.js<\/code><\/pre>Replace
u123456789<\/code> with your username anddomain.tld<\/code> with your domain.<\/p>Step 3 – Set the schedule and save<\/h3>
Choose a common schedule or set one manually, then click Save<\/b>. The cron job runs on the schedule you set, based on Coordinated Universal Time (UTC).<\/p>
![\"\"](\"https:\/\/www.hostinger.com\/support\/wp-content\/uploads\/sites\/55\/2026\/10\/2026-10-21_09-53.png\")
<\/p>Load environment variables in a Node.js cron job<\/h2>
A Node.js cron job doesn’t receive your website’s environment variables<\/a> automatically. Add
--env-file=\/home\/u123456789\/domains\/domain.tld\/hbuilds\/config\/.env<\/code> to the command to load them. The--env-file<\/code> option requires Node.js 20.6 or newer, so it doesn’t work on Node.js 18.<\/p>Node.js cron job limits<\/h2>
Node.js cron jobs at Hostinger follow four rules:<\/p>
- \n
- Each cron job runs one command.<\/li>\n
- The command must be 255 characters or shorter.<\/li>\n
- The command can’t contain the
%<\/code> character, because cron treats it as a line break.<\/li>\n- A cron job is stopped after 30 minutes.<\/li>\n<\/ul>
Cron jobs suit tasks that start, finish and exit, for example a nightly cleanup. They don’t replace always-running background workers such as queue workers or bots, which aren’t supported, as listed in Hostinger Node.js hosting limits for web and cloud plans<\/a>. For the number of cron jobs per plan, see how many cron jobs you can set up in Hostinger<\/a>.<\/p>
Run a Node.js cron job through a website URL<\/h2>
Call a protected route of your Node.js app with
curl<\/code> if you’d rather keep the task inside your app. Protect the route with a secret key so only the cron job can trigger it:<\/p>curl -s https:\/\/domain.tld\/api\/cron?key=your-secret-key<\/code><\/pre>This option uses your app’s existing environment variables, so the
--env-file<\/code> option isn’t needed.<\/p>Check the output of a Node.js cron job<\/h2>
Node.js cron jobs log their output the same way as other cron jobs. Follow how to check the output of a cron job at Hostinger<\/a> to view the results. If a cron job doesn’t run, see troubleshooting cron jobs at Hostinger<\/a>.<\/p>
Your Node.js cron job now runs on schedule. If it doesn’t run as expected, check the cron job output first, then confirm the Node.js version and script path in the command.<\/p>\n","protected":false},"excerpt":{"rendered":"
Schedule Node.js scripts on Hostinger web and cloud hosting using the Cron Jobs tool.<\/p>\n","protected":false},"author":594,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"include_on_kodee":true,"footnotes":""},"categories":[229],"tags":[],"class_list":["post-21119","post","type-post","status-publish","format-standard","hentry","category-cron-jobs"],"hreflangs":[],"include_on_kodee":true,"_links":{"self":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/users\/594"}],"replies":[{"embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/comments?post=21119"}],"version-history":[{"count":3,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21119\/revisions"}],"predecessor-version":[{"id":21157,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/posts\/21119\/revisions\/21157"}],"wp:attachment":[{"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/media?parent=21119"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/categories?post=21119"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.hostinger.com\/support\/wp-json\/wp\/v2\/tags?post=21119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- A cron job is stopped after 30 minutes.<\/li>\n<\/ul>
- Environment variables (optional)<\/b>:
- Redeploy your Node.js website<\/a> first if it hasn’t been redeployed since August 2026. Older deployments use a different folder structure, so the paths in this article won’t match.<\/li>\n