CopilotKit / CopilotKit/outpost

No integrations settings surface — configured/connected/failing state is invisible

Open
#209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area: product roadmap roadmap: later
Dominant language
TypeScript
Stars
7
Forks
3
Avg merge
7d 16h
Merged PRs (30d)
15

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
typescript
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.