Using IFTTT (IF This Then That) to Extend API Alert Messaging

IFTTT (IF This Then That) is a site that enables the creation of API “Recipes for the Small Business Owner.” Activity that takes place on a particular site is monitored by IFTTT, and if a trigger event occurs, then an action can be initiated that produces a result on a different site. The IFTTT “recipes” that enact this are actually little programs that are created by IFTTT users. A user can implement an already-created recipe (tailoring it to utilize their own accounts), or new recipes can be created.

In this post, I’ll illustrate how to create a new IFTTT recipe that is triggered by a Facebook Page notification sent by Slack in response to an alert created by your API Science account (see my post API Monitoring with Slack, Zapier, and Facebook for background on how I created the automated Facebook Page notification).

Once you’ve created an IFTTT account, you’ll see a “My Recipes” link at the top of your home page. Clicking this link brings you to your “My IF Recipes” page:


Click the “Create a Recipe” button to get your integration started.

Next, you’re prompted to specify the “this” that will trigger the “that”:


Click the “this” link to identify what event will trigger the “that” action which you’ll later specify.

Now, you select the IFTTT “channel” that will provide the trigger event. In our example, an update to a Facebook Page is the trigger. Clicking the “Facebook Pages” icon brings you to:


Click the “Connect” button, and you will be navigated to your Facebook account. You’ll have to approve information IFTTT will receive in order to confirm the connection. Then, IFTTT will ask you who can view posts they will privately send to you on Facebook. Providing IFTTT with appropriate permissions brings you to a page that lets you select which of your Facebook Pages you’d like to use with IFTTT, for example:


Select your Facebook Page on the pulldown list, then click the “Update” button to connect the page with IFTTT:


Clicking the “Done” button brings up another page where you can click a “Continue to the next step” button. Click that to enter the “Choose a Trigger” step.

Several options are available as IFTTT triggers for a Facebook Page. Since we’ve previously configured our “Lyra Monitors” Facebook Page to post new messages whenever one of our monitors sends an alert, we select the “New status message on page” trigger option, which “fires every time you create a new status message on your Facebook Page.”

Clicking the “Create Trigger” on the next page brings you to the “that” part of the equation. What should happen when your defined trigger event occurs?


Clicking “that” opens a display of IFTTT channels that provide an action that responds to your defined trigger.

Perhaps your team uses Todoist for organizing items on your team’s “to do” list? Select that as your IFTTT action channel. You’ll be asked to connect to your Todoist Channel:


Agree to the terms, then click the “Done” button, and the subsequent “Connect” button, and you can then create the task that will be performed on Todoist when the Facebook Page trigger is activated.

At this point, your IFTTT entries depend on the actions that your selected response site requires. For Todoist, you select a project, task content, and (optionally) more.

Clicking through let’s you create a recipe that will react to any new Facebook Page messages by creating an entry on your team’s Todoist page (or any other app you selected as the response to your trigger).

However you decide to make your team aware of API alerts, with IFTTT you can utilize API Science’s alert capabilities to extend critical messaging to your team using virtually every mainstream communications technology.

2 thoughts on “Using IFTTT (IF This Then That) to Extend API Alert Messaging

Comments are closed.