Make integration

Make (formerly Integromat) is a visual automation platform that lets you design, build, and automate workflows by connecting your favorite apps and services — without writing code. This integration lets your WeWeb backend trigger webhook-based Make scenarios with optional input data.

Use cases

• Trigger a Make scenario when something happens in your app (new order, new signup, form submission)
• Reuse existing Make automations from WeWeb without rebuilding them
• Hand off multi-app processes (CRM updates, notifications, file processing) to Make
• Send structured data from your backend into a Make scenario's webhook

Setup

1. Sign in to your Make account and note your zone — the sub-domain you are on (eu1, eu2, us1, or us2).

2. In Make, open your profile → API/MCP access and add a new API token. Scopes are the checkboxes you tick while creating the token — they decide what the token is allowed to read. Tick at least these five; each one powers a part of the integration:

   • organizations:read — Fills the Organization dropdown
   • teams:read — Fills the Team dropdown
   • scenarios:read — Fills the Scenario dropdown, and is used again on every run to look up the scenario's webhook
   • hooks:read — Reads that webhook, both to show its address and to call it when the action runs
   • udts:read — Reads the webhook's data structure, which is what pre-fills the Input Data fields

   If a scope is missing, the connection still saves, but whatever depends on that scope stops working: organizations:read, teams:read and scenarios:read each leave their own dropdown empty, and udts:read leaves Input Data with no pre-filled fields. Note that scenarios:read and hooks:read are also used every time the action runs, so a token missing either of those breaks Trigger Scenario itself with a 403 error, not just a dropdown. Scopes can't be changed on an existing token — create a new token with all five and update the connection.

3. In WeWeb, open the Data & API tab, then the Integrations subtab. Select Make, then click Add Connection.

4. Paste the API Token and select your Zone. The connection applies to all environments (Editor, Staging, Production); to use different values per environment, override the generated environment variables.

5. Test with Trigger Scenario on a simple webhook-triggered scenario — if everything is configured, Make responds (with Accepted by default) and the run appears in your Make scenario history.

How triggering works

WeWeb triggers Make scenarios through their webhook trigger:

• Only scenarios with a webhook trigger appear in the Scenario dropdown — scenarios with other trigger types are filtered out.
• Triggering queues the scenario to run. The action returns as soon as the webhook responds (Make's default response is the text Accepted) — it does not wait for the scenario to finish, unless the scenario is configured to respond only after completion with a Webhook response module (example under Trigger Scenario).
• An inactive scenario can still be triggered: the run is queued and processes once the scenario is activated.

The Input Data field is pre-filled with the webhook's learned data structure. Make webhooks learn their expected fields from sample requests — until the webhook has received at least one request, no fields appear (you can still add key/value pairs manually).

Common pitfalls (setup & usage)

Zone doesn't match the API token

The API token only works in the zone where it was created. Selecting a different zone in WeWeb makes every call fail with 403 or 404 errors. Check the sub-domain you see when logged into Make (e.g. eu2.make.com) and select that zone.

No fields in the Input Data field

Make webhooks learn their data structure from sample requests. If the webhook has never received one, no fields are pre-filled. Send a sample request to the webhook once (from Make's Redetermine data structure option or any HTTP client), then refresh — or enter the expected keys and values manually.

The action returns before the scenario finishes

The action responds as soon as the webhook accepts the request; the scenario runs asynchronously in Make. If you need the scenario's result in your workflow, end the scenario with a Webhook response module (example under Trigger Scenario).

All Actions

This integration provides one action that triggers webhook-based scenarios.

Action	Description
Trigger Scenario	Trigger a webhook-based Make scenario with optional input data

Action details

Trigger Scenario

Trigger a webhook-based Make scenario with optional input data.

Inputs

Display Key	Example Input	Description	Restrictions
Organization	"ACME Corp"	The Make organization to look in.	Required
Team	"Engineering"	The team within the organization. Only shown once an organization is selected.	Required
Scenario	"Process Customer Signup"	The webhook-triggered scenario to run. Only shown once a team is selected; only scenarios with a webhook trigger are listed.	Required
Input Data Optional	{"email":"customer@example.com"}	Data sent to the scenario webhook. Fields are populated from the webhook's learned data structure; if none appear, send a sample request to the webhook first.	Object

Example output

"Accepted"

Make's default webhook response is the text Accepted, sent as soon as the run is queued.

Returning custom data instead. In Make, add a Webhook response module (from the Webhooks app) as the last module of the scenario, with Status set to 200 and Body set to the JSON you want back — for example:

{ "status": "done", "customerId": "12345" }

The action then waits for the scenario to reach that module and returns the parsed JSON as its result — so you can bind e.g. result.customerId in the next steps of your WeWeb workflow. Because the trigger now waits for the scenario to respond, only use this with scenarios that finish quickly.

Documentation of API endpoint that powers action: Make help – Webhooks

Error handling

Error code and type	Reason
400 Bad Request	API token or zone missing on the connection.
403 Forbidden	API token invalid, missing scopes, or created in a different zone than the one selected.
404 Not Found	Resource not found — often a zone mismatch between the token and the selected zone.

The action can also fail with This scenario does not have a webhook trigger (the scenario's webhook was removed) or Could not resolve webhook URL for this scenario (Make did not return a webhook address) — check the scenario's trigger in Make.

FAQs

Why doesn't my scenario appear in the Scenario dropdown?

Only scenarios with a webhook trigger can be triggered from WeWeb, so the dropdown lists only those. Give the scenario a Custom webhook trigger in Make, then refresh the dropdown.

Why do I get "No organizations found" or empty dropdowns?

Verify your API token is valid, has the organizations:read, teams:read, scenarios:read, hooks:read and udts:read scopes, and — most commonly — that the selected zone matches the zone where the token was created. A missing scope breaks only what depends on it, so an empty Team dropdown points at teams:read. Keep in mind that scenarios:read and hooks:read are also used at run time: a token missing those breaks Trigger Scenario itself, not just a dropdown. Scopes are fixed at token creation, so create a new token if one is missing.

Can I trigger a scenario that is turned off?

Yes. The webhook accepts the request and queues the run; it processes once the scenario is activated. If you expect immediate execution, make sure the scenario is active.

How do I get the scenario's result back in WeWeb?

By default Make responds Accepted immediately. Add a Webhook response module at the end of your scenario with Status 200 and a JSON Body (e.g. {"status":"done","customerId":"12345"}) — the action then returns that JSON instead, and you can bind its fields in later workflow steps. See the example under Trigger Scenario.