Recipe
IFTTT Alert Receipt
Create a readable receipt when an IFTTT Applet sends an alert, updates a log, or completes a simple action.
Record simple Applet actions
Use this recipe when an Applet should leave a record that a trigger fired, an alert was sent, and the action finished.
When to use this recipe
Home or office alerts
Record alerts from connected devices, forms, calendars, or status services.
Simple notification trails
Keep a readable trail when an Applet sends an email, mobile notification, or chat message.
Low-risk automation logs
Use a completed receipt when no review is needed and the Applet only records or notifies.
Later follow-up
Append an event if a person later checks, resolves, or escalates the alert.
Workflow shape
Applet triggered
A connected service starts the IFTTT Applet.
Optional fields prepared
Ingredients or filter logic provide the summary values.
Action completed
The Applet sends a notification or performs the simple action.
Receipt created
The Webhooks action posts JSON to Automation Receipts.
Follow-up recorded
A later API call can append the resolution event.
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
Headers
Authorization: Bearer aar_live_REPLACE_MEExample run payload
Send this payload to POST https://automationreceipts.com/api/v1/runs. Replace example values with mapped values from IFTTT when the workflow is ready.
Create IFTTT alert receipt
{
"automation_name": "IFTTT Alert Receipt",
"run_uid": "ifttt-alert-REPLACE_WITH_TRIGGER_VALUE",
"source_type": "ifttt",
"trigger_type": "applet_triggered",
"status": "completed",
"risk_level": "low",
"input_summary": "An IFTTT Applet received an alert trigger from a connected service.",
"output_summary": "The Applet sent a notification and logged this 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": "Alert sent",
"event_summary": "The Applet sent the configured notification."
}
]
}Make run_uid unique
Use a trigger ingredient plus a timestamp, or another value that changes each time the Applet runs. Automation Receipts rejects duplicate run_uid values within the same workspace.
Events this recipe uses
| Event type | Label | What it records |
|---|---|---|
trigger_received |
Applet triggered | IFTTT received the configured trigger. |
action_taken |
Alert sent | The Applet completed its notification or action. |
note |
Follow-up note | A later check, resolution, or escalation was recorded. |
Append the final action
If the workflow continues after the receipt is created, append a timeline event using the original run_uid.
Append event request
curl -X POST "https://automationreceipts.com/api/v1/runs/ifttt-alert-REPLACE_WITH_TRIGGER_VALUE/events" \
-H "Authorization: Bearer aar_live_REPLACE_ME" \
-H "Content-Type: application/json" \
-d '{
"event_type": "note",
"event_label": "Alert checked",
"event_summary": "A person checked the alert and no further action was needed."
}'IFTTT notes
Use Additional headers
Put the Authorization bearer token in the Additional headers field and choose application/json as the content type.
Keep the body compact
IFTTT Applets are easier to maintain when the JSON body stays short and uses only useful ingredients.
Avoid secrets in ingredients
Do not pass account tokens, private URLs, or sensitive connected-account data into the receipt body.
Review is usually not needed
Most alert receipts can use approval_required false unless a person must explicitly review the action.
Review and data notes
| Workflow state | Suggested fields |
|---|---|
| Routine alert | status: "completed", approval_required: false, approval_status: "not_required" |
| Alert needs human check | status: "needs_review", approval_required: true, approval_status: "pending" |
| Resolved later | Append a note or action_taken event with the resolution summary. |
Send concise summaries by default. Avoid raw messages, documents, secrets, API keys, and full model payloads unless the receipt reader truly needs that information.
Troubleshooting
| Problem | What it usually means | Fix |
|---|---|---|
| 401 unauthorized | The bearer token is missing, wrong, or revoked. | Use the full active API key in the Authorization header. |
| 409 duplicate run_uid | A receipt already exists with that run ID in the workspace. | Map a dynamic value into run_uid 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. |
| Missing Content-Type | IFTTT did not send the body as JSON. | Choose application/json in the Webhooks action content type field. |
| Repeated duplicate responses | The Applet sends the same run_uid for every trigger. | Include a timestamp or changing trigger ingredient in run_uid. |