Connecting Another Platform: Which Method to Use
Scope Wiser has six ways to exchange data with another system, and they look alike. Start from what you want to happen, and this page tells you which one to build and where it lives.
Scope Wiser can exchange data with your shop, your CRM, your booking system or your own software. There are six ways to do it, several have the word webhook in the name, and picking the wrong one costs an afternoon.
This page is the decision. Find the sentence that matches what you want, and go to the guide it points at.
Start from what you want to happen
"Something happens in another system, and a WhatsApp message should go out." An order is placed, a payment clears, a form is submitted, a delivery is dispatched. → Webhook Workflow. Read Webhook Workflow: Complete Beginner's Guide.
"Something happens in a chat, and another system should know." A customer finishes a form, taps a button, or shares their location, and it should land in your CRM. → Outbound Actions. Read Outbound Actions: Push Bot Data to Any CRM.
"Mid-conversation, look something up and carry on." Check a booking reference, fetch a stock level, quote a price, and branch on the answer. → the HTTP API block in the Flow Builder. Read Calling External APIs From a Flow.
"Mirror every message into my own system." A copy of everything in and out, plus delivery and conversation status changes. → Bot Settings → Webhook. Read Bot Settings Explained: All Eight Tabs.
"My own software should drive Scope Wiser." Create contacts, send messages, read conversations, pull catalogue orders on a schedule. → the Developer API. Read Scope Wiser API: Overview and Authentication.
"I would rather not touch webhooks at all." → an automation platform sits in the middle and does the plumbing. Read Zapier: Setup and Top Use Cases or Make.com and n8n: Connecting Scope Wiser.
The same six, as a table
Method | Direction | Where it lives | Who builds it |
|---|---|---|---|
Webhook Workflows | In — and a template goes out | Automation → Webhook Workflows | Anyone |
Outbound Actions | Out | Automation → Outbound Actions | Anyone |
HTTP API block | Out, and the answer comes back | Flow Builder | Anyone, with an API to call |
Bot Settings → Webhook | Out, everything | Bot Settings → Webhook | A developer |
Developer API | You call Scope Wiser | Avatar menu → API Developer | A developer |
Google Sheets | In, on a schedule | Integrations → Google Sheets | Anyone |
Direction is the thing to get right. In means the other system starts it. Out means Scope Wiser starts it.
Where each one actually is
Everything except the Developer API lives inside Chatbot Manager, on the bot it belongs to.
Automation → Outbound Actions — the page calls itself Out-bound Webhook. Same feature.
Automation → Webhook Workflows — WhatsApp bots only.
Integrations → HTTP API — the named API calls your flows and automations use.
Integrations → Google Sheets — headed Google Sheet Data Fetch Campaigns.
Bot Settings → Webhook — the Bot Settings button, top right, then the Webhook tab.
Developer API — your avatar, top right of any page, then API Developer.
When two of them would work
Some jobs genuinely have two answers. These are the ones worth thinking about for a minute.
A new lead should reach your CRM. Outbound Actions sends a fixed set of subscriber fields and forgets about it. The HTTP API block composes exactly the request your CRM documents and can use the reply. Start with Outbound Actions; move to the HTTP API block when the CRM wants a shape Outbound Actions cannot produce.
An order should trigger a message. A Webhook Workflow if the shop can call a URL — which WooCommerce and Shopify both can. The Developer API if you would rather your own code decide when to send.
You need a whole conversation somewhere else. Bot Settings → Webhook pushes it as it happens. The Developer API's conversation endpoint pulls it when you ask. Push if you want it live; pull if you want it on a schedule and would rather not host a listener.
What every method needs from you
Three things trip up every integration, whichever route you take.
An approved template, whenever Scope Wiser starts the conversation. Outside 24 hours of the customer's last message, WhatsApp delivers only an approved template. No integration gets around this — it is Meta's rule. Get the template approved before you build the automation that needs it.
Phone numbers in the right format. Country code first, digits only, no +. Shops routinely store the plus sign, and it is the single most common reason a correctly-built workflow sends nothing.
A stable key. Use the subscriber id to tie a record in your system back to the conversation here. Names get edited and numbers get re-typed; the id does not.
Integrations are per bot
An outbound action, a webhook workflow or an HTTP API belongs to the bot you created it on. Running the same integration on a WhatsApp number and a Facebook Page means building it twice. Worth knowing before you plan a rollout across several numbers.
If you are not sure yet
Build the direction you can test today. A Webhook Workflow can be built from a pasted sample payload with no shop connected at all — paste the JSON, press Run Test, and the mapping fields fill in. That is usually the fastest way to find out whether the shape of your data fits, before anyone installs a plugin or writes a line of code.
What to read next
Webhook Workflow: Complete Beginner's Guide — the most-used integration in the product.
Outbound Actions: Push Bot Data to Any CRM — the other direction, in six minutes.
Scope Wiser API: Overview and Authentication — if you have a developer and your own system.
Google Sheets: Connect, Import and Use Data in Replies — the no-code middle ground.