In an Applet, the action is the work that IFTTT initiates as a result of an updated trigger.
Actions are organized under services. Some example actions are “Create post” or “Post a new tweet”. Services do not need to have all triggers, queries, and actions. Some services will have only one or any combination of the three.
When a user sets up an Applet, they populate the action’s “action fields” with data, usually including ingredients provided by the trigger. Think of action fields as a form field. For example, when using the “Create post” action, the two action fields are for the “Title” and “Post Body”. When using the “Post a new tweet” action, the only action field is the text of the message.
Almost every action has at least one action field.
We bring services together into Applets. An Applet connects two or more apps or devices together. It enables you to do something that those apps or devices couldn’t do on their own.
Some example Applets include, Sync Amazon Alexa to-dos with your Google Calendar or Create events in your iPhone Calendar, via Google Assistant. IFTTT users can turn on Applets that have been created by services or other users, or they can create their own. Here’s a short video tutorial that shows you how to connect your apps and devices, and turn on Applets.
The Applet ID is an ID that specifies an Applet on IFTTT. For example, this Applet's ID is
Applet version ID
An Applet version ID specifies a user's version of an Applet. It will look like
78911786 and is available on an Applet page when the user views it.
See Applet templates in the API reference documentation.
When a user sets up an Applet, IFTTT starts monitoring the endpoint specified by the trigger service. Every time IFTTT finds that the data has been updated, IFTTT will execute the Applet, pushing the data from the trigger over to the action(s). This is an “Applet Run”.
To get an Applet to run as close to the triggering event as possible, triggers should use the Realtime API.
The URI at the service's domain where IFTTT will request updates (for triggers) or POST data (for actions).
A key that identifies your service. Interchangeable with
Each trigger contains ingredients – individual pieces of data.
Some example ingredients from the “New tweet by you” trigger from the Twitter service:
- Text – The tweet itself.
- UserName – User name of tweeter.
- LinkToTweet – The URL to the tweet itself.
- CreatedAt – Date and time tweet was created.
- TweetEmbedCode – The HTML embed code for the Tweet.
A user will take the individual ingredients provided by a trigger or a query and will use them to fill in an action’s action fields.
In an Applet, the query is a way to request additional data if the trigger doesn't provide it. IFTTT initiates a Query execution as a result of an updated trigger.
Queries are organized under services. Some example queries are “List busy windows” or “Search events”. Services do not need to have all triggers, queries, and actions. Some services will have only one or any combination of the three.
When a user sets up an Applet, they populate the query’s “query fields” with data, usually including ingredients provided by the trigger. Think of query fields as a form field. For example, when using the “Search events” query, the two query fields are for the “Calendar id” and “Query”. When using the “List busy windows” query, the only query field is the id of the calendar.
Almost every query has at least one query field.
IFTTT’s Realtime API lets Applets using your triggers to run near-instantly. Utilizing the Realtime API is required for services with triggers.
Services are the basic building blocks of IFTTT. Some example services are Facebook, Twitter, Nest, Fitbit, Amazon Alexa and Gmail. Your product will be represented on IFTTT as a service.
In the context of the IFTTT platform, a slug is the immutable ID of a service, trigger, trigger field, ingredient, action, or action field.
In an Applet, the trigger is the data that, when changed, prompts an Applet to run on IFTTT. Some example triggers include, Breaking news for sport or New results from search.
Triggers are organized under services. Each service provides an endpoint for each trigger, which is checked after the service POSTs to the Realtime API (recommended) alerting IFTTT that there is fresh trigger data. If the Realtime API is not used, the trigger is checked periodically for new data.
Services do not need have to have all triggers, queries, _and* actions. Some services will have only one or any combination of the three.
When a user builds or turns on an Applet, they can specify certain parameters that IFTTT will pass to the service's endpoint when it makes the request for new data.
Think of trigger fields as a “filter” for the data requested from a trigger. For example, on the ESPN service, the “Breaking news for sport” has the trigger field “Sport”. When the user sets up an Applet with that trigger, she can select which sport she’s interested in. Or for the Craigslist “New results from search” trigger, the user can specify the URL of the specific search they want.