Resources · Make integration

IFTTT Make integrationAutomate IFTTT with Make.

Your IFTTT applets can hand their data to a longer workflow. The IFTTT Make integration gives you 2 modules: one instant trigger that receives data from an applet, and one action that sends data to an applet. This page shows how to connect the account and build a first scenario.

Try the IFTTT integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the IFTTT Make integration do for you?

The IFTTT Make integration is a two-way bridge between your applets and a Make scenario, the automation you build in Make as a chain of modules. IFTTT can push data into Make the moment an applet runs, and Make can send data back to an applet, which can then run it.

Extend an applet past its single step. Start a scenario with Receive data, and whatever the applet passes along reaches Make as a bundle, one item flowing from module to module. From there you can hand it to a spreadsheet, a CRM or any other app Make connects, like the Airtable Make integration.

Let another tool trigger an applet. A sales team logs a new deal in its CRM; the scenario catches that event and uses Send data to pass the details to an IFTTT applet, which takes care of the rest on the IFTTT side.

Keep a single hub for both worlds. Applets stay where they already work, and Make handles the steps that need filters or several apps in a row. Each module run counts as one operation, the unit Make counts on your plan.

Know the limits before you start: the Make documentation lists no quota or size limit for these two modules, and there is no Make an API Call module for IFTTT, so anything beyond receiving and sending applet data sits outside this integration. For the bigger picture on the tool itself, read the Make review, or weigh the options in n8n vs Make.

Connect

How do you connect IFTTT to Make?

  1. 01

    Add an IFTTT module

    In your scenario, click the +, search for IFTTT and pick Receive data or Send data. The module asks for a connection, meaning your IFTTT account linked to Make once, then click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the account owner. Then authorize Make on the IFTTT page that opens, or paste the key IFTTT gives you if the window asks for one.

  3. 03

    Save and reuse it

    Click Save. The connection now appears in both IFTTT modules, so the next time you add Receive data or Send data to a scenario, you simply select it from the list instead of starting over.

First scenario

Your first scenario with IFTTT and Make

GoalWhen a new deal lands in the CRM your team uses, Make sends its details to an IFTTT applet.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This one belongs to the app where the event starts, for example your CRM.

  2. 02

    Set the starting module

    Search your CRM by name and pick the module that watches new deals. Click Create a connection; once your account is linked, Make lists the objects it can read, so you pick what to watch from a list instead of typing it.

  3. 03

    Add Send data

    Click the + on the right of the first module, search IFTTT and choose Send data. Select your IFTTT connection, then map the deal details the previous module brings in.

  4. 04

    Test with Run once

    Create a test deal, then click Run once. Make runs the scenario a single time and shows the bundle each module received, so you can confirm the applet got the right data.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, the shortest gap on the Free plan. Keep it or adjust it, then switch the scenario on.

Triggers

What starts an IFTTT scenario

1 module starts a scenario when something happens in IFTTT. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by IFTTT as soon as it happens.

IFTTT1Receive data

Receive data

Instant trigger

In Make“Receives data from an applet.”

You get the data of an IFTTT applet inside Make the moment that applet sends it, ready to feed a spreadsheet, a CRM or a chat message. It is the only way to start a scenario from IFTTT, and each run of the applet arrives as a fresh bundle.

How it fires
instant. IFTTT calls Make through a webhook as soon as the applet runs, so there is no polling interval to wait for.
When to use it
an applet already reacts to something you care about, and you want Make to carry that result through several more apps.
Watch out
nothing reaches Make until the applet actually sends data, so run the applet once while the scenario waits in Run once.
Modules

What Make can do in IFTTT

IFTTT gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

IFTTT1

Send data

Action

In Make“Sends data to an applet. It can execute a specific applet.”

This action hands data from your scenario to an IFTTT applet, and can make that specific applet run. Any event Make sees in another app can then start something on the IFTTT side.

When to use it
a form entry, a new deal or a paid invoice in another app should set off an applet you already rely on.
Watch out
each call counts as one operation on your Make plan, so add a filter before this module when only some events should reach the applet.
Need help

Need help automating IFTTT with Make?

A person reads every message.

FAQ

Questions about the IFTTT Make integration

01Is the IFTTT Make integration free?
Yes, IFTTT is a standard app in Make, so both modules work on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops any run after 5 minutes, handles files up to 5 MB and caps data transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of 40 minutes. Make counts usage in operations, one per module run. IFTTT's own plans are a separate matter and are not covered here.
02What do you need to connect IFTTT to Make?
You need an IFTTT account and a Make account. The Make documentation lists no other prerequisite for this app. Add Receive data or Send data to a scenario, click Create a connection, name it if you like, authorize Make on the IFTTT page or paste the key IFTTT provides, then click Save. That one connection is reused by both IFTTT modules, so you set it up a single time and pick it from the list afterwards in any scenario that uses IFTTT.
03Does the IFTTT trigger in Make react in real time?
Yes. Receive data is an instant trigger: IFTTT calls Make through a webhook as soon as an applet sends data, so the scenario starts right away instead of waiting for a polling interval. In the editor it carries the lightning badge rather than the clock badge of scheduled triggers. The practical catch is on the IFTTT side: the applet has to run and send its data before anything happens in Make, so test it by triggering the applet while the scenario is waiting in Run once.
04What if the IFTTT module you need is missing in Make?
It depends on what you need. The IFTTT app in Make has only two modules, Receive data and Send data, and no Make an API Call module, so there is no generic way to reach other IFTTT features from Make. If the job goes beyond sending data to an applet or receiving it, check whether the other app involved has its own Make modules and connect it directly. When the setup gets tangled, the team behind this page can look at your case through the help form below.
05Should you use Make or n8n for IFTTT?
It depends on the tool your team already works in. On Make, IFTTT comes down to two modules: an instant trigger that receives applet data and an action that sends data to an applet. Many apps also have an n8n node, so check what n8n offers for IFTTT before you choose. The deciding criteria are practical ones: which tool already hosts your other scenarios, who will maintain them, and whether those two modules cover your need. The comparison linked earlier on this page goes through both tools in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations