Skip to main content

About Automation Receipts

Automation Receipts turns workflow runs into readable receipts. Send one HTTP request from a workflow, script, scheduled job, or internal tool and keep a clear record of what happened.

Request access Read the quickstart

A receipt layer beside the tools you already use

Automation Receipts does not replace n8n, Make, Zapier, cron, custom scripts, or internal tools. It gives those tools a simple place to send a useful record after work is done.

Simple input

A workflow sends a JSON payload with a run name, summaries, status, and optional timeline events.

Readable output

The app turns that payload into a page people can scan later, without opening raw execution logs.

Flexible review

Review can be recorded in Automation Receipts, another tool, or not be needed at all.

What a receipt records

Keep the details that help someone understand what ran, what was produced, and what happened next.

Run details

Automation name, source type, run ID, trigger, status, and risk level.

Summaries

Input summary, output summary, model used, tools used, and final action.

Timeline

Events such as trigger received, model called, output generated, and action taken.

Review record

Optional approval status, reviewer name, notes, and recorded outcome.

How it works

The integration is intentionally lightweight: one request creates the first receipt, and later requests can append events when the workflow continues.
  • Workflow runs
    A workflow, script, or scheduled job does the work it already does.
  • HTTP request is sent
    The workflow posts a JSON summary to Automation Receipts with a bearer API key.
  • Receipt is created
    Automation Receipts stores a readable run page with summaries, status, and timeline events.
  • Review can be recorded
    If useful, someone records an approval, rejection, needs-changes note, or reviewed outcome.

Support Reply Drafter

Receipt example
Review pending
Source
n8n
Trigger
Support email received
Output
Draft reply prepared
Final action
Draft created, not sent
Timeline
  • Input summarized
    The incoming request was reduced to a safe summary.
  • Draft prepared
    The workflow generated a reply for review.
  • Review requested
    A person can record the outcome here or elsewhere.

Use cases

Useful wherever a workflow produces something worth checking later.

Workflow runs

Record what an n8n, Make, or Zapier flow did without digging through raw logs.

Scheduled jobs

Keep summaries from cron jobs, command-line scripts, and background tasks.

AI-assisted steps

Track generated drafts, summaries, classifications, and review outcomes.

Internal tools

Give people a readable place to check what ran and which action followed.

Create your first receipt with one request.

Start with safe example data, create an API key after your account is active, and send a controlled receipt before connecting real customer data.

Request access Read the quickstart Browse recipes Read the disclosure