Skip to main content
Integrations Connecting a provider gives Squad up to three things. Events it can start an agent on, tools an agent can call while it runs, and content that becomes signals. Not every provider gives all three. Jira Service Management and Fellow also offer a workflow, which brings their content in on its own with no agent involved.
The Integrations page
Open Integrations in the workspace nav. Providers you’ve connected sit under Connected, the rest under Discover. A connection belongs to one workspace, so two workspaces in the same organisation can connect different tools.

​
Every provider

Slack

Capture feedback from Slack, read channel history from an agent, and get Squad’s output posted back into a channel.

Notion

Watch a Notion page for changes, and let an agent read the page it was triggered from.

Gong

Turn recorded sales calls into signals, with an agent that runs the moment a call lands.

Jira Service Management

Turn customer requests into signals on their own, and reply to them from an agent flow.

Linear

Start an agent when an issue or comment changes, read your issues, and file new ones from a flow.

GitHub

Run an agent when an issue opens or a pull request merges, and open or comment on issues from a flow.

PostHog

Query your product analytics from an agent, and run one when PostHog forwards an event.

Fellow

Turn AI meeting notes and transcripts into signals as Fellow finishes each one.

Review sources

App Store, Play Store, Google and Trustpilot reviews, imported daily as signals.

​
Categories

The filter in the top right offers six categories. Analytics, communication, database, developer tools, productivity and review sources. No provider uses productivity, so filtering by it always shows an empty grid.

​
The three ways to connect

A new workspace starts with every provider under Discover and nothing connected. Each card carries a Connect button.
The Integrations page before anything is connected, every provider under Discover
How Connect behaves depends on the provider.
Linear, Gong, Slack, Notion and Jira Service Management send you to the provider’s consent screen. Approve there, and you land back on the integration’s detail page in Squad with a green Connected badge.
GitHub’s card works the same way but takes you to a GitHub App install screen rather than an OAuth consent screen. That’s where you choose the account and the repositories Squad may see.

​
Setup required

A provider can be connected and still not working. When OAuth finishes but a step on the provider’s side is outstanding, the integration sits in Setup required. That’s an amber badge on the detail page, an amber border on the card, and a Finish setup button in place of Manage. Gong is the provider that lands there today. Its OAuth grant doesn’t give Squad a way to verify inbound webhooks, so the connection waits until you paste the verification public key from your Gong webhook rule. See Gong.

​
How triggers and tools reach your agents

An agent that starts from an integration event picks the trigger in the agent builder. The picker only lists providers that are connected and declare at least one trigger.
Slack declares no agent triggers by design, so it never appears in that picker. Neither do the review sources, which declare no triggers and no agent tools, so no agent can be started by a new review. See Slack and Review sources.
A triggered agent can always read the thing that started it, so the trigger provider’s read tools are there without being granted. Everything else comes from that connection’s row in the agent builder, set to None, Read only or Read & write. A few providers name their own levels, like Notion’s Can view. Write tools only ever come from an explicit Read & write, so a triggered agent never writes by accident. See Agent tools and access.
The chat assistant is different. It gets the read and write tools of every active integration with no configuration, because you’re in the loop for every message.

​
Connection health and disconnecting

The detail page header shows the status. Connected in green, Setup required in amber, Disconnected in red when the connection failed or was revoked. Below it sit the connected account and the date you connected.
If a connection predates Squad’s webhook routing, the detail page shows an amber banner. Its triggers never fire until you reconnect.
Disconnect lives in the Danger Zone at the bottom of the detail page. It drops the provider’s triggers and tools, and tears down any webhook Squad registered for you.
Gong is the exception. You created its rule inside Gong, so turn it off in the Gong admin as well.