Platform guide

Create a receipt from IFTTT

Use an IFTTT Webhooks action to create a receipt from an Applet.

Webhooks action

Add a Webhooks Make a web request action

Use this when an Applet should leave a receipt after a trigger fires or after another action prepares the summary you want to record.

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 IFTTT Webhooks body

Starter file

Download this JSON body for the Webhooks action, paste it into the Body field, then replace run_uid and summaries with Applet ingredients or safe static values.

Download IFTTT body JSON

What you need

Automation Receipts access

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

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

IFTTT trigger
  ->
Optional query/filter/action fields
  ->
Webhooks > Make a web request
  ->
Receipt appears in Automation Receipts

Request settings

Action: Webhooks > Make a web request
Method: POST
URL: https://automationreceipts.com/api/v1/runs
Content type: application/json
Additional headers: Authorization: Bearer aar_live_REPLACE_ME
Body: JSON payload

Headers

Authorization: Bearer aar_live_REPLACE_ME

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": "IFTTT Home Alert",
  "run_uid": "ifttt-REPLACE_WITH_DYNAMIC_VALUE",
  "source_type": "ifttt",
  "trigger_type": "applet_triggered",
  "status": "completed",
  "risk_level": "low",
  "input_summary": "An IFTTT Applet received a trigger from a connected service.",
  "output_summary": "The Applet sent a notification and logged a receipt.",
  "approval_required": false,
  "approval_status": "not_required",
  "final_action": "Notification sent.",
  "events": [
    {
      "event_type": "trigger_received",
      "event_label": "Applet triggered",
      "event_summary": "IFTTT started the Applet from the configured trigger."
    },
    {
      "event_type": "action_taken",
      "event_label": "Action completed",
      "event_summary": "The Applet completed its action and sent this receipt."
    }
  ]
}

Make `run_uid` unique

Use an available trigger ingredient, timestamp, or another changing value. If the Applet cannot build a unique value, add enough trigger context to avoid reusing the same 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/ifttt-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."
}

IFTTT notes

Starter file scope

This download is a copy-ready Webhooks action body. IFTTT does not use this file as an importable Applet template.

Set Content Type separately

IFTTT sets Content-Type through the Content Type field, so put Authorization in Additional headers and choose application/json for the body.

JSON payloads are best

Use a JSON body when you need more than a few values or want the receipt fields to stay explicit.

Keep the Applet simple first

Test with plain text summaries before adding filter code, multiple services, or sensitive connected-account data.

Callbacks are usually a later step

For IFTTT, start by creating receipts. Add review callbacks only when you have a reachable URL and a clear follow-up action.

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

IFTTT alert recipe

Create a receipt when an Applet sends an alert or completes an action.

Payload fields

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

Recipe library

Browse receipt patterns for other platforms and workflows.

IFTTT Webhooks FAQ

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