Integrations · GitLab GraphQL
A Guild agent can query and mutate any GitLab.com data through the GraphQL API, using a personal access token you connect once. Guild injects the token server-side so agent code never sees it, and credential policies let you restrict what each agent can reach before any request leaves Guild.
Book a demo
See how teams govern agents that use GitLab GraphQL.
Talk to sales
Get access to Guild, then connect GitLab GraphQL to your first agent.
What the GitLab GraphQL integration exposes
The integration provides a single tool,gitlab_graphql_graphql_query, which sends one GraphQL document to the GitLab.com GraphQL API. The tool supports both queries and mutations, so an agent can retrieve or modify GitLab data in one call. Tools are prefixed gitlab_graphql_ and you can use pick() to include only the ones your agent needs.
How it works
1
Open credentials settings
In Guild, go to Access & setup > Credentials and click Connect. Select gitlab-graphql from the list.
2
Paste your access token
Paste your GitLab personal access token into the API Key field. Guild stores it and sends it as a bearer token in the
Authorization header on every request.3
Scope the credential
Choose account, workspace, member, or agent scope. See Credentials for the full scope options and how Guild resolves which credential an agent uses.
Why GitLab GraphQL access needs governing
GitLab GraphQL mutations can create, update, or delete data across projects, issues, merge requests, and more. A single tool that accepts any GraphQL document gives an agent broad reach, so limiting what it can do matters. Credential policies let you write ALLOW and DENY rules that Guild’s credential proxy enforces before any request reaches GitLab. You can restrict by operation name, HTTP method, agent, or workspace, and a matching DENY rule always wins over any ALLOW rule. Guild injects the personal access token server-side only after the policy check passes. The token never enters the agent’s code, container, prompt, or state. You can scope the credential to a single agent or workspace so it never serves other workspaces. For details on how Guild chooses which credential to use and how the proxy works, see Credentials and Credential policies.About the GitLab GraphQL integration
This integration gives agents access to the GitLab.com GraphQL API through a single tool. Agents can send any GraphQL query or mutation to retrieve or modify GitLab data. A personal access token is required to authenticate requests. The integration isguildai~gitlab-graphql.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect GitLab GraphQL
In Guild, go to Access & setup > Credentials, click Connect, select gitlab-graphql, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thegitlab_graphql_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~gitlab-graphql:
Frequently asked questions
Can I run GraphQL mutations, not just queries?
Can I run GraphQL mutations, not just queries?
Yes. The
gitlab_graphql_graphql_query tool sends any GraphQL document, so agents can run mutations to modify GitLab data as well as queries to retrieve it.Does my agent ever see the personal access token?
Does my agent ever see the personal access token?
No. Guild stores the token and adds it to requests server-side as a bearer token. The token never enters the agent’s code, container, prompt, or state.
Can I limit which operations this agent is allowed to run?
Can I limit which operations this agent is allowed to run?
Yes. Credential policies let you write ALLOW and DENY rules scoped to specific agents, workspaces, or HTTP methods. The proxy enforces them before any request reaches GitLab.
Does this integration support webhook events from GitLab?
Does this integration support webhook events from GitLab?
Not yet. The catalog entry for
guildai~gitlab-graphql lists no webhook events, so event-driven triggers from GitLab are not available through this integration.Put a governed agent on GitLab GraphQL this week
Book a demo
See how teams govern agents that use GitLab GraphQL.
Talk to sales
Get access to Guild, then connect GitLab GraphQL to your first agent.