docs: finalize remaining setup heading phrasing (#22543)
* docs: fix thinking link and add reasoning anchor reference * docs(channels): rename LINE setup heading to onboarding * docs(channels): normalize Nextcloud Talk onboarding headings * docs(channels): use onboarding heading for Matrix setup * docs(channels): standardize Discord onboarding heading * docs(channels): standardize Telegram onboarding heading * docs(channels): standardize WhatsApp onboarding heading * docs(channels): rename iMessage onboarding and configuration sections * docs(channels): rename Slack onboarding and configuration sections * docs(channels): rename Signal onboarding heading * docs(channels): standardize Nostr onboarding and configuration headings * docs(channels): standardize Zalo onboarding and configuration headings * docs(channels): standardize Twitch onboarding heading * docs(channels): standardize Google Chat onboarding heading * docs(channels): standardize Mattermost onboarding heading * docs(channels): standardize Zalo Personal onboarding heading * docs(channels): normalize Discord configuration heading * docs(channels): standardize Microsoft Teams onboarding heading * docs(channels): rename Signal configuration reference heading * docs(channels): rename Matrix configuration reference heading * docs(channels): normalize WhatsApp configuration heading * docs(thinking): link reasoning section heading to in-page anchor * docs(channels): normalize BlueBubbles configuration heading * docs(channels): normalize Feishu configuration heading * docs(channels): standardize Signal setup option headings * docs(channels): refine Twitch setup heading clarity * docs(channels): simplify Zalo setup heading phrasing * docs(channels): trim Microsoft Teams minimal setup heading
This commit is contained in:
@@ -236,7 +236,8 @@ This is often easier than hand-editing JSON manifests.
|
||||
2. Find the bot in Teams and send a DM
|
||||
3. Check gateway logs for incoming activity
|
||||
|
||||
## Setup (minimal text-only)
|
||||
## Setup (minimal)
|
||||
|
||||
|
||||
1. **Install the Microsoft Teams plugin**
|
||||
- From npm: `openclaw plugins install @openclaw/msteams`
|
||||
|
||||
@@ -67,7 +67,7 @@ Minimal config:
|
||||
- Each account maps to an isolated session key `agent:<agentId>:twitch:<accountName>`.
|
||||
- `username` is the bot's account (who authenticates), `channel` is which chat room to join.
|
||||
|
||||
## Setup (detailed)
|
||||
## Setup (detailed, recommended)
|
||||
|
||||
### Generate credentials
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ It is a good fit for support or notifications where you want deterministic routi
|
||||
- DMs share the agent's main session.
|
||||
- Groups are not yet supported (Zalo docs state "coming soon").
|
||||
|
||||
## Setup (fast path)
|
||||
## Setup (quick path)
|
||||
|
||||
### 1) Create a bot token (Zalo Bot Platform)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user