Integromat (Make)

Log in to your Make account at make.com. Click Create a new scenario. On the blank scenario canvas, click the large + circle in the center to choose your first module — this is the trigger. In the module search, type 'webhook' and select Webhooks → Custom Webhook from the results. In the Custom Webhook configuration panel, click Add → give the webhook a descriptive name (e.g., FlutterFlow-UserSignup) → Save. Make immediately generates a unique webhook URL that looks like: https://hook.eu2.make.com/abc123xyz... (the region subdomain may differ based on your Make account's data region — eu2, us1, etc.). Click Copy address to clipboard and save the URL — this is what you will paste into FlutterFlow in the next step. IMPORTANT: Do not close this scenario yet. After configuring the FlutterFlow API Call (Step 2), you will come back to run a test POST from FlutterFlow so Make can 'determine the data structure' of your webhook payload. Make cannot map fields to downstream modules until it has seen at least one real sample payload. The webhook module will show 'Waiting for data...' until that test is sent. Note: Make scenarios must be activated (the toggle in the top-right of the scenario editor set to ON) before they run in production. While building, leave it off to avoid consuming operations on test runs.

In FlutterFlow, open the left nav and click API Calls → + Add → Create API Group. Name the group Make. Set the Base URL to the Make webhook URL you copied (e.g., https://hook.eu2.make.com/abc123xyz). Leave all authentication headers empty — the webhook URL is the only credential. Add a new API Call inside the group. Click + Add → Create API Call. Name it sendEvent (or something descriptive for the specific event you are sending). Set the Method to POST. Leave the endpoint path field empty — the Base URL is the complete URL. In the Body tab, set the body type to JSON. Define the JSON body with the fields you want to send to Make. For example, a signup event might look like: { "event": "user_signup", "name": "{{ name }}", "email": "{{ email }}", "plan": "{{ plan }}" } In the Variables tab, add the corresponding variables (name, email, plan — all String type). These become the binding points in your Action Flow Editor where you connect widget values or App State fields. Leave the Response & Test tab for now — you will parse the response in Step 4 if you add a Webhook Response module. For fire-and-forget scenarios, no response parsing is needed; FlutterFlow will receive a 200 Accepted response automatically. Click Save to save the API Call. You now have a complete Make webhook API Call ready to trigger from any widget action.

Before you can build the downstream modules in Make, Make needs to receive at least one real sample payload to understand the field names and data types in your webhook data. This is a required step — you cannot map fields to a Sheets column or a Slack message template until Make has seen the structure. In FlutterFlow's API Calls panel, open the sendEvent API Call. Go to the Response & Test tab. In the Variables section, fill in test values for each variable (e.g., name = 'Test User', email = 'test@example.com', plan = 'starter'). Click Send Test Request. If the Function is configured correctly and your Make scenario is on the canvas with the webhook module showing 'Waiting for data...', Make should receive the test payload within a few seconds. Go back to your Make scenario tab — the webhook module should now show a green checkmark and the list of fields it detected (event, name, email, plan). If Make does not receive the test: verify the webhook URL in FlutterFlow's Base URL exactly matches the URL Make generated (no trailing slash differences, correct region subdomain). Also confirm your Make scenario is saved (click Save in Make's scenario editor) — Make only listens for test data when the scenario is open in the editor, even if the scenario is not activated. Once Make has determined the data structure, the field names from your payload are available to map to any downstream module. You can now build the scenario by adding modules: a Google Sheets 'Add a Row' module, a Slack 'Create a Message' module, an HTTP module to call another API — whatever your automation needs.

Now build the automation inside Make. Click the + circle after the webhook module to add the first downstream module. Search for the app you want to connect — Slack, Google Sheets, HubSpot, Gmail, Airtable, or any of Make's 1,800+ connectors. For a Google Sheets example: select Google Sheets → Add a Row. Connect your Google account if you have not already. Choose the spreadsheet and sheet tab. Map the columns: for the Name column, click the field and select the name variable from your webhook payload (shown in the data structure panel). Map email and plan similarly. Click OK. Add another module for Slack: select Slack → Create a Message. Choose the channel. In the Text field, compose the message with Make's variable mapping: "New signup: {{name}} ({{email}}) on the {{plan}} plan". Click OK. Make executes modules left to right in your scenario. Each module run consumes one operation from your monthly quota. A scenario with 3 modules uses 3 operations per webhook trigger. To activate the scenario for production: click the ON toggle in the bottom-left of the Make scenario editor. Once active, every POST from FlutterFlow to the webhook URL triggers the full scenario. While the scenario is OFF, Make receives the data but does not process it (useful for testing without consuming quota). If you want the Make scenario to return data to FlutterFlow, add a Webhooks → Webhook Response module as the LAST module. Configure the Response body with the fields you want to return (e.g., {"ticketId": "{{generatedId}}"}). Change the webhook's Response setting to 'Respond immediately' off — this makes the webhook wait for the scenario to complete before sending the response. See Step 5 for wiring the response in FlutterFlow.

If your Make scenario ends with a Webhook Response module, FlutterFlow can read the returned JSON. In FlutterFlow's API Calls panel, open the sendEvent call and go to Response & Test. After triggering a test that goes through the full Make scenario (with the Webhook Response module active), paste the returned JSON into the Sample Response field and click Generate JSON Paths. FlutterFlow creates extractors for each returned field (e.g., $.ticketId, $.status). In your Action Flow, after the sendEvent API Call step, add an action that stores the extracted response fields in Page State variables and displays them to the user — a success dialog showing the ticket ID, a confirmation Text widget, or a navigation to a result screen. Security: by default, the Make webhook URL is unauthenticated — anyone who discovers the URL can trigger your scenario. For automations involving sensitive data or operations with real downstream effects, add a simple token check in Make: 1. In FlutterFlow's API Call, add a header: X-Auth-Token with value {{ authToken }}. Add authToken as a variable and set a hard-coded default value in the App Values (not a secret key, just a shared string like a random UUID). 2. In Make, add a Filter after the webhook module: only continue if {{headers.x-auth-token}} equals your expected token value. This stops random webhook triggers without needing a full Firebase Function proxy. It is sufficient for most FlutterFlow → Make scenarios because the operations are not financial or user-account-modifying. If you would rather skip the webhook security setup and automation logic entirely, RapidDev's team can set up Make scenarios alongside FlutterFlow apps quickly — book a free scoping call at rapidevelopers.com/contact.