Make.com and n8n: Connecting Scope Wiser

Connect Scope Wiser to Make.com or n8n in both directions: push chatbot data out with Outbound Actions, and let a scenario or workflow trigger a WhatsApp message through a Webhook Workflow.

Last updated Sep 5, 2026

Make and n8n do the same job as Zapier: they sit between Scope Wiser and everything else, so neither side needs to know about the other. Make is hosted and visual. n8n can be hosted by you, which is often the deciding factor where data has to stay in a particular country.

Neither has a purpose-built Scope Wiser app, and neither needs one. Both connect with a webhook in one direction and an HTTP request in the other, and both are quick to build.

The one thing to settle first: which direction

Scope Wiser → Make / n8n. Something happens in a conversation and you want it recorded or acted on elsewhere. Scope Wiser pushes with Outbound Actions; the automation platform catches it.

Make / n8n → Scope Wiser. Something happens in another app and a WhatsApp message should go out. The automation platform sends; Scope Wiser catches it with a Webhook Workflow.

Most real setups end up building both, one at a time. If you are not sure which you need, Connecting Another Platform: Which Method to Use settles it in a minute.

What you need

A Make or n8n account. On n8n, a workflow you can activate — the URL you need only works properly once it is published.
A connected channel in Scope Wiser and a bot worth wiring up.
For the outbound direction, something that collects data — usually a User Input Flow. What User Input Flows Are and When to Use Them covers building one.
For the inbound direction, an approved WhatsApp template. Scope Wiser is starting the conversation, so nothing else will deliver.

Direction one: Scope Wiser sends

Make

Create a new scenario.
Add the Webhooks app and choose the Custom webhook module.
Click Add, give the webhook a name, and save. Make generates a URL — copy it.
Leave the scenario listening. Make works out the data structure from the first real request it receives, so it needs one before you can map anything.

n8n

Create a new workflow and add the Webhook node.
Copy the Test URL for now.
Click Listen for test event so n8n is actually waiting.

The n8n trap worth knowing before it costs you an hour. The Webhook node has two addresses: a Test URL and a Production URL. The test one only listens for about two minutes after you press Listen for test event, and it exists so you can watch the data arrive in the editor. Paste that one into Scope Wiser permanently and your integration will work once, in front of you, and never again. Build with the Test URL, then publish the workflow and swap Scope Wiser over to the Production URL. Production runs show up under the Executions tab rather than in the canvas.

Then, in Scope Wiser

Open Chatbot Manager, select the bot, then Automation → Outbound Actions. The page is headed Out-bound Webhook.
Click Create.
WEBHOOK NAME * — name it for the destination: Make — new lead, n8n — location shared.
OUT-BOUND WEBHOOK URL * — the URL you copied.
SELECT ACTIONS THAT WILL TRIGGER THE WEBHOOK? * — tick POSTBACK, USER INPUT FLOW or LOCATION.
SELECT DATA FIELDS THAT WILL BE SENT? * — tick what the other side needs. Always include SUBSCRIBER ID, and include INPUT FLOW DATA if you want the answers rather than just the person.
Save.

Now trigger it for real: message the bot and complete the flow to the end. Make will read the structure from that request; n8n will show it in the canvas. Only then build the rest of the scenario or workflow.

Outbound Actions: Push Bot Data to Any CRM covers the field picker in full, including why POSTBACK ID and INPUT FLOW DATA stay unavailable until their trigger is switched on.

Direction two: Make or n8n sends

This direction is a Webhook Workflow, and the automation platform is just the thing that calls it.

In Scope Wiser, open Automation → Webhook Workflows and click Create.
Give it a WORKFLOW NAME and pick the approved MESSAGE TEMPLATE it should send, then press Create Workflow.
Copy the Webhook Callback URL from the Configure Webhook Data card.
In Make, add the HTTP app's Make a request module. In n8n, add the HTTP Request node.
Set the method to POST, the URL to the callback URL, and send your data as JSON.
Send one real request, then go back to Scope Wiser and map the fields.

On the mapping step, the Custom JSON Body tab is usually faster than waiting for a live event: paste a sample of what your scenario sends, press Run Test, and the mapping rows fill from it. Webhook Workflow: Complete Beginner's Guide covers mapping, formatters, conditions and the report in detail — including the Trim Left formatter that strips the + from phone numbers, which almost every integration needs.

Automations worth building first

Small ones, that fail visibly. These are the four that earn their keep quickest.

Build this	Direction
Form completed in chat → row in your database or CRM	Scope Wiser sends
New paid invoice in your accounting tool → WhatsApp confirmation	Make / n8n sends
Booking made in your scheduling app → WhatsApp reminder the day before	Make / n8n sends
Customer shares location → dispatch task created	Scope Wiser sends

Resist wiring five things at once. Each one is five minutes; debugging five at once is an afternoon.

When data does not arrive

Work along the chain rather than guessing.

Nothing reached Make or n8n. Check LAST CALLED AT on the Outbound Actions list. Blank means Scope Wiser never fired — usually the trigger event did not actually happen, because the test flow was abandoned halfway rather than completed.
It worked once and then stopped, on n8n. The Test URL. Publish the workflow and move Scope Wiser to the Production URL.
Make shows no fields to map. It has not seen a request yet. Trigger one real event, then reopen the module.
Scope Wiser received the call but sent nothing. Look at SKIPPED before FAILED on the Webhook Workflows list — SKIPPED means one of your own rules excluded it, which is not a fault.
FAILED is climbing. Almost always the phone number: a leading +, a missing country code, or a number with no WhatsApp account.
A template variable comes out blank. The mapping points at a field that is missing from this particular payload. A Default Value formatter covers the gap.

Make, n8n, Zapier or Pabbly?

All four connect the same way, so choose on price and hosting rather than capability.

Zapier — the largest app library, the simplest to start. Zapier: Setup and Top Use Cases.
Make — cheaper at volume, and better where a scenario branches or loops.
n8n — self-hostable, so the data never leaves your infrastructure. The usual choice where that is a requirement rather than a preference.
Pabbly — covered alongside Zoho Flow in Pabbly Connect and Zoho Flow.

If you already pay for one, use that one. The Scope Wiser side is identical in every case.