How to migrate old actions to the native Apilio-IFTTT integration

Getting Started & How-To's
1

Here’s a bit more detail on how to find and update those old webhooks:

How to migrate to the 2019 version an old webhook that runs an IFTTT action

Launch an action from a logiblock in apilio via webhooks
Launch an action from a logiblock in apilio via webhooks1600×900 56.6 KB

Option 1: migrate manually to the native IFTTT integration

IFTTT now allows you to edit existing applets and add/remove triggers, so you don’t have to start from scratch. You can simply update the applet to use the new integration:

  1. Go to the https://app.apilio.com/ifttt_actions and identify any very old actions. They will have “(Using IFTTT Webhooks)” in their name:

    image
    image1113×685 50.2 KB

  2. Find the Logicblock that is using this action and edit it.

  3. Delete the old webhooks IFTTT action. It will have the new IFTTT icon.

  4. Create a new IFTTT action in your Logicblock, with the same event name as the existing old one

  5. Delete the old action and save your Logicblock.

  6. Go to IFTTT and edit your existing applet that was using these old webhooks as the trigger. Add a new trigger using the Apilio service, and select the event name you just duplicated in the new action. Delete the old webhooks trigger and save your applet with the new Apilio trigger.

  7. You have completed the update and everything will continue to run in the same way.

Option 2: We migrate you automatically to an HTTP request

For those of you who don’t migrate to the IFTTT integration, we’ll move your actions to the new HTTP actions. This will keep your automations running, but mind the following differences:

  • It won’t be an explicit IFTTT action in your Logicblock
  • Actions from the Apilio channel on IFTTT (option 1) are easier to track and analyse as they appear as such in your IFTTT logs
  • There have been instances where IFTTT has updated the maker keys without notifying the users, and this has broken their applets, making them update manually each one of their affected applets. If you use the Apilio channel this won’t happen.
  • The action will be a URL with just a default description. You will need to edit the description to something that is meaningful for you.

If you haven’t migrated your actions manually by the end of May (option 1), to guarantee that your routines continue to operate we will migrate them over to an HTTP action (option 2).

Do you also have old incoming webhooks?

If you have incoming webhooks that update variables or evaluate Logicblocks, you’ll need to update these as well. Here’s the guide to to help you update the webhook configuration in external services:

:bulb: Related articles

2 Likes