Instagram Automation
Instagram messaging and DM automation is planned — not available today.
Instagram automation would let Wavy receive and respond to Instagram direct messages, automate comment-to-DM flows, and manage story replies through the Instagram Messaging API. Wavy's backend handles WhatsApp messaging through the Meta Cloud API, but there is no Instagram messaging client, no Instagram webhook handler, and no Instagram-specific automation rule. The channel model supports a type field that could accommodate Instagram, but no Instagram channel type has been implemented. This page is not indexed because the capability is not live.
What does not exist
Removed from this page because it is not built.
The following were referenced in placeholder content but are not part of any live Instagram offering.
- Instagram messaging client — The backend has a WhatsApp client that calls the Meta Graph API messaging endpoint. There is no Instagram Messaging API client. No Instagram DM send, receive, or status path exists.
- Instagram webhook handler — The webhook receiver processes WhatsApp inbound messages and status receipts. It does not handle Instagram webhook events. No Instagram-specific webhook route has been added.
- Comment-to-DM automation — There is no logic to detect Instagram comments and send an automated DM. The rules engine evaluates WhatsApp new_message triggers; it has no Instagram trigger type.
- Story reply automation — There is no path to receive or respond to Instagram story replies. No story interaction object exists in the data model.
- Instagram channel type — The channel model has a type field (default: "whatsapp"), but no Instagram type has been registered. No Instagram channel can be created or configured.
What does exist
The WhatsApp infrastructure that Instagram would parallel — and why it is not Instagram.
Wavy has a messaging architecture that could be extended to Instagram, but the extension has not been built.
- WhatsApp messaging client — The
WhatsAppClientsends text and template messages through the Meta Graph API. This is WhatsApp-specific; Instagram uses a different API surface (Instagram Messaging API) that is not integrated. - Webhook receiver architecture — The
/webhooks/metaendpoint verifies and processes inbound webhooks. The architecture could be extended to handle Instagram events, but no Instagram event parsing or routing exists. - Rules engine — The automation engine evaluates triggers and filters on inbound messages. The trigger type is
new_messagefor WhatsApp. No Instagram trigger type has been added. - Channel model — The channel data model has a type field that could accommodate non-WhatsApp channels. The infrastructure for multi-channel exists in principle, but Instagram is not implemented.
- Instagram listed as planned — The integrations page lists Instagram and RCS messaging as planned additional channels. This is a roadmap item, not a current capability.
The intended path
What Instagram automation would look like when built.
If and when Instagram automation is built, the intended path would add an Instagram Messaging API client alongside the existing WhatsApp client, extend the webhook receiver to parse Instagram events, register an Instagram channel type in the channel model, and add Instagram trigger types to the rules engine. This would let Wavy receive Instagram DMs, automate responses through rules, and manage Instagram conversations in the same inbox as WhatsApp conversations.
The Instagram Messaging API requires a Meta app with the instagram_manage_messages permission, a connected Instagram Business or Creator account, and webhook subscription for Instagram messaging events. None of that integration work has been started. This page will be updated and the noindex directive removed when an Instagram messaging path reaches a configuration-dependent state — meaning an Instagram client exists, is workspace-scoped, and can be enabled with provider setup.
Questions
Instagram automation — straight answers.
Can I automate Instagram DMs through Wavy today?
No. There is no Instagram messaging client, no Instagram webhook handler, and no Instagram-specific automation rule. Wavy handles WhatsApp messaging only.
Does Wavy's Meta integration cover Instagram?
No. The WhatsApp client calls the WhatsApp Cloud API. Instagram uses a different API surface — the Instagram Messaging API — which is not integrated. The Meta access token used by the WhatsApp client is scoped to WhatsApp, not Instagram.
Can I at least receive Instagram messages in the Wavy inbox?
No. The webhook receiver processes WhatsApp inbound messages. It does not parse Instagram webhook events. No Instagram conversation can be created or displayed in the inbox.
Is the channel model ready for Instagram?
The channel model has a type field that could accommodate Instagram in principle, but no Instagram channel type has been registered or implemented. The infrastructure is multi-channel-ready; the Instagram implementation is not.
Will Instagram automation be added in the future?
Yes, it is a planned capability listed on the integrations page. When it reaches a configuration-dependent state — an Instagram client exists, webhook events are handled, and it can be enabled with provider setup — this page will be updated and the noindex directive removed.
Can I use the same Meta Business Manager for WhatsApp and Instagram?
That is a Meta configuration question outside Wavy's scope. Wavy's integration is WhatsApp-specific today. Even if your Meta Business Manager supports Instagram, Wavy has no code to interact with the Instagram Messaging API.
Instagram automation is planned, not shipped.
Explore Wavy's available WhatsApp messaging, automation, and campaign capabilities today. When Instagram integration is built, this page will say so plainly.