Integrations (Dashboard)
The dashboard view of every integration Chief is connected to in your tenant. For the capabilities of integrations, see Features → Integrations.
What You See
Each integration is a card with:
- Name & icon
- Status — ✅ healthy, ⚠️ token expiring, ❌ failing
- Connected by — the user who set it up
- Last used — most recent task that touched this integration
- Scope summary — what permissions the credential has
Adding a New Integration
Click + Add Integration.
- First-class options show one-click OAuth buttons (Google, Stripe, GitHub, etc.).
- Custom API opens a form for base URL + auth method.
- Bring your own MCP server lets you point Chief at a self-hosted MCP endpoint.
After connecting, Chief runs a quick capability probe — listing what tools the integration exposes — so you can see what Chief will be able to do.
Connection Health
Tokens expire. Chief pings every connection on a schedule and on each use. When a token is close to expiry, you’ll see a ⚠️ on the card and Chief sends one DM to admins.
Failed connections move to ❌ and are excluded from new tasks until repaired. Existing crons that depend on a failed connection are auto-paused with a notification.
Repairing a Failed Connection
Click the integration → Reconnect. For OAuth, this restarts the consent flow. For API-key auth, you paste a fresh key.
If the integration also exposes a Test button, use it to confirm the fix before unpausing dependent crons.
Disconnecting
Integration → Settings → Disconnect. The credential is permanently deleted. You can re-add later, but any in-flight tasks using it will fail.
Scopes & Permissions
For OAuth integrations, the granted scopes are listed at the bottom of the card. To change scopes, disconnect and reconnect — Slack/Google/etc. require a fresh consent flow when scopes change.
Audit Log
Every integration call Chief makes is logged. Click Activity on any integration card to see the call history: timestamp, action, status, and the Slack thread that triggered it.