Skip to main content

Migrating webhooks to Make

Make uses a different webhooks architecture than Integromat. We introduced the following changes:

  • Webhooks have a different URL (referencing the make.com domain and the geographical region of the data center, e.g. hook.us1.make.com).

  • One webhook can no longer be used in multiple scenarios. Make requires you to use a separate webhook for each scenario.

First, follow the documentation at Upgrading to Make. Use the following additional instructions for specific webhook use cases.

Use the following strategies to upgrade webhooks that are used in only one scenario:

  • Duplicate webhooks during migration and turn off the original ones.

  • Duplicate webhooks and forward data to them from Integromat. Note: This is a risky approach, we will stop supporting Integromat in 2023, causing the forwarding to stop working. To avoid this, Convert Integromat webhooks to Make webhooks.

Webhook collision

Make requires you to use a separate webhook for each scenario. Use the following tips to migrate scenarios that shared a single webhook on Integromat.

If you use one webhook to trigger multiple scenarios, the Migration tool shows a warning and does not allow migrating those scenarios until you resolve the webhook collision.

webhook_migration_collision.png

Use the following strategy to upgrade webhooks that are used in multiple scenarios (referred to as colliding webhooks).

Solve webhook collision using a router

Use this approach when it's not convenient to update all your 3rd party systems to use unique webhooks. This procedure details how to create a single new webhook and distribute its data to new unique webhooks. This way, you will not have to update your 3rd party systems to each use a unique webhook, but rather update all systems to use one new webhook. You will then use the new webhook to distribute data to the individual colliding scenarios.

  1. On Integromat, open one of the colliding scenarios.

  2. Open the webhook module's settings and click Add under Webhook.

    • This is the new and unique webhook that you will use after you migrate the scenarios to Make.

  3. Configure the new webhook in the same way as the original webhook, which triggered the scenario. Set it as the trigger for the scenario.

  4. Repeat these steps for all colliding scenarios that use the same webhook. Create a unique webhook for each one and set it as a trigger.

  5. Migrate the colliding scenarios. Choose to duplicate the webhooks without forwarding traffic.

  6. On Make, create a new scenario. Add a custom webhook as the trigger.

  7. Connect a router to the custom webhook module.

  8. Connect as many HTTP > Make a request modules as the number of colliding scenarios.

  9. Set up each of the HTTP modules to call the unique webhooks that you migrated in step 5. In the HTTP modules, pass the data coming from the trigger webhook to the newly created webhooks.

The scenario will look similar to the following screenshot:

webhook_deconflict_scenario.png

Convert forwarded webhooks to Make webhooks

Before we stop supporting Integromat, which is scheduled to happen during 2023, you need to change the systems that send data to those webhooks so that they point to Make.

These instructions apply if:

  • You migrated scenarios with webhooks to Make.

  • In the migration process, you chose to forward webhooks from Integromat to Make.

The steps to take differ based on the type of webhook:

  • Custom webhooks and manually registered app-specific webhooks

  • Automatically registered app-specific webhooks

Custom webhooks and manually registered app-specific webhooks

You created these webhooks manually in Make and registered them manually in systems, which send data to them.

Update the systems that send data to those webhooks with the webhook counterparts in Make.

  1. Log in to Integromat and open Webhooks.

  2. Identify the webhooks that forward data to Make. Type the word “forwarded” into the search box to only show those webhooks that are forwarded to Make.

  3. Copy the Make webhook URL.

  4. Update your 3rd party apps and other scenarios which call this webhook to the new Make URL.

webhooks_forwarded.png

Automatically registered app-specific webhooks

Make automatically created and registered these webhooks in the systems, which send data to them. This happens when you create a connection to an app and add the webhook from the scenario designer.

  1. Open the scenario that uses the webhook.

  2. Open the connection settings of the trigger module.

  3. Click Add next to Webhook.

  4. Set up the webhook the same way you set it up originally on Integromat.

In this section: