Integration tools in Chat

Chat automatically gains the tools of every integration your organization installs — search them, run them, and stay in control with per-action confirmation.

Chat's capabilities grow with your organization. Install an integration — Slack, GitHub, a CRM, or any custom integration from a pack — and Chat can use that integration's tools the same day, with no extra configuration.

Integration tools appear in Chat only when your organization has at least one enabled integration. Enable integrations under Settings → Integrations.

How it works

Instead of loading every integration tool into the conversation up front, Chat uses two built-in helpers:

Tool search — when you ask for something an integration can do ("send a Slack message to #ops", "create a GitHub issue"), Chat searches your organization's installed integration tools and finds the best match, including the exact parameters the tool accepts.
Tool run — Chat fills in the parameters and asks you to confirm before executing. Integration tools can have real side effects (messages sent, records created), so every run requires your explicit approval in the chat panel.

This keeps conversations fast no matter how many integrations are installed — Chat only pulls in the details of the tools it actually needs.

What you'll see

Ask naturally. "Post the deployment summary to #releases in Slack."

Chat finds the tool. It searches your installed integrations and picks the matching tool — here, Slack's Send Message.

Confirm the action. Chat shows what it is about to run and waits for your approval before anything executes.

See the result. The tool's output streams back into the conversation.

Connections and credentials

A tool may show as setup required when the integration is installed but the workspace has no usable connection yet:

OAuth integrations (e.g. Slack, GitHub with user sign-in) need you to connect your account under Settings → Integrations.
API-key integrations need a workspace credential configured by a workspace admin.

Credentials never pass through the conversation — execution happens on the platform with the connection your organization configured, under the same governance (policies, data-loss prevention, audit) as workflow execution.

Governance

Integration tool runs from Chat follow the exact same rules as running the tool inside a workflow:

Organization integration policies (allowed capabilities, blocked vendors) apply.
Data-loss-prevention scanning and pre-action policies apply.
Every run is attributed to you in the audit trail.

If a tool is blocked by policy, Chat tells you why instead of executing it.

Troubleshooting

Symptom	Likely cause
Chat says no matching tool exists	The integration isn't installed or enabled for your organization
Tool found, but the run fails asking for an API key	The workspace has no connection for that integration — configure one under Settings → Integrations
Chat never offers integration tools	Your organization has no enabled integrations yet