WhatsApp

Delivery: Official add-on. WhatsApp in Fased uses linked WhatsApp Web sessions. The gateway owns the socket state, routes DMs and groups separately, and lets you choose a personal-number or dedicated-number operating model. Status: supported through WhatsApp Web using Baileys.

Pairing

Unknown DMs can require approval.

Groups

Group allowlists and mention behavior.

Troubleshooting

Shared channel repair steps.

Quick setup

Open Agents > selected Agent > Channels > WhatsApp and click Install. Restart the Gateway when prompted.
Return to Agent > Channels > WhatsApp.
Choose personal-number or dedicated-number setup.
Keep DM policy on pairing or allowlist to start.
Scan the QR code from WhatsApp.
Approve the first pairing request if using pairing mode.

CLI install:

fased plugins install @fased/whatsapp
fased gateway restart

CLI login:

fased channels login --channel whatsapp
fased pairing list whatsapp
fased pairing approve whatsapp <CODE>

Config shape:

{
  channels: {
    whatsapp: {
      dmPolicy: "pairing",
      allowFrom: ["+15551234567"],
      groupPolicy: "allowlist",
      groupAllowFrom: ["+15551234567"],
    },
  },
}

Operating model

Mode	Use when
Dedicated number	You want a clear bot identity and cleaner allowlists.
Personal number	You need to use an existing WhatsApp account and accept tighter self-chat/allowlist care.

When possible, use a dedicated number for Fased.

Runtime behavior

Linked session state is stored locally by the gateway.
DMs and groups route separately.
Group replies should start mention-gated or allowlisted.
Task commands create Agent-owned Tasks; WhatsApp is the transport.
Media and long output are subject to channel limits and chunking behavior.

Access model

Area	Recommended start
DMs	pairing or allowlist
Groups	allowlist plus mention gating
Personal-number mode	explicit self-chat and sender policy
Multi-account	named account per linked WhatsApp session

Troubleshooting

Symptom	Check
QR login fails	Existing session state, phone connectivity, gateway logs.
Bot ignores DMs	Pairing state, allowlist, phone number format.
Group replies missing	Group policy, mention requirement, group sender allowlist.
Session disconnects	Re-link QR and check host sleep/network state.
Messages duplicate	Personal-number self-chat policy and route/session settings.

Overview

Common setup

Team and enterprise

Self-hosted and protocol

Optional and legacy

Configuration and behavior

WhatsApp

Pairing

Groups

Troubleshooting

Quick setup

Operating model

Runtime behavior

Access model

Troubleshooting

​WhatsApp

Pairing

Groups

Troubleshooting

​Quick setup

​Operating model

​Runtime behavior

​Access model

​Troubleshooting

​Related

WhatsApp

Quick setup

Operating model

Runtime behavior

Access model

Troubleshooting

Related