Skip to main content
Question

Does Manychat control WABA?

  • March 6, 2026
  • 1 comment
  • 8 views
SSTrey

When WhatsApp is linked & Approved on Manychat, does Manychat controls this WABA?

That means the WABA is locked to ManyChat's platform and Meta intentionally restricts direct API access to itself directly. Is this is by design? ie. ManyChat manages the API layer on my behalf.

 

I ask this because I’m trying to build a Make workflow to send an HTTP scenario from Google Sheets directly to a WhatsApp number via the META Whatsapp API. (to access it independently, via Meta).  I’m hitting a permission wall over and over again here.

Im not successful yet with A below. I want to try B now.

 

SUMMARY:

  • A:  Meta Cloud API — works only if YOU own and control the WABA directly, not through a Tech Provider like ManyChat
  • B:  ManyChat API — works only for existing subscribers, but since ManyChat owns the WABA, this is the correct path for your setup

    1 reply

    Fabio Gaulke
    Forum|alt.badge.img+3
    • Fabio Gaulke
    • Community Moderator
    • March 6, 2026

    Hi, ​@SSTrey!

     

    Yes, as Manychat is set as Partner + Credit Line, it controls the WABA.

    But you can use Manychat’s API to integrate with Make and send your content → /fb/sending/sendContent

     

    But, in my opinion, the best and “simpler” way to send content (including Message Templates) to contacts, is creating automations and using the /fb/sending/sendFlow endpoint.

     

    And Make has all the native nodes you need to create subscribers if needed or get the User IDs if a subscriber already exists in your Manychat account:

    You also need to create an extra automation to copy the WhatsApp ID to a custom field every time a contact is created. This is to use /fb/subscriber/findByCustomField, because the WhatsApp ID isn’t considered a system field in Manychat.

    This way - creating the flow with the Message Template - is also much easier easy to maintain. 😉

     

    Hope this helps!

    @fabio.gaulke | @monada.ag
    Community Terms & ConditionsCookie settingsAccessibility statement