Teams go-live: deploy the Teams bot
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker, typescript
Research direction
Start by inspecting apps/teams-bot and its Dockerfile, then identify how the service exposes the health endpoint on port 3003. Deploy to staging with SHADOW_MODE=true, verify /health and the Teams-to-ticket-to-assignee flow, and confirm the required Bot Framework and shared Outpost variables are set before production promotion. Review #177 before promoting production.
Written by the indexing model from the issue text.
Description
The Teams bot is built and has a Dockerfile, but is not deployed. Health port 3003.
Why it matters
Teams is the channel our enterprise customers use. Until this is deployed, the highest-value channel Outpost supports is not receiving anything, and those tickets are not auto-created or routed.
Checklist
- Create the Railway service pointed at
apps/teams-bot - Set the Bot Framework app ID + password and the shared Outpost env vars
- Deploy to staging first with
SHADOW_MODE=trueand confirm it logs rather than posts - Verify
/healthon3003returns green - End-to-end: message in Teams → ticket created → routed to the on-call assignee
- Promote to production
Blocked-by note: #177 (orphaned-reply handling is Teams-only) is worth resolving before the production promotion, not before staging.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 4
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 7
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from CopilotKit/outpost
-
area: docs area: security roadmap: now
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
CopilotKit/outpost#277 ·
Maintainers usually reply within 4 days
-
area: infrastructure roadmap roadmap: later
Difficulty 1/5 Under an hour Newbie friendliness 74/100
CopilotKit/outpost#179 ·
Maintainers usually reply within 4 days
-
area: ai roadmap roadmap: now
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/outpost#145 ·
Maintainers usually reply within 4 days
-
area: integrations priority: low roadmap roadmap: later
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
CopilotKit/outpost#124 · 3 comments ·
Maintainers usually reply within 4 days
-
area: integrations priority: low roadmap roadmap: later
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CopilotKit/outpost#123 · 2 comments ·
Maintainers usually reply within 4 days
All issues in CopilotKit/outpost
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
supadata-ai/mcp#27 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
capricorn86/happy-dom#2485 ·
Maintainers usually reply within 2 days
-
优化导入 OCR 模型选择文件的按钮样式Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
siyuan-note/siyuan#20430 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Albert-Weasker/niubigeo#194 ·
Maintainers usually reply within 1 day