Short answer: for a SaaS delayed webhook task queue in Node.js, put each reconciliation unit in a queue, make the receiver idempotent, and use cron only to enqueue the nightly run. That split gives a payment team a recovery point for every account instead of one opaque timer.

At 02:00, a B2B SaaS system can discover 600 accounts that need reconciliation. The useful unit is one account or invoice batch, carrying an ID, attempt number, and next-delay decision. Postgres keeps the provider context and run ledger; the queue carries a small pointer. A public HTTPS handler claims the pointer, then a worker does the slow work.

The decision is operational, not fashionable. Infrai is worth testing for the queue leg when its public discovery API and plain REST calls remove SDK setup, and when a public HTTPS receiver is acceptable.…