IFTTT webhooks: Receive a web request URL, Make a web request and your key

The IFTTT Webhooks service gives you a trigger URL, https://maker.ifttt.com/trigger/{event}/with/key/{key}, for receiving requests, and a Make a web request action for sending them. This page covers your IFTTT webhook key and URL format, passing value1 to value3 versus a JSON payload, and checking what your device or Applet actually sends with a free bin. It also goes over the 12-second timeout and plan limits.

Trigger URLs and your Webhooks key

Connect the IFTTT Webhooks service to generate your account's key, then open the Webhooks documentation page at ifttt.com/maker_webhooks/documentation to see it. If you already have an Applet that uses a Webhooks trigger, it also shows Your webhook URL at the bottom of its page.

In the URL, {event} has to match the trigger's Event Name and the key is what authorizes the request, so treat it like a password. If your key leaks, or as IFTTT's first troubleshooting step when a trigger stops working, regenerate it at https://ifttt.com/maker_webhooks/settings and update your URLs with the new one. Sending a request with a wrong key returns HTTP 401 with {"errors":[{"message":"You sent an invalid key."}]} (checked on 2026-10-29).

# Fire a Receive a web request Applet with three values
curl -X POST \
  "https://maker.ifttt.com/trigger/<event>/with/key/<key>" \
  -H "Content-Type: application/json" \
  -d '{"value1":"21.5","value2":"kitchen","value3":"ok"}'

Check what your device or script sends

When an Applet doesn't fire, find out what your sender is actually sending before you blame IFTTT.

1. Create a free bin in your browser at view.webhooks.page or by running curl -X POST https://webhooks.sh/v1/bins.
2. Temporarily replace the maker.ifttt.com URL in your device or script with the bin's ingest URL, keeping the same path if you like, such as https://<bin>.webhooks.page/trigger/<event>.
3. Fire the request and check the bin in your browser for the HTTP method, the Content-Type header (the JSON payload trigger needs Content-Type: application/json), field names spelled value1, value2 and value3, and valid JSON in the body.

The bin replies with its own HTTP 200, so this only tests the sending side; switch your device or script back to the IFTTT URL once the request looks right.

Make a web request: see what IFTTT sends

The IFTTT Make a web request action only reaches publicly accessible URLs, so it can't call a server on localhost, but it can call a webhooks.sh bin. Point the action's URL field at https://<bin>.webhooks.page/ifttt and run the Applet, and the bin will show the method, Content-Type, any extra headers from Additional Headers, and the raw body after IFTTT fills in the ingredients, which is the quickest way to spot broken JSON.

Ingredients dropped into the Body field can break JSON syntax, for example when they contain quotes or line breaks. Fix that by wrapping the ingredient in <<< and >>>, like <<<{{Username}}>>>, or wrap the whole body in <<< and >>> to keep its formatting.

Two limits apply. Any header whose name contains authorization, cookie, key, token or secret shows as redacted in the viewer and the API, so you won't see its value there. Also, a bin always replies with a fixed HTTP 200 and a small JSON body like {"ok":true,"delivery_id":"..."}, which can't be customized, so it can't stand in for an API that the Make a web request with JSON response query reads from.

Timeouts, limits and plans

IFTTT gives an outbound Webhooks action 12 seconds to finish before the Applet fails with Timed out waiting for response from .... Your receiving server should answer the request right away and do any slow work after. IFTTT also doesn't use a fixed IP address or range for Webhooks, so IP allowlists won't work on your firewall.

On plans, the IFTTT plans page says all core features are on every plan and names Webhooks among the services available on every plan, including Free at $0 with 1,000 credits a month. The Make a web request action page and the JSON payload trigger page still show a Pro badge, though, so check what your own account's editor shows.

Keep the test URL

A free bin lasts 48 hours and takes up to 100 requests a day with bodies up to 100KB, which is plenty for debugging an Applet. If you want to keep the same .webhooks.page URL past 48 hours, claim the bin from the bin page with a free Google sign-in before it expires, and it will keep new requests on a rolling 30-day basis at the same 100 requests a day limit.

If you need more, Solo is $12 a month and gives you named, persistent endpoints on webhooks.host, 250,000 requests per billing period, 90 days of history, and forwarding to up to 3 verified HTTPS URLs, plus the wsh CLI to relay live requests to localhost. See pricing for the full breakdown.

FAQ

How do I find my IFTTT webhook URL and key?

Connect the Webhooks service in IFTTT, then open ifttt.com/maker_webhooks/documentation to see your key. Your trigger URL is https://maker.ifttt.com/trigger/{event}/with/key/{key}, and any Applet using a Webhooks trigger also shows Your webhook URL at the bottom of its page.

Is IFTTT Webhooks free?

IFTTT's plans page lists Webhooks as available on every plan, including the $0 Free plan with 1,000 credits a month. However, the Make a web request action page and the JSON payload trigger page still display a Pro badge, so check what the editor shows on your account.

How do I send more than three values to IFTTT?

Use the Receive a web request with a JSON payload trigger at https://maker.ifttt.com/trigger/{event}/json/with/key/{webhooks_key} with the header Content-Type: application/json. The entire request body becomes the JSON Payload ingredient, which you can parse using filter code.

Why does my IFTTT webhook return 401?

The key in your trigger URL is wrong. In a check on 2026-10-29, sending an invalid key to a trigger URL returned HTTP 401 with {"errors":[{"message":"You sent an invalid key."}]}. Copy your key again from the documentation page, or regenerate it at https://ifttt.com/maker_webhooks/settings.

Why does IFTTT say Timed out waiting for response?

Your server didn't respond within 12 seconds, which is the timeout for IFTTT Webhooks actions. Have your server return an HTTP response immediately and run any slow tasks in the background.

Does IFTTT use fixed IP addresses for webhooks?

No. IFTTT doesn't set a fixed IP address or IP range for the Webhooks service, so you can't allowlist IFTTT by IP.