Send email and create PagerDuty incident when Webhook event occurs
3 ready-made Webhooks and PagerDuty Applets
Turn one on, or build your own. Webhooks can start an automation with "Receive a web request", and IFTTT can then run "Create a new incident" on PagerDuty.-
-
-
Create a PagerDuty incident when a Webhook event is received
-
-
Create a PagerDuty incident when a Webhook event is received
-
Automate Webhooks and PagerDuty from your AI assistant
Ask ChatGPT to create webhook applets that connect your projects to IFTTT's 750+ services, right from your AI assistant with IFTTT MCP.
Set up IFTTT MCP
Create your own Webhooks and PagerDuty workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
11 triggers, queries, and actions
New incident assigned to me
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Fires when a new incident gets assigned to the current user.
New oncall shift starts for me
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Fires when a new oncall shift starts for the current user.
Receive a web request
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Receive a web request with a JSON payload
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
List incidents
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
Returns a list of incidents.
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
Create a new incident
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will create a new incident in PagerDuty.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Update incident status
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will update the status of an incident.
Create a new incident
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will create a new incident in PagerDuty.
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
List incidents
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
Returns a list of incidents.
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
New incident assigned to me
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Fires when a new incident gets assigned to the current user.
New oncall shift starts for me
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
Fires when a new oncall shift starts for the current user.
Receive a web request
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Receive a web request with a JSON payload
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Update incident status
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will update the status of an incident.
Build an automation in seconds!
If
Select a trigger the automation will use
New incident assigned to me
New oncall shift starts for me
Receive a web request
Receive a web request with a JSON payload
Then
Select an action the automation will perform
Create a new incident
Make a web request
Update incident status
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Webhooks automation
Find an Applet using Webhooks and PagerDuty
Find an automation to connect to, or create your own!Connect IFTTT to your accounts
Securely connect the Applet services to your respective accounts.Finalize and customize your Applet
Review trigger and action settings, and click connect. Simple as that!Upgrade your automations with
-
Connect to more Applets
Connect up to 20 automations with Pro, and unlimited automations with Pro+ -
Add multiple actions with exclusive services
Add real-time data and multiple actions for smarter automations -
Get access to faster speeds
Get faster updates and more actions with higher rate limits and quicker checks
Webhooks and PagerDuty tips, tools, and resources
More on Webhooks and PagerDuty
About Webhooks
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 1000+ apps and services on IFTTT.
About PagerDuty
PagerDuty's Platform for Real-Time Operations integrates machine data & human intelligence to improve visibility & agility across organizations. PagerDuty gives you real-time visibility into your critical apps and services all in one place, driven by the full-service ownership model.
Check our support section if you experience any problems with this integration.