If a webhook is triggered, get a mobile notification
by
About this Applet
Launch a Cursor cloud agent automatically from incoming Webhooks events. When your Maker Webhooks endpoint receives a JSON web request, this Applet passes the payload to Cursor to start an agent that works on the GitHub repository you specify. This is useful for automating code tasks, CI workflows, or triaging requests by spinning up Cursor agents from Webhooks triggers.
If
Trigger ingredients
EventName
JsonPayload
OccurredAt
Then
Action fields
GitHub repository
What should the agent do?
Agent name (optional)
You might also like...
-
555
-
-
Relay a Webhooks request to another URLby
287
-
-
Add Webhooks data to Google Sheets automaticallyby
261
-
Related services
-
-
App store rating
Create your own Webhooks and Cursor 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
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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).
Get agent status
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 current status and details of a Cursor cloud agent, including its latest run status, the final result text, and the pull request URL if one was created.
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 agents
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 Cursor cloud agents belonging to the authenticated account, one record per agent, most recent first.
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.
Add a follow-up instruction to an agent
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 add a follow-up instruction to a Cursor cloud agent, starting a new run to guide it toward additional changes.
Launch an agent
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 launch a new Cursor cloud agent to work on a GitHub repository using the instructions you provide.
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.
Stop an agent
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 stop a running Cursor cloud agent by cancelling its latest run, without deleting the agent.
Add a follow-up instruction to an agent
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 add a follow-up instruction to a Cursor cloud agent, starting a new run to guide it toward additional changes.
Get agent status
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 current status and details of a Cursor cloud agent, including its latest run status, the final result text, and the pull request URL if one was created.
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).
Launch an agent
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 launch a new Cursor cloud agent to work on a GitHub repository using the instructions you provide.
List agents
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 Cursor cloud agents belonging to the authenticated account, one record per agent, most recent first.
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.
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
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).
Stop an agent
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 stop a running Cursor cloud agent by cancelling its latest run, without deleting the agent.
Build an automation in seconds!
If
Select a trigger the automation will use
Receive a web request
Receive a web request with a JSON payload
Then
Select an action the automation will perform
Add a follow-up instruction to an agent
Launch an agent
Make a web request
Stop an agent
You can add delays, queries, and more actions in the chat.
More on Webhooks and Cursor
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 Cursor
Cursor is an AI-first code editor that launches cloud agents to automate coding tasks, generate code, and manage repositories. Use IFTTT to launch Cursor agents from other services and query their status.