How a configurator can connect with Make

AutomationAssessed per project

Make, formerly Integromat, is an automation platform that started in Prague. Scenarios are assembled visually from modules, can branch, and can be started by a received webhook.

What a configuration could hand over

When an enquiry should go somewhere different depending on what the customer chose, branching helps. The configurator can call a webhook on submission, and a Make scenario can then pass a pergola to one salesperson and a fence to another, or write the enquiry to a spreadsheet and the CRM at once. The field structure is agreed during implementation.

  • Custom webhook

    On submission the configurator could call the URL of a Custom webhook module, and the scenario would start at once, as with an instant trigger.

  • Data structure

    From a sample configuration we post during setup, Make determines the data structure, so dimensions, material or price can be mapped in later modules.

  • Router and filters

    A router can split enquiries by product or price band, with a filter on each route and a fallback route for everything else.

  • Webhook response

    The Webhook response module can return a custom reply to the configurator, such as the CRM record number, if you want to use it further.

What we need to connect it

  1. The scenario would run in your own Make organisation; we supply the data structure and sample configurations for testing.

  2. We would keep the webhook URL as a secret on the configurator’s server, because anyone who knows it can start the scenario.

  3. Credits for the scenario’s operations come out of your Make plan, so we estimate together how many modules one enquiry uses.

  4. Field names are agreed in advance, and if they ever change we warn you before the scenario breaks.

Worth deciding up front

  • Make processes at most 300 incoming webhook requests per 10 seconds, and a webhook queue is capped by plan at no more than 10,000 items; once the queue is full, further requests are rejected.
  • Make deactivates a webhook that has not been attached to any scenario for more than 5 days, which matters when a scenario is being rebuilt.
  • Router routes run one after another, not in parallel, so their order decides what happens first.

Questions about this connection

Who maintains the Make scenario after go-live?

The scenario sits in your account, so your own staff or agency can change it without touching the configurator. On our side the data structure would stay stable, and we would warn you ahead of any change to it.

In that case Make returns an error status code and does not process the request. How the configurator should react, for example by retrying or by an email alert, is designed during implementation.

Other integrations

Put Make to work in your sales.

Tell us what you sell and how an enquiry is handled today. On the demo you will see the configurator, and we will go through which data could flow from it into your system.

treede is not an official partner or reseller of the systems named here. All names and marks belong to their owners. Integration options are verified during implementation against the system interface and version. Make official site