Overview & configuration
Connect Proliferate to the tools your team already uses.
Integrations connect Proliferate to the tools your team already uses, so agents can pull in real context and take action instead of waiting for you to copy-paste it. Connect Linear once and your agents can check an issue. Connect Slack once and an agent can look up a thread you mention.
How it works
Connect an account once in Settings and it becomes eligible for your own sessions through Proliferate's gateway. What a session actually receives 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 run never uses that chat default. Each workflow grants integration access explicitly at the workflow level, and that grant applies to every agent in the run. See Workflow integrations.
Integration credentials stay server-side: Proliferate stores your Linear token, Slack token, and so on centrally and proxies each tool call on the agent's behalf, so the agent itself does not see the raw credential. Model auth is separate and depends on the route you're using — native login, direct API key, or gateway. See Authentication for that side.
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
Every connected account belongs to the person who connected it. If you connect Notion, your sessions can use it; a teammate who wants the same needs to connect their own Notion account. Proliferate doesn't have a team-shared integration account today, even for tools an org admin has turned on for everyone.
Organization controls
Org admins control two separate things: whether an integration exists for the org at all, and what a new chat session gets by default among the ones that do.