How integrations work
- An admin connects a service in Access & setup > Credentials on an organization, or you connect it on your personal account
- The credential becomes available to every workspace the account owns. Workspaces, members, and individual agents can also have their own — see Credentials
- Agents use service tools (e.g.
gitHubTools) to interact with the connected service - Guild’s credential proxy adds authentication server-side, so agents never see the credential
Browse integrations
See the Integrations directory for the full catalog of connected services — GitHub, Slack, Jira, and many more — organized by category, each with setup details and the tools it provides. The Agent Hub also lists integrations other people have published. See Browse integrations on the Agent Hub. Don’t see what you need? You can create your own integration for any HTTP-accessible service.Using integrations in agents
Import the service’s tool set and spread it into your agent’stools object:
Requesting credentials at runtime
If an agent needs a credential that hasn’t been connected, it can request one usingguildTools:
Related pages
- Credential policies for limiting what agents can do with a connected credential
- Agent SDK tool sets for giving integration tools to agent code
- Event triggers for running agents on events from a connected service
- Create an integration for a service Guild doesn’t cover yet