Hi all!
I wanted to share a small service I built for cases where your workflow, CRM, helpdesk, or AI assistant needs to talk to users through WhatsApp, Instagram DM, or Facebook Messenger.
The official Meta APIs are the right production path, but the setup takes time: Meta Developer account, app permissions and review, tokens, and different payloads for each channel. To make all three channels work, you end up touching 50+ settings/parameters across Meta and your own webhook setup, and it is easy to miss one. It gets even more annoying when the channels belong to your client, not to you.
Fiwano removes that layer by giving you one transport API and couple of nodes. In n8n the core loop is: `Fiwano Trigger → your workflow → Fiwano Send Text`
All three channels arrive in the same shape:
```json
{
“event”: “message.received”,
“channel_id”: “…”,
“channel_type”: “whatsapp”,
“timestamp”: “2026-07-08T10:30:00Z”,
“data”: {
“from”: “…”,
“type”: “text”,
“text”: “Hi”
}
}
```
Reply with the same fields:
```text
Channel ID: {{$json.channel_id}}
Recipient: {{$json.data.from}}
```
That is the main point: for normal inbound → workflow → reply automations, you do not need separate WhatsApp / Instagram / Messenger workflows. `channel_type` is there for visibility, logging, or rare channel-specific UI, not as the default routing mechanism.
Fiwano is a focused transport service, not a chatbot builder. Your n8n workflow still owns the logic. The n8n package is verified by n8n and installs from the editor.
I also made a GitHub cookbook for builders: GitHub - fiwano-com/fiwano-cookbook: Working examples & API reference for building WhatsApp, Instagram & Messenger integrations on Fiwano — verified Meta Tech Provider. · GitHub . It has what you need for a quick integration, plus practical guides on Meta messaging windows, costs, and connection options.
There are two importable workflows:
- `fiwano-universal-auto-responder.json` - one trigger answers messages across WhatsApp, Instagram, and Messenger.
- `fiwano-connect-channels.json` - optional flow for connecting customer/client channels through the API.
Limits:
- Your n8n instance must be publicly reachable for webhooks.
- WhatsApp free-form replies work inside the 24-hour window. Outside it, use approved WhatsApp templates.
- Instagram and Messenger do not have a WhatsApp-template equivalent for arbitrary outbound starts after the allowed window.
- Fiwano is for messaging/DMs only, not comments, posts, ads, analytics, or the full Meta Graph API.
Links:
- Verified n8n integration: Fiwano integrations | Workflow automation with n8n
- Importable workflows: n8n-nodes-fiwano/workflows at main · fiwano-com/n8n-nodes-fiwano · GitHub
- Cookbook and Meta messaging guides: GitHub - fiwano-com/fiwano-cookbook: Working examples & API reference for building WhatsApp, Instagram & Messenger integrations on Fiwano — verified Meta Tech Provider. · GitHub
If you are building client messaging workflows in n8n, I would be happy to hear what still feels unclear or inconvenient.