channel-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Channel Setup

渠道设置

When to Use

使用场景

Use this skill when wiring a freshly connected channel (WhatsApp, Telegram, Instagram, Messenger, email, phone number) into code, or when deciding which sender ID to pass to the API.

当你将新连接的渠道（WhatsApp、Telegram、Instagram、Messenger、邮件、电话号码）接入代码，或者决定向API传递哪个发送者ID时，使用此技能。

The two-layer model

双层模型

Zavu has two objects that beginners often conflate:

Layer	What it is	Where it lives
Account	The connection to a provider: a WhatsApp Business Account, a Facebook Page, an Instagram account, a Telegram bot, an email domain, a phone number	Connected in the dashboard (Accounts, Phone Numbers) or via partner invitations
Sender	The API handle that ROUTES accounts: what you pass as `Zavu-Sender` , what carries the webhook and the AI agent	`GET /v1/senders`

Billing: accounts are what you pay for (a WhatsApp account, a channel connection, a phone number). Senders are free — they are the view that groups your accounts under one sending identity.

Connecting always yields a ready sender. When an account is connected and no sender references it, Zavu creates one automatically, named after the account (the WhatsApp verified name, the Page name, the @username). The first sender of a project becomes the default. Partner-invitation connects have always worked this way; every connect surface now does.

Zavu有两个常被初学者混淆的对象：

层级	定义	位置
Account（账户）	与服务商的连接：WhatsApp Business Account、Facebook主页、Instagram账户、Telegram机器人、邮件域名、电话号码	在控制台（Accounts、Phone Numbers页面）连接，或通过合作伙伴邀请连接
Sender（发送者）	用于路由账户的API句柄：你作为 `Zavu-Sender` 传递的内容，承载webhook和AI Agent	通过 `GET /v1/senders` 获取

计费规则： 账户是计费对象（例如WhatsApp账户、渠道连接、电话号码）。发送者免费——它们是将你的账户归为同一发送身份的视图。

连接后自动生成可用的发送者。当账户连接后且没有发送者引用它时，Zavu会自动创建一个发送者，命名与账户一致（WhatsApp验证名称、主页名称、@用户名）。项目的第一个发送者会成为默认发送者。合作伙伴邀请连接一直遵循此规则；现在所有连接界面均采用此逻辑。

Finding the sender to send from

查找用于发送的发送者

GET /v1/senders

is the answer to "what can I send with, and from where?". Each sender's

channels

array is the source of truth for capability — computed from its actual configuration, not inferred:

json

{
  "id": "sender_12345",
  "name": "Acme Store",
  "channels": ["whatsapp", "sms", "voice"],
  "isDefault": true
}

An empty
```
channels
```
array means the sender cannot send anything yet (a phone number alone does not enable SMS).
Omit
```
Zavu-Sender
```
to use the project's default sender.
To target a specific one, pass its ID as a header inside the send params object:
```
'Zavu-Sender': "sender_12345"
```
.

GET /v1/senders

接口可以回答“我可以用什么发送、从哪里发送？”的问题。每个发送者的

channels

数组是功能的真实来源——由实际配置计算得出，而非推断：

json

{
  "id": "sender_12345",
  "name": "Acme Store",
  "channels": ["whatsapp", "sms", "voice"],
  "isDefault": true
}

空的
```
channels
```
数组表示该发送者暂时无法发送任何内容（仅电话号码不会启用SMS功能）。
省略
```
Zavu-Sender
```
参数将使用项目的默认发送者。
若要指定特定发送者，在发送参数对象的请求头中传递其ID：
```
'Zavu-Sender': "sender_12345"
```
。

Per-channel wiring

按渠道配置

You connected...	The sender...	Send with
WhatsApp (embedded signup or invitation)	auto-created, `channels` includes `whatsapp` once the account is active	`channel: "whatsapp"`
Messenger Page / Instagram account	auto-created, named after the Page/@username	`channel: "messenger"` / `"instagram"`
Telegram bot	attached via `POST /v1/senders/{senderId}/telegram` (bot token from @BotFather)	`channel: "telegram"`
Email domain (verified)	attach with `emailAddress` on sender create/update	`channel: "email"`
Nothing yet (zero-setup start)	`enableSmsOneway: true` on `POST /v1/senders` or `PATCH /v1/senders/{senderId}` — no number, no credential, active immediately; recipients cannot reply	`channel: "sms_oneway"`
Phone number	route it to a sender ( `PATCH /v1/phone-numbers/{id}` with `senderId` ) — that is what turns SMS on; add `enableVoice` for calls	`channel: "sms"` / `"voice"`

One sender can carry several channels at once — that is the point: one

Zavu-Sender

, every channel.

你连接了...	发送者情况...	发送时指定
WhatsApp（嵌入式注册或邀请）	自动创建，账户激活后 `channels` 包含 `whatsapp`	`channel: "whatsapp"`
Messenger主页 / Instagram账户	自动创建，命名与主页/@用户名一致	`channel: "messenger"` / `"instagram"`
Telegram机器人	通过 `POST /v1/senders/{senderId}/telegram` 关联（从@BotFather获取机器人令牌）	`channel: "telegram"`
已验证的邮件域名	在创建/更新发送者时通过 `emailAddress` 字段关联	`channel: "email"`
尚未连接任何渠道（零配置启动）	在 `POST /v1/senders` 或 `PATCH /v1/senders/{senderId}` 中设置 `enableSmsOneway: true` ——无需号码、无需凭证，立即生效；接收者无法回复	`channel: "sms_oneway"`
电话号码	将其路由到某个发送者（通过 `PATCH /v1/phone-numbers/{id}` 并传入 `senderId` ）——这才是启用SMS的方式；添加 `enableVoice` 可启用通话功能	`channel: "sms"` / `"voice"`

一个发送者可以同时承载多个渠道——这正是设计的初衷：一个

Zavu-Sender

，支持所有渠道。

Constraints

限制条件

A sender belongs to one project; an account is routed by at most one sender.
Webhooks and AI agents are configured per sender, so they apply to every channel that sender carries.
Free plans include two connection slots (one can be a WhatsApp account); paid plans add connections at a monthly fee per connection. Creating senders never costs anything.

一个发送者属于一个项目；一个账户最多由一个发送者路由。
Webhook和AI Agent是按发送者配置的，因此会应用于该发送者承载的所有渠道。
免费套餐包含两个连接插槽（其中一个可为WhatsApp账户）；付费套餐按每月每个连接的费用增加连接数。创建发送者永远不收取任何费用。