Background
When you connect the Webhooks service to your IFTTT account, a unique Webhooks key is automatically generated for you. This key acts like a personal identifier that allows external services or devices to securely trigger your Applets that use Webhooks as the Trigger.
Your Webhooks key is what links incoming web requests to your IFTTT account. For example, you might use it to have a device, script, or third-party service send a request to IFTTT to turn on your lights, post a message, or log data in a spreadsheet.
It’s important to note that your Webhooks key is only used with Webhooks Triggers, not with Actions. Since your key uniquely identifies your account, you should keep it private and avoid sharing it publicly. Anyone who has access to your key could trigger your Applets without permission.
Finding your Webhooks key
Go to the Webhooks service page.
If you haven’t connected it yet, select Connect Webhooks.
Once connected, return to the Webhooks service page and scroll down to the About Webhooks section at the bottom.
Click Documentation. You can also go directly to the Webhooks Documentation page.
Your unique Webhooks key will be displayed at the top of that page
Using your key in a Webhooks URL
If your Applet uses the Receive a web request trigger, your Webhooks URL should be formatted as:
https://maker.ifttt.com/trigger/{event}/with/key/{webhooks_key}
If your Applet uses the Receive a web request with a JSON payload trigger, your Webhooks URL should be formatted as:
https://maker.ifttt.com/trigger/{event}/json/with/key/{webhooks_key}
(Note the /json/ after the event name.)
In the above URLs:
{event} should be replaced with the event name configured in the Event Name field of your Applet's Trigger
{webhooks_key} should be replaced with your Webhooks Key
Finding the Webhooks URL for a specific Applet
You can also find your Applet’s exact Webhooks URL by:
Opening the Applet.
Scrolling to the Your Webhook URL field.
Copying the URL directly from that field.
For additional details on how to pass values to Webhooks in your Webhooks Triggers you can view our FAQ here.