Your n8n flow.
One CSV checkpoint.

Start with one small report.

Use a synthetic or sanitized UTF-8 CSV within 1 MiB, 100 columns and 10,000 data rows. Decide which headers, row range and dates should pass. You can explore those rules in the free browser checker before connecting anything.

Production submission needs an existing, unpaused Report Watch monitor in an eligible workspace, its report ID and its submission token. A person sets up the workspace with ChatGPT sign-in. Public workspaces require confirmed live payment to run monitors; importing this file does not create access or buy a subscription.

Connect it in six deliberate steps.

1. Import and keep it unpublished.

   Download the workflow JSON and import it into your own n8n instance. Inspect its nodes before running it. Keep the workflow unpublished and use its Manual Trigger; this recipe has no schedule or incoming webhook.

   Self-hosted operators can use n8n import:workflow --input=workflow.json, then execute the imported ID. Use a separate test instance when evaluating the download. Follow the official Server CLI instructions; an import can overwrite a matching existing ID.

2. Save the intended submission.

   In Saved submission envelope, replace the placeholder values with the existing monitor’s monitorId, a stable submissionId, its intended deadlineMs and the exact csv text. The unchanged placeholders intentionally fail validation before a request can run. Keep the values together in a durable, protected envelope before sending. The workflow does not add a durable queue for you.

   The deadline is exactly 13 digits of Unix milliseconds for a real occurrence under that monitor’s daily or weekly schedule. Use its timezone and daylight-saving rules. Do not use the current time, append the grace period or move a late report into the next period. Replace all fictional values with your own authorized configuration.

3. Add a protected report credential.

   In n8n, create an HTTP Header Auth credential. Set the header name to Authorization and its value to Bearer <report-token>, with one space after Bearer. Select this credential in the HTTP Request node.

   Use only the token scoped to this monitor. Keep it out of the envelope, exported workflow, ordinary node fields, prompts and source control. This integration never needs your ChatGPT session, Stripe key, OpenAI key or owner maintenance credential. n8n’s credential documentation explains Header Auth.

4. Confirm the request destination and body.

   The production target is POST https://reportwatch.mayd-it.com/api/ingest/<monitorId>. Keep the origin fixed. Send Idempotency-Key from the saved submission ID and X-Report-Deadline from the saved deadline.

   The body must be the raw CSV text with Content-Type: text/csv; charset=utf-8. Keep redirects disabled, certificate checks enabled and pagination off. Do not add an Origin header, a file URL, JSON wrapper or multipart upload. A loopback mock used in testing is a separate destination; never give it a real report token.

5. Run the manual test once.

   Start at Start manually and execute the workflow using a small synthetic report. Submit CSV once makes one attempt. Keep Response Format set to Autodetect and Include Response Headers and Status enabled. The next step inspects the parsed response and its HTTP status. No automatic retry or report-generation step runs after a failure.

   Confirm the received CSV bytes, ID and deadline match your saved envelope. Use the monitor’s rules to create a deliberate pass and a deliberate failure. A production submission writes saved check evidence and can queue report notifications, so use only a monitor and recipient you are authorized to test.

6. Inspect the classified receipt.

   Read the check receipt checks the HTTP status, JSON content type, expected receipt fields and matching deadline. Only a valid check receipt can be classified as passed or failed. An HTTP 200 alone is insufficient.

   The final node, Inspect outcome before continuing, exposes passed, quality_failed or review in the outcome field. It performs no downstream action. Add your own reviewed routing only after verifying the connection.

Three outcomes, three next steps.

duplicate: true returns the original saved result, which can be passed or failed. The original check time and late status still apply. A new receipt does not prove that the report reached a client.

Keep one attempt’s identity.

After an uncertain request, retain the same monitor ID, submission ID, deadline and exact CSV bytes. A timeout does not establish whether the server saved the first attempt. Reload the envelope after a restart; do not regenerate it inside a retry loop.

Do not change the ID to bypass a 409 conflict. Schedule changes, a paused report, token replacement or loss of access can invalidate a previously eligible retry. The production workflow must manage its own durable envelope storage, bounded retries and review process.

Verify the connection you will use.

Your own acceptance checklist

• Confirm a synthetic pass and a deliberate missing-column or row-count failure.
• Retry the exact envelope and confirm the original check ID and timestamp return.
• Confirm that reusing its ID with changed content is rejected; then test a correction with a new ID and the original deadline.
• Confirm redirects, unexpected HTML, invalid JSON and a mismatched deadline go to review.
• Check credential, access and quota failures without automatic retries or new IDs.
• In your authorized production monitor, verify saved evidence and the intended alert recipient. A queued email is not proof of delivery.

Check both sides’ data handling.

Report Watch processes submitted CSV rows in memory and retains normalized headers, rules, fingerprints and check evidence. Your n8n instance has its own handling of execution inputs, outputs and errors. Those records can include CSV data and header values; this recipe does not promise that n8n saves nothing.

Review execution-history settings, access permissions, credential storage, debug output and retention before using real data. CLI execution can print complete workflow execution data even when history saving is disabled. Keep acceptance inputs synthetic and review exports before sharing them. See n8n execution settings and the Report Watch privacy details.

A pass does not verify business accuracy, source completeness or client delivery. Background checks and email take time. Keep other required checks and avoid relying on this service as the sole control for critical reporting.

Keep the contract close.

• Report Watch submission and retry reference
• Report Watch OpenAPI contract
• n8n HTTP Request node documentation
• n8n Manual Trigger documentation

This guide is published by Mayd-it LLC. n8n is a separate product; no endorsement or marketplace approval is claimed.