Platform guide

Create a receipt from Zapier

Use Webhooks by Zapier to send a receipt payload from a Zap.

Webhooks by Zapier

Add a Webhooks by Zapier action

Place the webhook action after the Zap has enough fields to explain the trigger, output, review state, and final action.

Use the Automation Receipts API endpoint

Send create-run requests to https://automationreceipts.com/api/v1/runs. If your account uses a different workspace or environment endpoint, use the endpoint shown in your Automation Receipts setup.

Use the Zapier Custom Request JSON

Starter file

Download this JSON body for Webhooks by Zapier, paste it into the Custom Request Data field, then replace run_uid and summaries with Zap values.

Download Zapier JSON

What you need

Automation Receipts access

Use an active account and an active API key. The key is sent as a bearer token.

Zapier workflow

Start with a controlled workflow run and safe example values before connecting private data, customer-facing actions, or live approval steps.

Basic workflow shape

Put the receipt step after the workflow has enough information to summarize the trigger, output, review state, and final action.

Zap trigger
  ->
Zap actions or formatter steps
  ->
Webhooks by Zapier
  ->
Receipt appears in Automation Receipts

Request settings

App: Webhooks by Zapier
Event: Custom Request or POST
Method: POST
URL: https://automationreceipts.com/api/v1/runs
Payload type: JSON or raw JSON
Headers: Authorization and Content-Type

Headers

Authorization: Bearer aar_live_REPLACE_ME
Content-Type: application/json

Sample payload

Use the platform's mapped values where the example says to replace a value. Keep summaries readable and avoid sending raw secrets, full customer messages, or unnecessary private payloads.

Create-run JSON

{
  "automation_name": "Zapier Invoice Follow-up",
  "run_uid": "zapier-REPLACE_WITH_UNIQUE_RUN_ID",
  "source_type": "zapier",
  "trigger_type": "new_invoice",
  "status": "completed",
  "risk_level": "low",
  "input_summary": "A new invoice matched the follow-up conditions.",
  "output_summary": "Zapier created a follow-up task and sent this receipt.",
  "approval_required": false,
  "approval_status": "not_required",
  "final_action": "Follow-up task created.",
  "events": [
    {
      "event_type": "trigger_received",
      "event_label": "Invoice trigger received",
      "event_summary": "The Zap started from a new invoice trigger."
    },
    {
      "event_type": "action_taken",
      "event_label": "Task created",
      "event_summary": "The Zap created the follow-up task."
    }
  ]
}

Make `run_uid` unique

Use a Zap run value, source record ID plus timestamp, or another dynamic value from the trigger/action data. Automation Receipts rejects duplicate run_uid values within the same workspace.

Optional timeline events

For the first controlled run, include a short events array in the create-run payload. If the workflow continues later, append an event with the original run_uid.

Append an event later

POST https://automationreceipts.com/api/v1/runs/zapier-sample-run-001/eventsAuthorization: Bearer aar_live_REPLACE_ME
Content-Type: application/json

{
  "event_type": "action_taken",
  "event_label": "Workflow finished",
  "event_summary": "The workflow finished and the receipt was updated."
}

Zapier notes

Starter file scope

This download is a copy-ready Custom Request body. Zapier templates are shared by link inside Zapier, not imported from this JSON file.

Use Custom Request for nested JSON

The example payload includes an events array. Custom Request is usually the clearest Zapier option when you want to type exact JSON.

Fill the Data field

If a Custom Request has an empty Data field, Zapier may send fields from the previous step instead of your intended receipt payload.

Validate raw JSON

Raw JSON is sent as entered, so check quotes, commas, and mapped fields before turning on the Zap.

Check plan access

Confirm your Zapier plan supports the Webhooks by Zapier action before relying on it in a live workflow.

Troubleshooting

Problem	Likely cause	What to check
401 unauthorized	The bearer token is missing, revoked, or not the full API key.	Use the complete key value shown when it was created, prefixed with Bearer.
409 duplicate run_uid	A receipt already exists with that run ID in the workspace.	Use a dynamic value that changes for each workflow run.
422 validation error	A required field is missing or a machine value is not allowed.	Check automation_name, run_uid, summaries, source_type, status, and approval_status.

Next steps

Zapier invoice recipe

Track an invoice trigger, task creation, and follow-up outcome.

Payload fields

Check field meanings, allowed values, request limits, and event types.

Recipe library

Browse receipt patterns for other platforms and workflows.

Zapier Webhooks docs

Open the platform documentation for the HTTP, webhook, or action step used in this guide.