Frequently Asked Questions
1. Basics
Automation Receipts is a receipt layer for workflows, scripts, AI-assisted automations, and internal tools.
Your workflow sends a JSON payload, and the app turns the important details into a page people can read later.
Not primarily. Automation Receipts can record approval status and review notes, but its main job is to keep a clear record of what happened.
Approval can happen in Automation Receipts, n8n, Slack, email, another tool, or not be required for the workflow at all.
No. Automation Receipts is more focused than that.
It is for readable receipts of automation work, not a workflow builder, monitoring suite, or governance platform.
2. Workflows and platforms
Any platform or script that can send an authenticated HTTP POST with JSON can create a receipt.
Current platform guides cover n8n, Make, IFTTT, StackAI, Zapier, and custom scripts. Automation Receipts stays service-agnostic, so cron jobs and internal tools can use the same API.
Use an HTTP Request node in n8n.
Send a JSON body to https://automationreceipts.com/api/v1/runs with an Authorization: Bearer ... header containing your Automation Receipts API key.
The n8n guide includes request settings, example payloads, dynamic run_uid guidance, and an optional callback pattern.
Use the Make HTTP app with a Make a request module.
Set the method to POST, send JSON to https://automationreceipts.com/api/v1/runs, and add Authorization: Bearer ... plus Content-Type: application/json headers.
The Make guide includes a downloadable starter JSON body and notes on mapping dynamic values into run_uid.
Use the IFTTT Webhooks service with a Make a web request action.
Set the method to POST, content type to application/json, add the bearer API key in Additional headers, and send the receipt JSON body to the Automation Receipts run endpoint.
The IFTTT guide shows a compact payload that works well with Applet ingredients.
Use an action or custom API-style step after the StackAI agent or workflow has produced the information you want to record.
POST a JSON receipt payload to https://automationreceipts.com/api/v1/runs with the bearer API key in the request headers.
The StackAI guide is written for agent output, workflow summaries, and optional review records.
Use Webhooks by Zapier with a POST or Custom Request action.
Send the JSON body to the Automation Receipts run endpoint and include both Authorization: Bearer ... and Content-Type: application/json headers.
The Zapier guide includes request settings, a starter JSON file, and duplicate run_uid troubleshooting.
No. AI-assisted automations are a strong use case, but ordinary webhooks, scheduled jobs, scripts, and internal tools can use the same receipt format.
The product should work for useful workflows whether or not a model is involved.
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.
The receipt format is meant to be practical rather than tied to one workflow platform.
3. Receipts and review
A receipt can record the automation name, source platform, trigger, input summary, output summary, status, risk level, approval status, final action, and timeline events.
The goal is to preserve the details that help someone understand what ran, what was produced, and what happened next.
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 such as an execution ID or timestamp.
No. Approval can be recorded in Automation Receipts, but it may happen in n8n, Slack, email, another tool, or not be required at all.
When review is useful, the receipt can keep the status and notes beside the rest of the run record.
4. Data and accounts
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.
Yes. Start with safe example data before connecting real customer data.
It is the safest way to confirm your workflow can create a receipt.
Paid plan enforcement is not active in the app yet.
Approved accounts can use the available receipt features while pricing, limits, and plan details are finalized.
Request access and mention the workflow you want to connect.
After your account is active, create an API key in Automation Receipts and keep it out of screenshots, chat, docs, and public places. The quickstart walks through the first receipt request.