Skip to content
Start in the sandboxStart free
All connectors
Gamma logo

Gamma

Content creation & media

Move briefs, assets and sign-offs through Gamma without chasing between tools.

14 ways to read, 5 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Gamma with Nexra

Connected, approved, proven.

The things teams do most with Gamma, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Export gammaApproval by rule
  • Generate with the Gamma agentApproval by rule
  • List card analyticsRead

Example flow

  1. Gamma · List card analyticsDone
  2. Gamma · Export gammaNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Gamma.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Gamma
  • Gamma's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Generate Gamma presentations, documents, social posts and images from text or templates, track jobs and exports, and read gammas, themes, folders, comments and engagement analytics.

Gamma Tech, Inc. API docs
Source actions
14
Destination actions
5
Data types
13

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Agent generations2
  • Generate with the Gamma agentDestinationNot retried automaticallyApproval before production

    Start an agent-driven generation from a brief, optionally starting from a template or existing Gamma. Poll agent_generations.get.

  • Get agent generationSource

    Status, Gamma ID and URL, and credits used for an agent generation job.

Analytics1
  • Get gamma analyticsSource

    Views, unique viewers and editors, card count, last opened and a 30-day daily breakdown.

Card analytics1
  • List card analyticsSource

    View time and viewer reach for every card in a Gamma.

Comments1
  • List commentsSourceIncremental

    Comment threads with replies on one Gamma.

Exports2
  • Export gammaDestinationNot retried automaticallyApproval before production

    Start an asynchronous export of an existing Gamma to PDF, PPTX or PNG. Poll exports.get for status.

  • Get exportSource

    Status of an export job started with exports.create.

Folders1
  • List foldersSource

    Folders the key owner is a member of, for use as folderId.

Gammas2
  • Get gammaSource

    Title, type, URL, thumbnail, author, theme and timestamps for one Gamma.

  • Search gammasSourceIncremental

    Full-text search over gammas the key owner can access, with author and last-updated filters.

Generations2
  • Generate from textDestinationNot retried automaticallyApproval before production

    Start an asynchronous generation of a presentation, document, webpage or social post from text. Poll generations.get for the result.

  • Get generationSource

    Status, Gamma ID and URL, and credits used for a generation job.

Images2
  • Generate imageDestinationNot retried automaticallyApproval before production

    Start an asynchronous on-brand image generation from a prompt. Poll images.get for the image.

  • Get image generationSource

    Status, image URL, size and media library ID for an image generation job.

Template generations1
  • Generate from templateDestinationNot retried automaticallyApproval before production

    Start an asynchronous generation that adapts a one-page workspace template Gamma to a prompt. Poll generations.get for the result.

Templates1
  • Search templatesSource

    Workspace templates (usable with template_generations.generate) and official Gamma explore templates.

Themes1
  • List themesSource

    Standard and custom workspace themes, for use as themeId.

Viewer analytics2
  • Get viewer analyticsSource

    One authenticated viewer's engagement with per-card time share.

  • List viewer analyticsSource

    Per-viewer engagement: name, email, last opened and cards viewed.

Access and limits

Authentication
Gamma API key
Plans and access
API keys are available on Gamma Pro, Ultra, Teams and Business plans. Generation spends the workspace's Gamma credits. Gamma search is rolling out gradually and returns HTTP 403 until enabled for the workspace. Analytics need edit permission on the Gamma (manage permission for all viewers).
Test environment
Gamma has no sandbox. Use a test workspace with limited credits and read operations to validate a connection.
Rate limits
Gamma applies burst, hourly and daily request limits reported in x-ratelimit-* headers and returns HTTP 429 when exceeded. Nexra honours Retry-After and backs off on reads; generations are never retried.
Pagination
Themes, folders, comments and viewer analytics use cursor pagination (limit, after, nextCursor, hasMore). Gamma and template search return up to 25 hits in a single page.
Provider events
Gamma does not document webhooks; generation, image and export jobs are polled with their status endpoints. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Generation (from text, from a template, by the agent) and image generation spend Gamma credits. They are marked billable and are never retried automatically.
  • Nexra never deletes or archives gammas or media, never runs agent edits on existing gammas, never publishes a Gamma site and never sets external (link) access or email sharing. Generated content is limited to workspace members.
  • Export and generation download links (exportUrl) are bearer links that anyone can use for about a week, so Nexra does not return them; records report exportReady instead. Downloading the exported file is an engine gap; open the Gamma in the app to download it.
  • Generated image CDN URLs are returned as Gamma provides them.
  • The API cannot edit an existing Gamma's content; generate a new one instead.
  • Gamma search (gammas.search) is rolling out gradually and returns HTTP 403 until Gamma enables it for the workspace. It returns at most 25 hits with no further pages; filter by updatedAfter to page through time.
  • Viewer analytics are capped at 500 viewers, update about hourly and include viewer email addresses when the API key user has manage permission.
  • createdBy filters accept 'me' or a Gamma user ID only; email addresses are refused so they never appear in a URL.
  • OAuth (auth.gamma.app with PKCE and rotating refresh tokens) is not offered; connect with a workspace API key.
  • Whether exporting an existing Gamma consumes credits is not documented; exports.create is not retried automatically.

Developer reference

  1. Create the Gamma Tech, Inc. credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Gamma, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Gamma Tech, Inc. docsAPI referenceGamma Tech, Inc. docsAuthenticationGamma Tech, Inc. docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/gamma and the Connections API.