Integrations connect Guild to the external services your team uses — GitHub, Slack, Jira, and more. Once connected, agents can use these services through their tool sets.Documentation Index
Fetch the complete documentation index at: https://docs.guild.ai/llms.txt
Use this file to discover all available pages before exploring further.
How integrations work
- An admin connects a service at the organization level via Settings > Credentials
- The integration becomes available to all workspaces in the organization
- Agents use service tools (e.g.
gitHubTools,slackTools) to interact with the connected service - Authentication is handled automatically by the runtime
Integration Hub
| Integration | Category | Tools package |
|---|---|---|
| GitHub | Code & CI/CD | @guildai-services/guildai~github |
| Azure DevOps | Code & CI/CD | @guildai-services/guildai~azure-devops |
| Bitbucket | Code & CI/CD | @guildai-services/guildai~bitbucket |
| Slack | Communication | @guildai-services/guildai~slack |
| Jira | Project management | @guildai-services/guildai~jira |
| Confluence | Productivity | @guildai-services/guildai~confluence |
| Figma | Productivity | @guildai-services/guildai~figma |
| New Relic | Monitoring | @guildai-services/guildai~newrelic |
| Cypress | Testing | @guildai-services/guildai~cypress |
| TestRail | Testing | @guildai-services/guildai~testrail |
| Pipedream | Automation | @guildai-services/guildai~pipedream |
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: