Guides · Quick reference
Channel cheat sheet · Quick reference
One card per channel: what you need, how it's identified, and the step that fails most · a 1-minute lookup
How to use this: each card is a pocket summary to choose and connect a channel. For the full step by step, go to the corresponding channel guide. All Meta channels connect with the same 2-step panel flow (see the 2-step connection addendum).
Cards index
Card 1 · WhatsApp (QR mode)
| Who it's for | Anyone who wants to keep their number and their WhatsApp app on the phone. |
|---|---|
| How it connects | You scan a QR code from the panel (like Linked Devices). |
| Minimum | Your phone with WhatsApp. |
| What you need | Your phone with WhatsApp, 2 minutes. No Meta App. |
| Technical identity | whatsapp channel (no Meta identity). |
| Upside | Super fast, you keep the phone app. |
| Risk | It's an unofficial route: Meta can disconnect/block the number. Don't use a business-critical number as your only channel. |
| Trap #1 | One number, one route. The same number can't be on QR and Cloud at once, nor scanned in two sessions (they kick each other out and you risk a block). |
Captura próximamentePHOTO/CLIP 1 — the panel showing the WhatsApp QR ready to scan.
Card 2 · WhatsApp Cloud API (official, BYOC)
| Who it's for | Anyone who wants Meta's official and stable route and can dedicate a number. |
|---|---|
| How it connects | Meta App → WhatsApp product → credentials → 2-step webhook. |
| Minimum | A Meta App + a dedicated number (not active in the regular app). |
| What you need | Meta App, WABA, a dedicated number (not active in the regular app), App Secret (32 hex), Access Token. |
| Technical identity | meta channel, meta_object_type = whatsapp, meta_object_id = Phone Number ID. |
| Upside | Maximum stability, official templates, no ban risk. |
| Risk | The number stays dedicated to the API (you don't use it on the phone). Requires business verification for production. |
| Trap #1 | The API Setup token expires in 24 h → use a permanent System User token for production. |
| Full guide | WhatsApp Cloud API — Chapter 1 (in preparation) |
Captura próximamentePHOTO/CLIP 2 — the API Setup screen with Phone Number ID and WABA ID.
Card 3 · Facebook Messenger (Page)
| Who it's for | Businesses that receive messages on their Facebook Page. |
|---|---|
| How it connects | Meta App → Messenger → credentials → 2-step webhook. |
| Minimum | A Facebook Page you manage with full access. |
| What you need | Facebook Page (you a full-access administrator), App Secret (32 hex), Page Access Token, Page ID. |
| Technical identity | meta channel, meta_object_type = page, meta_object_id = Page ID. |
| Webhook field | subscribe messages on the Page object. |
| Trap #1 | On the Page Connect, allow popups and give Full access; if your Page doesn't show up, add yourself in Business Settings → Pages → People. |
| Full guide | Guide A — Create your Meta App and connect Messenger(+ 2-step connection addendum) |
Captura próximamentePHOTO/CLIP 3 — Messenger API Settings with the Page connected (✓).
Card 4 · Instagram (DMs)
| Who it's for | Businesses that serve customers over Instagram direct messages. |
|---|---|
| How it connects | Professional Instagram + linked Page → Meta App → Instagram → 2-step webhook. |
| Minimum | Professional Instagram + a linked Facebook Page. |
| What you need | Professional Instagram, linked Facebook Page, App Secret (32 hex), Instagram Access Token, Instagram ID. |
| Technical identity | meta channel, meta_object_type = instagram, meta_object_id = Instagram ID. |
| Webhook field | subscribe messages on the Instagram object. |
| Trap #1 | Turn on Settings → Messages → Connected tools → Allow access to messages; without that switch, 0 messages. |
| Trap #2 | The object_id is the numeric Instagram ID, not your @username. |
| Full guide | Connect your Instagram to the assistant |
Captura próximamentePHOTO/CLIP 4 — Instagram with "Allow access to messages" turned green.
Comparison table (choose your channel)
| Channel | Official | Keeps phone app | Block risk | Identity (meta_object_type) | Key value (object_id) |
|---|---|---|---|---|---|
| WhatsApp QR | No | Yes | Medium-high | — (whatsapp) | — |
| WhatsApp Cloud | Yes | No | None | whatsapp | Phone Number ID |
| Messenger | Yes | N/A | None | page | Page ID |
| Yes | N/A | None | instagram | Instagram ID |
What ALL Meta channels share
- App Secret = exactly 32 hexadecimal characters (0-9, a-f). Truncated or with spaces → everything fails silently.
- 2-step webhook: generate Callback+Verify in the panel → paste in Meta → connect with credentials. Generate once, don't regenerate after pasting.
- Subscribe only the
messagesfield (not the 30+ boxes in the dialog). - The first valid message activates the channel (pending → connected).
- In the panel, each channel shows its type (whatsapp / page / instagram) so you know at a glance what each card is.
Cards based on the system's real channel model. Meta's interface changes frequently: labels may vary, but each channel's identity (type + id) and the 2-step flow stay the same.