Overview & configuration
Connect Proliferate to the tools your team already uses.
Integrations let agents pull real context and take action instead of waiting for you to paste it in. Connect Linear once and an agent can read an issue. Connect Slack once and it can find the thread you mentioned.
How it works
Connect an account in Settings and it becomes eligible for your sessions, through Proliferate's gateway. What a session gets depends on how it starts:
- Chat. A new chat session can use the integrations you've connected that are currently enabled for your organization. An org admin can narrow that default set from organization settings. See Integrations (admin).
- Workflows. A workflow step runs as an ordinary session in its workspace, so it gets the same integration access any session there would. See Workflows.
Integration credentials stay server-side. Proliferate stores your Linear and Slack tokens centrally and proxies each call, so the agent never sees a raw credential. Model auth is separate; see Authentication.
Two ways to connect
- OAuth. Click Connect, sign in through your browser, and approve access. Most pre-registered integrations (Linear, Notion, Slack, GitLab, and more) work this way.
- API key. Paste a key generated from the provider's own dashboard. Integrations like Context7, Exa, Tavily, Render, and Neon work this way.
Connections are personal
A connected account belongs to whoever connected it. If you connect Notion, your sessions can use it; a teammate needs their own. There is no team-shared integration account, even for tools an admin enabled org-wide.
Organization controls
Admins control two things: whether an integration exists for the org at all, and which of those a new chat session gets by default.