Readable receipts for workflows that do real work
Add one HTTP request to your workflow and get a readable receipt of what happened, what was produced, whether it was reviewed, and what happened next.
Support Reply Drafter
A support message asks whether a duplicate charge can be reviewed.
A reply draft is prepared and held for review.
Draft created, not sent.
Timeline
{
"status": "needs_review",
"approval_status": "pending",
"final_action": "Draft created, not sent."
}Built for people wiring together real workflows with
One HTTP request
Send a JSON payload from n8n, Make, IFTTT, StackAI, Zapier, a script, a cron job, or an internal tool and create a receipt page.
Timeline of what happened
Record status, events, summaries, review state, and final action in a format people can read later.
Review when needed
Approval is optional. Use Automation Receipts as a review record, not as a forced workflow gate.
Send the result back
When useful, a saved review can send a small result callback back to the workflow that created the receipt.
A focused receipt layer beside your workflow tools
Support Reply Drafter
What a receipt is
A receipt is a human-readable page for one workflow run: what triggered it, what it produced, what needs review, and what happened next.
What a run records
A run can include status, source type, input and output summaries, timeline events, model or tool notes, review status, and final action.
Why summaries matter
Store useful summaries instead of dumping private payloads into every receipt. Keep the trail readable and easier to review.
Start with safe example data before connecting real customer data.
Create an API key, send a controlled run, add an event, and open the receipt page. You do not need to create an automation first; Automation Receipts can create one from the automation name in your first API run.
Fits where the workflow already runs
Events build the timeline
Append events as the workflow progresses, or send an events array when the run is created. The timeline stays readable.
Review can happen anywhere
Record approval status in the receipt, even when the actual review happens in Slack, email, n8n, or another tool. If a callback URL is provided, the saved review result can be sent back to the originating workflow.
Export the record
Use Markdown export when a receipt needs to travel into a ticket, docs page, handoff note, or client update.
Common workflow receipts
Examples of common business workflows that can be tracked.
1
HTTP request
2
core API endpoints
1
readable receipt trail
0
workflow-builder lock-in
Request access
Request access, create an API key, and send your first receipt from n8n, Make, IFTTT, StackAI, Zapier, a script, cron job, or internal tool.
The full FAQ covers setup, access, payloads, privacy, and practical workflow use.