feat: Webhook integration for team notifications (Feishu/WeChat Work)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 342
- Avg merge
- 13h 48m
- Merged PRs (30d)
- 211
Description
Feature Request
Summary
Add webhook support to notify team members via Feishu (Lark) or WeChat Work (WeCom) when certain events occur in TeamAI.
Use Case
Our team uses Feishu/WeChat Work as the primary communication tool. We want to:
- Track team activity - Know when colleagues push/pull resources
- Monitor skill usage - Understand which skills are being used
- Session visibility - Get notified when team members start/stop AI sessions
Proposed Solution
Add webhook configuration in teamai.yaml:
sharing:
webhooks:
enabled: true
endpoints:
- url: https://open.feishu.cn/open-apis/bot/v2/hook/xxx
type: feishu
events: [push, pull, skill-use, session-start, session-stop]
- url: https://qyapi.weixin.qq.com/cgi-bin/webhook/send?key=xxx
type: wecom
events: [push, pull]
Events to Support
| Event | Description |
|---|---|
push |
Resource pushed to team repo |
pull |
Resources pulled from team repo |
skill-use |
AI tool invoked a skill |
session-start |
AI session started |
session-stop |
AI session ended |
Questions for Maintainers
- Is this feature aligned with the project direction?
- Should webhook be a built-in feature or a plugin?
- Any preferred event naming convention?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed sharing.webhooks configuration in teamai.yaml and the listed push, pull, skill-use, session-start, and session-stop events. Resolve whether this belongs in the core or a plugin, define the event naming and Feishu/WeCom payload requirements, and confirm the maintainers’ direction before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100