Integrations
Two ways to connect WhatsApp. Neither of them is unlimited.
Most tools in this space describe what they can do and stay quiet about the rest. The table below is the same capability declaration the product reads at runtime — the one that disables a button and tells you why.
Sedge is not a WhatsApp product
WhatsApp Cloud API
OfficialMeta's official platform. Fully supported and compliant, but WhatsApp limits what it can do inside groups.
- Group size limit
- 8
- Works in existing groups
- no
- Message deletion window
- not supported
Linked device (unofficial)
UnofficialLinks Sedge to an existing WhatsApp account the way WhatsApp Web does. Full moderation capability in real groups.
- Group size limit
- 1,024
- Works in existing groups
- yes
- Message deletion window
- 48 h
Simulator
Built inA built-in test account with synthetic groups and traffic. Nothing leaves this server and no real WhatsApp account is involved.
- Group size limit
- 1,024
- Works in existing groups
- yes
- Message deletion window
- 48 h
WhatsApp Cloud API
Compliant, and genuinely restricted.
Meta's official platform is the safe choice, and it is the one we recommend where it fits. What it cannot do inside groups is not a gap in Sedge — it is the API.
- A group is capped at 8 participants. For most community groups, that rules it out.
- It only operates in groups the business itself created. It cannot be added to a group that already exists.
- It cannot delete a message. Sedge disables that action on this connection and offers removing the member instead.
- It cannot change admin roles, and cannot add a participant directly — members must join through an invite link.
- Message deletions and edits are not reported, so rules that depend on seeing them do not fire.
| Operation | Status | Detail |
|---|---|---|
| Receive messages | Supported | Works as expected. |
| Remove a member | Supported | Works as expected. |
| Delete someone else’s message | Not available | WhatsApp's official API cannot delete messages. You can remove the member instead. |
| Send a moderation notice | Supported | Works as expected. |
| Add a member to a group | Not available | Members must join via an invite link — WhatsApp requires them to opt in. |
| Create an invite link | Supported | Works as expected. |
| See joins and leaves | Supported | Works as expected. |
| Find your groups | Limited | Only groups created through this app. |
| Find communities | Not available | Communities aren't available in WhatsApp's official API. |
Linked device
Full capability, and real risk to the number you link.
This adapter connects the way WhatsApp Web does. It works in your real groups with full admin capability — and it is not an official Meta integration.
Read this before choosing it
Sedge will not let you connect this provider without acknowledging that, in the product, on the record. We do not implement ban evasion and we do not implement anything designed to defeat WhatsApp’s security controls — which means we cannot make this risk go away, only state it.
| Operation | Status | Detail |
|---|---|---|
| Receive messages | Supported | Works as expected. |
| Remove a member | Supported | Works as expected. |
| Delete someone else’s message | Limited | WhatsApp only allows deleting messages for everyone within about 48 hours. |
| Send a moderation notice | Supported | Works as expected. |
| Add a member to a group | Limited | If the member limits who can add them to groups, we send an invitation instead and wait for them to accept. |
| Create an invite link | Supported | Works as expected. |
| See joins and leaves | Supported | Works as expected. |
| Find your groups | Supported | Works as expected. |
| Find communities | Not available | Community structure is not exposed by this adapter; groups are managed individually. |
Simulator
A real connection with synthetic traffic.
Every installation ships with a built-in simulator: synthetic groups, synthetic members and synthetic messages, generated in-process. Nothing leaves the server and no WhatsApp account is involved.
It declares full capability, so every screen and every workflow can be exercised before you connect anything real. It is always labelled as a simulation, and its data is never mixed with a live connection’s.
Beyond WhatsApp
Getting events out of Sedge.
Sedge is deliberately narrow about what it connects to. It is broad about what it will tell other systems.
Webhooks
Signed deliveries for moderation events, connection status changes and review decisions, with retries, a delivery log and a dead-letter state you can see.
API keys
Scoped to a subset of your own permissions, revocable, and never able to reach the platform console. Reads and reports only — no key can change a moderation decision.
Try it on the simulator first.
Every plan includes it. Connect nothing, protect a synthetic group, and see the whole workflow before you decide which provider you want.