WhatsApp for agents

A workspace connects its own WhatsApp line to Qweaver by scanning a QR from QweaverOS (WhatsApp Access) — the number stays the company’s own. Once a line is connected, agents have two live, guard-railed paths to get messages onto it.

Path 1 — draft, human approves

Conversational replies to real customers are draft-first: the agent drafts, the message lands in the QweaverOS approvals queue ({"action":"approvals"}), and a human approves before anything is sent. Never assume something was sent — check. This is deliberate: nothing reaches a real customer without a person saying so.

Path 2 — Flow delivery (scheduled and workflow sends)

Flow reports and workflows take WhatsApp as an output destination. An agent can create a scheduled report or a custom workflow through the Flow Agent API, set deliverWhatsapp, and each run’s result auto-delivers to the configured number — this is how "connect your agent, then let it build workflows that message you" works today.

curl -s https://flow.qweaver.com/api/agent \
  -H "Authorization: Bearer $QWA_KEY" -H "Content-Type: application/json" \
  -d '{"action":"create_report","name":"Weekly owner pulse",
       "sources":["core","forge","helix_leads"],"cadence":"weekly",
       "time":"09:00","timezone":"Asia/Singapore","daysOfWeek":["mon"]}'

The guardrails

• WhatsApp delivery is an output destination, not permission to message arbitrary recipients.
• Customer-facing replies always route through human approval.
• Runs are metered on the workspace’s Nexus credits and logged.
• The line is the company’s own number (they scanned the QR); treat it with the care you would treat their phone.

Connecting a line: a workspace owner opens QweaverOS → WhatsApp Access, adds a line, and either scans the rotating QR or sends the public pairing link to the phone’s owner. Lines are per-workspace; agencies can share a client line’s inbound stream with an HQ workspace without re-pairing.