IFTTT Integration Tester
Verify end-to-end automation chains — key stays in your browser, event names are remembered.
How to use this tool
IFTTT Integration Tester — enter your Maker event and key, craft value1–value3 JSON, and fire the webhook straight from your browser with live status, latency and history. Free, private, 100% browser-based.
formula
POST maker.ifttt.com/trigger/{event}/with/key/{key} + JSON {value1..3} (browser-direct)How do I test? +
Enter the event name, Maker key and JSON, then Send. Status, body and latency appear instantly.
How do I test my IFTTT webhook? +
With this tool: enter the Maker event name, your key from ifttt.com/maker_webhooks and a JSON payload with value1–value3, then Send. You get the HTTP status, response body and latency instantly, plus a request history.
What if the response cannot be read (CORS)? +
Some networks block reading the reply. Your applet may still have fired — use “Send blind” (no-cors fire-and-forget) and check the applet activity page, or copy the equivalent cURL command and run it in a terminal.
Is my Maker key safe? +
Yes. Requests go directly from your browser to maker.ifttt.com; the key is never sent to or stored on 0Appz servers. Only the event name (never the key) is remembered locally, and the history log stores statuses without keys.