Developer Tools · Integration
GraphQL
Add GraphQL to your product for your customers, and give your AI agents governed access to it.
Embed a GraphQL integration so your customers can point your product at their own endpoint instead of asking you to build a bespoke connector for their internal API. Schemas differ per customer, so the queries, mutations, and variables you use are configuration rather than code, and introspection lets your product discover what an endpoint actually exposes. fastn handles per-customer credentials, retries, and pagination.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own GraphQL endpoint so your product reads their data without a custom build.
Introspect a schema at runtime so your product shows the types and fields a customer's endpoint exposes.
Run parameterised queries and mutations per tenant, with credentials held per customer.
Map a customer's response shape to the fields your product expects, as configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent introspects a schema before deciding which query to run.
An agent runs a read-only query to ground an answer in the customer's own data.
An agent executes a mutation within governed permissions, with each call logged.
Example prompt
Introspect this endpoint, then query the ten most recently created records and show the fields available on them.
Set up GraphQL in 4 steps
- 01Open the GraphQL connector from your fastn dashboard.
- 02Have each customer supply their own endpoint URL and credentials.
- 03Define the queries and mutations your product uses and map the response fields, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the GraphQL integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a GraphQL integration without building it. Your customers point it at their own endpoint and credentials and work their services, builds and deployments through it, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a GraphQL update is not your on-call problem.
- One integration serves your product and your agents. The same governed GraphQL connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitHubWorks well with
PostgreSQL
SnowflakeOften used alongside
Tools the same teams tend to run next to GraphQL, across other categories.
Slack
Airtable
Anthropic Claude
ServiceNowGraphQL integration FAQ
How do I add a GraphQL integration to my product?
Enable the GraphQL connector in your fastn dashboard, then let each customer authenticate their own GraphQL account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no GraphQL client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is a GraphQL connection configured per customer?
GraphQL is a specification rather than a service you sign up for, so there is no GraphQL account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own services, builds and deployments. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this GraphQL integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent introspects a schema before deciding which query to run.
Who maintains the GraphQL integration?
fastn does. When GraphQL changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to GraphQL events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in GraphQL?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the GraphQL integration?
A common starting point: connect their own GraphQL endpoint so your product reads their data without a custom build. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the GraphQL integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding GraphQL does not change your per-connector cost. You can start free with 3 connected accounts.
Add GraphQL to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.