AI & Models · Integration
Gamma
Add Gamma to your product for your customers, and give your AI agents governed access to it.
Gamma's public Generate API sits at public-api.gamma.app/v0.2/generations and takes an X-API-KEY header, and it is a generation surface only: there is no endpoint to list, read or edit the gammas already in a workspace, so it cannot be used as a document store. A POST returns a generationId immediately and you then poll GET /generations/{id} until the status reports completion, at which point you get the gamma URL and any requested export files. The request body drives the whole output: input text, the text mode that decides whether Gamma rewrites or preserves your wording, the format (presentation, document or social), card count and theme, all of which are fixed at submission and cannot be changed afterwards through the API. Generation consumes the account's credit allowance rather than counting requests, so quota errors show up as spent credits rather than rate limiting, and long inputs cost more. Access is tied to paid plan tiers, so a customer's key may authenticate and still be refused generation. fastn keeps each customer's API key, tracks the asynchronous job through to its finished URL, and handles the upkeep as the beta API version moves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Gamma workspace so decks generated from your product land in their account, not yours.
Turn a quarterly report your product already assembles into a presentation the customer can open and edit in Gamma.
Generate a branded onboarding document per new client using the customer's own Gamma theme.
Queue a batch of generations and surface the finished gamma links back in your app once each job completes.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent draft a deck outline, submit it to Gamma and return the link, with each generation audited per tenant.
Let an agent regenerate a document in a different format while the credit spend stays attributed to the right customer.
Allow an agent to check the status of pending generations and report which ones failed.
Example prompt
Turn last month's account summary into a ten card Gamma presentation using our standard theme.
Set up Gamma in 4 steps
- 01Enable the Gamma connector from your fastn dashboard.
- 02Have each customer authorise their own Gamma account, so calls run under their credentials rather than a shared key.
- 03Decide which models, requests and outputs your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Gamma integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Gamma integration without building it. Your customers connect their own Gamma account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Gamma update is not your on-call problem.
- One integration serves your product and your agents. The same governed Gamma connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
Anthropic Claude
OpenAI
Azure OpenAIOften used alongside
Tools the same teams tend to run next to Gamma, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeGamma integration FAQ
How do I add a Gamma integration to my product?
Enable the Gamma connector in your fastn dashboard, then let each customer authenticate their own Gamma account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Gamma client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Gamma account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Gamma account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Gamma integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent draft a deck outline, submit it to Gamma and return the link, with each generation audited per tenant.
Who maintains the Gamma integration?
fastn does. When Gamma 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.
Whose Gamma API key and quota does each call use?
Each customer authorises their own Gamma account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the Gamma integration?
A common starting point: let a customer connect their own Gamma workspace so decks generated from your product land in their account, not yours. 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 Gamma integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Gamma does not change your per-connector cost. You can start free with 3 connected accounts.
Add Gamma to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.