What is Automation Receipts?
Automation Receipts is a readable receipt/log layer for automations, including AI-assisted workflows. Your workflow sends one HTTP request, and the app turns the important details into a receipt people can read later.
FAQ
Practical answers for early testers.
A short guide for n8n users, solo builders, small teams, and automation consultants who want readable records for AI-assisted workflows.
Is Automation Receipts an approval system?
Not primarily. Automation Receipts can record approval status and review notes, but its main job is to make a clear receipt of what happened in an automation.
Does approval have to happen inside Automation Receipts?
No. Approval can be recorded in Automation Receipts, but approval may happen in n8n, Slack, email, another tool, or may not be required for a workflow at all.
Does Automation Receipts replace n8n, Make, Zapier, or my automation platform?
No. Automation Receipts does not replace n8n, Make, Zapier, cron jobs, or custom scripts. It sits beside them as a receipt layer.
What does a receipt record?
A receipt can record the automation name, source platform, trigger, input summary, output summary, model or tools used, status, risk level, approval status, final action, and timeline events.
Do I need to send full customer data?
No. Send summaries by default. Avoid storing full customer messages, private documents, secrets, API keys, or raw model payloads unless you have a clear reason.
Can I use sample data first?
Yes. Start with sample data before connecting real customer data. It is the safest way to confirm your workflow can create a receipt.
What platforms does it work with?
Any platform or script that can send an HTTP POST with JSON can create a receipt. n8n is the first practical guide, but the app is service-agnostic.
How does n8n connect to Automation Receipts?
Use an HTTP Request node in n8n. Send a JSON body to the Automation Receipts run endpoint with an Authorization header containing your Automation Receipts API key.
What is run_uid and why does it need to be unique?
run_uid is your workflow's unique ID for one automation run. Automation Receipts uses it to prevent duplicate receipts in the same workspace, so use a dynamic value like an execution ID or timestamp.
Can I use this with custom scripts or cron jobs?
Yes. PHP scripts, PowerShell scripts, Python jobs, cron jobs, and internal tools can send receipts as long as they can make an authenticated JSON request.
Is pricing active yet?
No. Pricing is not active yet. Automation Receipts is in early testing with n8n and automation users.
Is this enterprise AI governance or observability?
No. Automation Receipts is intentionally smaller than that. It is for readable receipts of AI-assisted automations, not a workflow builder, monitoring suite, or enterprise governance platform.
Who is this for?
It is for solo builders, small teams, n8n users, and automation consultants who want a practical record of what their AI workflows did.
How do I request access?
Use the request access form and mention the workflow you want to connect. After access is approved, create an API key in Automation Receipts and keep it out of screenshots, chat, docs, and public places.