Node JS is event-driven and non-blocking, but monitoring those background processes can be tricky if the process fails silently. You don’t need a complex APM tool just to check if a scheduled task ran.

olic.io simplifies this with a “healthcheck” approach. We listen for a simple HTTP GET request. If your Node script hits our endpoint, we know your job is done. If we don’t hear from you, we alert you.

Adding a Heartbeat to Your Node Script

Modern Node environments (v18+) support the native fetch API, meaning you don’t even need external dependencies like axios or node-fetch.

Implementation

// Your unique olic.io URL
const HEARTBEAT_URL = "https://api.olic.io/ping/YOUR-ID-HERE";

async function runJob() {
  try {
    console.log("Starting scheduled task...");

    // --- YOUR CORE LOGIC HERE ---
    // await databaseCleanup();
    // ----------------------------

    // Send the success ping
    const response = await fetch(HEARTBEAT_URL);
    
    if (response.ok) {
        console.log("Ping sent to olic.io");
    } else {
        console.error("Failed to ping olic.io");
    }

  } catch (error) {
    console.error("Job failed:", error);
    process.exit(1);
  }
}

runJob();

This method is entirely async/await compatible, keeping your code clean. This simplicity is key when you are managing Teams of developers who need to read and understand scripts quickly.

Why Node JS for Backend Automation

Node JS allows developers to use a single language for both frontend and backend, which is a massive advantage for small SaaS teams. It is heavily used for I/O intensive tasks, such as Importing data or triggering webhooks.

Because Node is often used to orchestrate microservices, a single failure can cascade. Monitoring your Node cron jobs ensures that your scheduled maintenance or data sync tasks are actually completing, keeping your application state healthy.

Learn more about Node JS here.