Run Multiple Engines at Once

A workspace is not locked to a single channel. WaDesk lets one workspace connect any combination of the three engines — Unofficial API, WhatsApp Cloud API (Meta), and Twilio — at the same time, and use them side by side across the whole app.

New in v1.1. Earlier versions used one engine per workspace. From v1.1 a workspace can hold several connected senders across different engines simultaneously.

Why use more than one engine

  • Keep a fast, no-approval Unofficial API number for support chats and an official Cloud API number for templated marketing — in the same workspace.
  • Add a Twilio sender for regions or numbers you run through Twilio.
  • Spread load and reduce risk by sending from several numbers.

How to set it up

  1. Your platform admin sets which engines are allowed under Admin → Settings (allowed sending engines) and on the workspace's plan.
  2. On the Devices screen, connect each number as usual: scan a QR for an Unofficial API number, run Embedded Signup (or enter Meta details) for a Cloud API number, and enter your Twilio sender details for Twilio. Each connected sender appears as its own card.
  3. That's it — the rest of the app now offers all of them.

How sending & replies work

  • Grouped sender pickers. Campaigns, Broadcasts, Scheduled messages, Flows, and the Chat composer show the available senders grouped by engine, so you choose exactly which number sends.
  • Per-message routing. The correct engine is resolved for each message based on the sender you picked — a single campaign always goes out through the engine of its chosen sender.
  • Reply on the same channel. Inbound messages are tagged with the engine they arrived on, and replies go back out on that same channel, so a customer who messaged your Cloud API number is answered from it.
  • Engine badges & filters. The inbox, dashboards, and message history label each item with its engine and let you filter by it.

Feature differences between engines

Some features are engine-specific and the app adapts automatically:

  • WhatsApp Forms and native template management are Cloud API features.
  • Twilio sends use Content Templates (ContentSid).
  • The Unofficial API needs the bundled Node bridge running; Cloud API and Twilio do not.

Developer detail on each engine: WhatsApp Engines. Channel setup: Connecting a Channel.

WaDesk Documentation