Send an Android SMS for new Jotform submissions
Other popular Jotform workflows and automations
-
1
-
-
Notify via Notifications when Copper finds a Jotform submitter
-
-
Add new Mailchimp subscriber from Jotform submission
19
-
-
Create ClickUp tasks for new submissions in Jotform
3
-
-
Post new Jotform submissions to Blogger automatically
2
-
-
Create Squarespace contact when a new submission is added to Jotform
-
-
Save MailerLite subscriber snapshot to Google Drive
-
-
Upload Jotform submissions as TikTok video drafts
1
-
-
Add new Jotform submissions to Airtable automatically
21
-
Automate Jotform and Webhooks from your AI assistant
Ask ChatGPT to create Jotform applets and check submission history, all from your AI assistant with IFTTT MCP.
Set up IFTTT MCP
Create your own Jotform and Webhooks 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.
8 triggers, queries, and actions
New submission
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 on a new form submission.
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 submissions
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 new form submissions.
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).
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.
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.
History of submissions
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 new form submissions.
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).
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 submission
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 on a new form submission.
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).
Build an automation in seconds!
If
Select a trigger the automation will use
New submission
Receive a web request
Receive a web request with a JSON payload
Then
Select an action the automation will perform
Make a web request
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Jotform automation
Find an Applet using Jotform and Webhooks
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
Jotform and Webhooks tips, tools, and resources
More on Jotform and Webhooks
About Jotform
Jotform and IFTTT let you automatically respond to form submissions and send the data where it needs to go.
About Webhooks
Webhooks and IFTTT let you connect any custom device or app to over 750 services by sending and receiving web requests.