Platform guide

Create a receipt from Make

Use the Make HTTP app to send a JSON receipt payload from a scenario.

HTTP app

Add an HTTP Make a request module

Place the HTTP module near the end of a scenario, after Make has the trigger details, generated output, review state, or final action you want recorded.

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 Make starter payload

Starter file

Download this JSON body for the HTTP module, paste it into Make, then replace the API key, run_uid, and example summaries with mapped scenario values.

Download Make starter JSON

What you need

Automation Receipts access

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

Make 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.

Scenario trigger
  ->
Workflow modules
  ->
HTTP > Make a request
  ->
Receipt appears in Automation Receipts

Request settings

Module: HTTP > Make a request
Method: POST
URL: https://automationreceipts.com/api/v1/runs
Body content type: application/json
Body input: JSON string or data structure
Authentication: Bearer token in Authorization header or an API key credential that sends the Authorization header

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": "Make Lead Follow-up",
  "run_uid": "make-REPLACE_WITH_EXECUTION_ID",
  "source_type": "make",
  "trigger_type": "new_lead",
  "status": "needs_review",
  "risk_level": "medium",
  "input_summary": "A new lead requested pricing information.",
  "output_summary": "Make prepared a follow-up task and draft response.",
  "approval_required": true,
  "approval_status": "pending",
  "final_action": "Draft held for review before sending.",
  "events": [
    {
      "event_type": "trigger_received",
      "event_label": "Lead received",
      "event_summary": "The scenario started from a new lead."
    },
    {
      "event_type": "approval_requested",
      "event_label": "Review requested",
      "event_summary": "The follow-up draft is waiting for review."
    }
  ]
}

Make `run_uid` unique

Map a Make execution ID, generated UUID, timestamp, or source record ID into run_uid. 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/make-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."
}

Make notes

Starter file scope

This download is a copy-ready request body for the Make HTTP module. It is not a full Make scenario blueprint.

Use mapped values

Hardcoded strings are fine for the first test. Replace run_uid, summaries, and final_action with mapped values before connecting a live scenario.

Keep content type explicit

Use application/json for the request body so Automation Receipts receives a JSON object.

Check the module output

Treat HTTP 201 as success. If the module returns 401, 409, 413, or 422, inspect the response body before rerunning the scenario.

Keep summaries short

Make can pass large bundles between modules, but receipts are easier to read when you send concise summaries instead of raw payloads.

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

Make lead recipe

Build a practical lead follow-up receipt from a Make scenario.

Payload fields

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

Recipe library

Browse receipt patterns for other platforms and workflows.

Make HTTP docs

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