Integrations connect Kluff to the tools you already use: Slack, GitHub, CRMs, spreadsheets, and the rest of your stack. Once a connection is in the workspace, you choose which projects may use it, and agents and flows can act there instead of making you copy-paste between apps.
The public catalog of what you can connect is on the Integrations page. Tools that publish an MCP server can also be added that way; see MCP.
Connect a tool
- Open Integrations in the left icon strip.
- Pick a tool and complete the sign-in or API setup it asks for.
- Decide who the connection is for (you, a team, or the workspace) when the tool offers sharing.
- Back in a project, open Tools in the sidebar and enable the integration for that project.
An integration that isn't turned on for a project won't be used by that project's agents, even if someone else in the workspace connected it.
Project tool profiles
Each project has its own tool list. That's how you keep a customer-data integration off a public-docs project, or give only the support project access to the helpdesk.
For each enabled tool you can usually choose:
- Automatic: the agent may use it as part of the task
- Ask first: the agent pauses for approval before it acts
Start with ask-first on anything that sends mail, changes records, or touches production. Loosen it once you trust the workflow.
What agents do with integrations
With a tool enabled, you can ask an agent to look up an account, file a ticket, read a channel, or draft from a doc. The agent still explains what it did; for changing actions you should see an approval or an artifact you can review.
Skills package integrations together with instructions and templates so you don't re-explain the same setup on every thread.

