What integrations are
An integration gives Console’s agents a set of tools in one third-party app your team uses. Once an organization admin connects Slack, every agent in your organization can post to Slack. Connect Jira, and agents can file and update issues. Connect Confluence, and they can write up what they found. These are separate from the built-in tools every agent already has for reading code, scanning, and recording findings — those are in the tool reference. Integration tools exist only for apps an admin has connected. These are the apps you can connect today:
Each app’s page lists every tool by name, what it needs before you connect, and what it can’t do.
Integrations are a different thing from the vendor connectors on the
same Connections page. Vendor connectors let agents read findings from security scanners. Integrations let
agents act in your team’s collaboration and tracking apps.
How it works
One connection per app, per organization. An organization admin connects the app once, and the connection is shared by everyone in the organization. There is nothing to configure per agent or per workflow — once an app is connected, its tools are offered to every agent that runs, in chat and in workflows alike. Agents act as a bot account you own. You create a dedicated account for Amplify in the app — anamplify-agent@yourcompany.com, say — and authorize that account when you connect. Everything agents do
is attributed to it, and its permissions in the app bound what agents can reach. See
the bot account for how to set one up.
Tools are named after the app. Every integration tool is named <App>_<Action> — Jira_CreateIssue,
Slack_GetThreadMessages, Notion_SearchByTitle. That’s the name you use in an agent’s
allowed-tools. See
using integration tools in an agent.
Nothing destructive is exposed. No integration tool deletes, removes, archives, or trashes anything, in any
app. The toolset for each app is a fixed, curated allowlist — agents cannot reach an app’s other API surface,
and Console’s own tools can’t be used to call the app’s API directly either.
What agents see
An agent only ever sees the tools for apps that are connected. There is no “connect Slack” prompt in the middle of a run — if Slack isn’t connected, the Slack tools simply aren’t there, and an agent asked to post to Slack will say it has no way to. If a connection stops working mid-run, the agent is told and moves on rather than stalling:
Each tool call is given 60 seconds, and a result longer than 16,000 characters is truncated with a note
saying so.
Where integrations are available
Next steps
Connect an app
The bot account, the connect flow, and disconnecting.
Use integration tools in an agent
Grant tools, and add a Slack or Jira step to a workflow.