mirror of
https://github.com/labring/FastGPT.git
synced 2026-05-01 02:01:34 +08:00
Archer
4b24472106
* docs(i18n): translate batch 1 * docs(i18n): translate batch 2 * docs(i18n): translate batch 3 (20 files) - openapi/: app, share - faq/: all 8 files - use-cases/: index, external-integration (5 files), app-cases (4 files) Translated using North American style with natural, concise language. Preserved MDX syntax, code blocks, images, and component imports. * docs(i18n): translate protocol docs * docs(i18n): translate introduction docs (part 1) * docs(i18n): translate use-cases docs * docs(i18n): translate introduction docs (part 2 - batch 1) * docs(i18n): translate final 9 files * fix(i18n): fix YAML and MDX syntax errors in translated files - Add quotes to description with colon in submit_application_template.en.mdx - Remove duplicate Chinese content in translate-subtitle-using-gpt.en.mdx - Fix unclosed details tag issue * docs(i18n): translate all meta.json navigation files * fix(i18n): translate Chinese separators in meta.en.json files * translate * translate * i18n --------- Co-authored-by: archer <archer@archerdeMac-mini.local> Co-authored-by: archer <545436317@qq.com>
73 lines
2.7 KiB
Plaintext
73 lines
2.7 KiB
Plaintext
---
|
|
title: WeCom Bot Integration
|
|
description: FastGPT WeCom Bot Integration Tutorial
|
|
---
|
|
|
|
- Starting from version 4.12.4, FastGPT commercial edition supports direct WeCom bot integration without additional APIs.
|
|
- Starting from version 4.14.4, FastGPT cloud service edition supports WeCom intelligent bot integration through custom domain configuration.
|
|
|
|
## 1. (Required for Cloud Service Edition) Configure Custom Domain
|
|
|
|
WeCom requires intelligent bot message push addresses to use the enterprise's primary domain, so cloud service edition users must configure a custom domain before using WeCom bots.
|
|
|
|
- [Configure Custom Domain](/docs/introduction/guide/team_permissions/customDomain)
|
|
|
|
If you are a commercial edition user, continue using your enterprise domain.
|
|
|
|
## 2. Create an Intelligent Bot
|
|
|
|
### 2.1 Super Admin Login
|
|
|
|
[Click to open WeCom Admin Console](https://work.weixin.qq.com/)
|
|
|
|
### 2.2 Find the Intelligent Bot Entry
|
|
|
|
On the "Security & Management" - "Management Tools" page, click "Intelligent Bot" (Note: Only the enterprise creator or super admin has permission to see this entry)
|
|
|
|
|
|
|
|
### 2.3 Select "API Mode Creation" for the Intelligent Bot
|
|
|
|
On the create bot page, scroll down and click "API Mode Creation"
|
|
|
|
|
|
|
|
### 2.4 Get Key Credentials
|
|
|
|
Randomly generate or manually enter Token and Encoding-AESKey, and record them
|
|
|
|
|
|
|
|
### 2.5 Create WeCom Bot Publishing Channel
|
|
|
|
In FastGPT, select the Agent you want to use. On the Publishing Channels page, select "WeCom Bot" and click "Create"
|
|
|
|
|
|
|
|
### 2.6 Configure Publishing Channel Information
|
|
|
|
Configure the publishing channel information. You need to enter the Token and AESKey recorded in step 2.4 (Token and Encoding-AESKey)
|
|
|
|
|
|
|
|
### 2.7 Copy Callback URL
|
|
|
|
After clicking "Confirm", select your configured custom domain, copy the callback URL, and paste it back into the WeCom intelligent bot configuration page.
|
|
|
|
|
|
|
|
## 3. Use the Intelligent Bot
|
|
|
|
In the WeCom platform's "Contacts", you can find the created bot and start sending messages
|
|
|
|
|
|
|
|
## FAQ
|
|
|
|
### Sent a message but no response
|
|
|
|
1. Check if the trusted domain is configured correctly.
|
|
2. Check if Token and Encoding-AESKey are correct.
|
|
3. Check FastGPT chat logs to see if there is a corresponding question record.
|
|
4. If there is no record, the app may have encountered an error. Try the simplest bot first.
|