Got it, let's clear this up—cron-job.org works by sending an HTTP request to a URL you specify on your chosen schedule. So your Node.js task doesn't run directly on their platform; instead, you need to host a simple HTTP endpoint that triggers your task whenever cron-job.org hits that URL.

Here's a step-by-step breakdown with code examples:

1. Build a Simple Express Endpoint #

First, create a basic Node.js server using Express (you can use other frameworks too, but Express is straightforward). This endpoint will listen for GET requests and run your task when triggered.

const express = require('express');
const app = express();
const port = process.env.PORT || 3000;

// This is the URL cron-job.org will call
app.get('/execute-scheduled-task', async (req, res) => {
  try {
    console.log('Scheduled task initiated...');
    
    // Replace this with your actual Node.js task logic
    await runMyCustomTask();
    
    console.log('Task completed without errors');
    res.status(200).send('Task executed successfully 🎉');
  } catch (err) {
    console.error('Task failed:', err);
    res.status(500).send(`Task failed: ${err.message}`);
  }
});

// Example task function—replace with your own work
async function runMyCustomTask() {
  // Example: Fetch data from an API, update a database, send emails, etc.
  return new Promise((resolve) => {
    setTimeout(() => {
      console.log('Custom task finished processing');
      resolve();
    }, 1500);
  });
}

app.listen(port, () => {
  console.log(`Server live on port ${port}`);
});

2. Deploy the Endpoint to a Public Host #

You need to host this server somewhere public so cron-job.org can reach it. Popular options include:

• Vercel (great for Node.js apps, easy deployment)
• Railway
• Heroku
• Any other platform that hosts Node.js HTTP services

Once deployed, you'll get a public URL like https://your-deployed-app.vercel.app/execute-scheduled-task—this is the URL you'll give to cron-job.org.

3. Configure cron-job.org #

1. Log into your cron-job.org account
2. Create a new task
3. Paste your deployed endpoint URL into the "URL" field
4. Set your desired schedule (e.g., every hour, daily at 3 AM)
5. Optional: Add custom HTTP headers (like an auth secret) to prevent unauthorized requests (see tip below)
6. Save the task—cron-job.org will now hit your URL on schedule, triggering your Node.js task.

Pro Tips #

• Secure Your Endpoint: Add an authentication check to prevent random people from triggering your task. For example, set a secret header in cron-job.org and validate it in your endpoint:

  app.get('/execute-scheduled-task', async (req, res) => {
    // Validate the secret header
    const cronSecret = req.headers['x-cron-secret'];
    if (cronSecret !== process.env.CRON_SECRET) {
      return res.status(403).send('Unauthorized');
    }
    // Rest of your task logic...
  });
  

  Store the secret in your deployment platform's environment variables (never hardcode it!).

• Handle Long-Running Tasks: If your task takes more than a few seconds to run, consider using a task queue (like BullMQ) instead of running it directly in the endpoint. The endpoint can just trigger the task and return a response immediately, while the queue processes it in the background.

• Log Everything: Add detailed logs to your task so you can debug failures later—most deployment platforms let you view server logs easily.

内容的提问来源于stack exchange，提问作者Asher Dale