No integrations settings surface — configured/connected/failing state is invisible
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start at the /settings/integrations entry point and trace the environment-variable integration configuration and worker sync-adapter registration described in #161. Define how configured, connected, erroring, and last successful sync are sourced; done means a read-only page lists Slack, Teams, Linear, GitHub App, HubSpot, and Postmark with those states.
Written by the indexing model from the issue text.
Description
Integrations are configured entirely through environment variables — Slack, Teams, Linear, GitHub App, HubSpot, Postmark. There is no settings surface showing which integrations are configured, which are connected, or which are failing.
Why it matters
Nobody can tell from the dashboard that the HubSpot sync is dead-lettering, that Linear sync never started because one of its three secrets is missing, or that the Slack bot is not deployed. Each of those is currently discovered by reading logs. Related: #161 asks the worker to publish which sync adapters it actually registered — that data is the natural backing for this page.
Fix
A /settings/integrations page listing each integration with configured / connected / erroring state and last successful sync. Read-only first; env vars stay the source of truth. Credential editing from the UI is a separate, larger decision.
- 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
-
bot:ai-assisted status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
midnightntwrk/midnight-js#1424 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mksglu/context-mode#1268 ·
Maintainers usually reply within 5 days
-
Edit:Opencheck:failed streams:edit
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
iptv-org/iptv#54352 · 1 comment ·
Maintainers usually reply within 1 day
-
[Table] reserveSelectedRowOnPaginate=false 时表头全选包含其他页数据Possibly taken @dvd233 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Tencent/tdesign-react#4416 · 2 comments ·
Maintainers usually reply within 1 day
-
area:widget bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
interledger/publisher-tools#894 ·
Maintainers usually reply within 1 day