Skip to script setup
Report WatchBY MAYD-IT

SCRIPTS · SCHEDULED JOBS · AUTHORIZED AGENTS

Your report.
A repeatable checkpoint.

Save the finished CSV and its deadline together. Inspect the submission locally, then send it with a client that keeps retries tied to the original file.

Node.js 22+ · no packages · tested locally on Node 24. What was verified.

Start with an eligible report. A person configures its rules, schedule and token. Public monitoring requires confirmed payment. Downloading this client does not create an account, buy a plan or enable a schedule.

Connect one report first.

  1. Prepare the finished file.

    Save the downloaded client in your controlled workflow. Replace the uppercase placeholders below. Use a new protected output file for each period or correction; existing envelopes are never overwritten.

    node report-watch-client.mjs prepare --csv report.csv --monitor REPORT_ID --deadline INTENDED_DEADLINE_MS --id STABLE_SUBMISSION_ID --out submission.json

    The deadline is the intended scheduled occurrence in 13-digit Unix milliseconds, without grace. Use the report’s timezone and daylight-saving rules. It is not the current time or a value to recalculate during retries.

  2. Inspect without a request.

    node report-watch-client.mjs inspect --envelope submission.json

    This checks local encoding, fields and size. It does not verify server access, schedule eligibility or CSV quality. The free checker helps you explore rules before sending.

  3. Connect the protected token and send.

    Inject REPORT_WATCH_TOKEN through your execution platform’s secret facility. Use the token for this report; keep it out of commands, source files, envelopes and prompts.

    node report-watch-client.mjs send --envelope submission.json

    Send saves evidence and may queue alerts. The destination is fixed to Report Watch, redirects are disabled, and the printed receipt omits CSV rows, rules and credentials.

Your local envelope contains the CSV. Store it in a protected folder, with appropriate Windows permissions or POSIX access controls. Retain it for review after uncertainty; apply your own retention policy afterward.

Give your job a clear next step.

  • Exit 0 after Send: passed. Store the receipt and inspect late. Local Prepare and Inspect also exit 0, but send nothing.
  • Exit 2: quality failed. Evidence was saved. Review the check and prepare a corrected file with a new ID and the same intended deadline.
  • Exit 3: review needed. Keep the original envelope. Do not mark the report passed or generate a new ID to bypass an error.
  • Exit 1: local input error. Review file access, the command, saved fields and protected token.

A duplicate returns the original check and timestamp. A pass verifies the submitted CSV against its rules; it does not establish business accuracy or client delivery.

Keep retries boring and predictable.

Timeouts and server errors permit four attempts total, with waits of 5, 30 and 120 seconds. Each attempt has a 30-second timeout including the response body. All attempts keep the original CSV, ID and deadline.

Access errors, quota limits, redirects and malformed receipts stop for review. An external scheduler must prevent overlap and route nonzero exits to its review process. It should not restart failed jobs forever.

The client does not generate files, calculate timezone occurrences, install a scheduled task or maintain a background queue. After a restart, retry the saved envelope. A new period or corrected artifact gets a separate envelope.

Full command and retry reference →

Tested with synthetic data. Verify your connection.

Local CLI tests cover exact file preservation, overwrite refusal, timeouts, bounded retries, redirects and invalid receipts. The actual application handler and an in-memory database also verified a committed response loss, identical retry, failed CSV and correction.

These checks made no production submissions or email sends. Your own scheduled workflow, paid access and alert delivery still need verification. Begin with synthetic data and inspect the saved evidence before relying on automation.

FIND THE RIGHT START

One file, or a recurring workflow?

Check a file for free, then explore whether scheduled monitoring fits the job.

Submission contract · OpenAPI · n8n workflow