Connect Alloy to the tools your business runs on

Alloy is not meant to replace every system your company already uses. It connects to those systems so AI teammates can help where work already happens.

Use integrations to connect CRMs, support tools, databases, internal APIs, email, documents, project systems, and other operational tools.

MCP servers are registered at the organization level and can be enabled for specific AI teammates. That gives teams a practical way to decide which teammate can use which connected tool.

Teams can add an MCP server, test the connection, and assign it to the AI teammates that need it for their work.

Alloy workflows can call tools, run code, send messages, ask for user input, call AI teammates, and finish with a clear result.

Runtime tools can help AI teammates check URLs, make HTTP requests, update contacts, escalate conversations, use storage, schedule work, run code, or call another teammate when those tools are enabled.

Variables and secrets let teams reuse configuration and credentials in URLs, headers, and workflow steps. Secret values stay masked in the Alloy interface and exports.

This keeps integration setup easier to manage than hard-coding credentials into every workflow.

The private API lets approved external systems use organization-scoped API keys to work with Alloy storage and trigger workflows.

Use this when a product, backend service, or automation needs to start work in Alloy without a person manually opening the workspace.

Current integration examples include searching Gmail, finding email contacts, creating Gmail drafts, creating Google Drive files, and creating Jira Data Center issues.

These examples show the pattern: connect to the outside system, pass approved inputs, complete a specific task, and return a useful result to the workflow or AI teammate.