Connectors feed your dashboard. Nexus uses each one read-only — it pulls recent activity into a normalized feed that skills read. Some providers only issue coarse OAuth scopes that include write access (Slack and GitHub, for instance), but Nexus never writes on its own: nothing is ever written back to a connected account without an approval — writes only happen through the approvals flow.
Manage everything in Settings → Connections.
Available connectors
| Connector | What Nexus reads | Actions it can propose today |
|---|---|---|
| Slack | Your mentions and messages you can see, via a user token that acts as you. | Send a message — send-risk, always approval-gated. |
| GitHub | Your notifications: mentions, review requests, assignments, and other activity on repos you watch. | Read-only today (no GitHub actions in the catalog yet). |
| Asana | Your tasks and their activity. Note: Asana's OAuth grants a full user scope (their model — there is no narrower read scope today). | Complete a task, comment on a task — reversible workspace writes. |
| Google — Gmail, Calendar, Drive | One connection per Google account: Gmail, Calendar, full Drive, and Meet — all through Nexus's own client, one consent screen. (While Nexus's Google verification is in progress, connecting is limited to invited test accounts and Google asks you to re-consent weekly.) | Send a Gmail draft or message — send-risk, always approval-gated (arriving with the current release). |
The action catalog grows over time; a connector reading your data doesn't imply Nexus can act on it. Whatever can be proposed is listed above, and every proposal is approval-gated.
A note on Slack's chat:write scope: it's requested at connect time so that approved messages can be sent — the scope is the capability, the approval is your consent per message. Workspaces connected before this scope was added need a reconnect before send actions work.
Lookback windows
How far back a connector read may reach is set by your plan, enforced server-side:
- Free — 7 days per connector. Every connector is included; only the window is limited.
- Pro / Team — full lookback.
The window applies to reads, not storage: connector content is fetched on demand for each run and isn't warehoused. What persists is what your runs write — briefs, memory entries, notes.
Multiple accounts
You can connect several accounts per provider — multiple Slack workspaces, multiple Google accounts (the Google flow always shows the account picker), multiple Asana accounts. Each connection is labeled so briefs say which account an item came from.
Copy connect link: next to Connect there's a copy-link button. The link is a short-lived (10-minute), single-purpose authorization URL you can open in any browser profile — useful when the provider has no account chooser (Asana) or when the right account lives in another profile.
Connection health
- A connection whose token stops working shows needs reconnect in Settings → Connections; briefs simply skip it until you reconnect. Reconnecting is the same button as connecting.
- Reconnecting creates a fresh connection under the hood. If an action proposal was pending against the old connection, reject it and let the next run re-propose.
Teams
Connectors are personal in v1 — they attach to your personal space only. Team dashboards are built from what members contribute (chat, notes, runs in the team space), not from members' connectors. See Teams.
Disconnecting
Disconnect deletes the connection's stored token, so Nexus can no longer reach that account. It does not revoke the grant at the provider's end — to fully revoke, also remove Nexus from that provider's connected-apps settings (for Google, your account permissions page). Deleting your Nexus account deletes every stored connector token as part of the purge — see the privacy policy.