Chatflow coexistence: template reads work; sending denied by Meta (#200)
Status: Open · Asked by Instacare Laundry on · 0 views
Please inspect the Meta sending authorization behind our existing Pabbly Chatflow coexistence connection. The workspace shows Connected/Active, and the owner confirms WhatsApp Business mobile and Web work. Preserve that same-number coexistence connection and our existing signed webhook receiver.
An authenticated GET /api/v1/templates?all=true succeeds with HTTP200. Three exact English Utility templates are APPROVED and match our Meta definitions. The installed backend API token matches the private workspace credential. The send payload follows your documented POST /api/v1/messages contract: numeric to, type=template, templateName and an ordered bodyParams array.
One separately approved personal diagnostic using instacare_payment_support_v1 returned HTTP400 at 2026-10-17T15:02:42Z. Chatflow returned status=error and Meta returned OAuthException, code200:
> (#200) You do not have the necessary permission to send messages on behalf of this WhatsApp Business Account
No Meta message ID was returned. Automatic retries are disabled. Please identify the exact missing sending permission, app/token authorization or WABA/phone asset assignment behind this connection, and provide a supported repair that preserves mobile/Web and existing webhook routing. We have not established which of these grants is missing. Template-read success and a Connected badge do not establish send permission.
Please do not ask us to delete/deregister the phone, reset the Business app, repeat onboarding or regenerate credentials without explaining the exact required change and continuity impact. API keys, tokens, account identifiers, recipient details and the Meta trace ID can be supplied only through an approved private support channel when needed; none belong in a public forum post.
Our automation is paused. No automatic retries, payment or paid-order writes occurred during this diagnostic. Please help identify and repair the exact sending authorization failure while preserving the existing mobile/Web coexistence and webhook routing.