All connectors
Implemented
Content creation & media
Gamma logo

Gamma

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.

Turn CRM, project or report data into on-brand decks and documents automatically, file them in the right folder and follow up on who viewed them.

Source actions

14

Destination actions

5

Data types

13

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

agent generations
  • Generate with the Gamma agent
    Destination
    Not retried automatically
    Approval before production

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

    agent_generations.generate
  • Get agent generation
    Source

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

    agent_generations.get
analytics
  • Get gamma analytics
    Source

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

    analytics.get
card analytics
  • List card analytics
    Source

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

    card_analytics.list
comments
  • List comments
    Source
    Incremental

    Comment threads with replies on one Gamma.

    comments.list
exports
  • Export gamma
    Destination
    Not retried automatically
    Approval before production

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

    exports.create
  • Get export
    Source

    Status of an export job started with exports.create.

    exports.get
folders
  • List folders
    Source

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

    folders.list
gammas
  • Get gamma
    Source

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

    gammas.get
  • Search gammas
    Source
    Incremental

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

    gammas.search
generations
  • Generate from text
    Destination
    Not retried automatically
    Approval before production

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

    generations.generate
  • Get generation
    Source

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

    generations.get
images
  • Generate image
    Destination
    Not retried automatically
    Approval before production

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

    images.generate
  • Get image generation
    Source

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

    images.get
template generations
  • Generate from template
    Destination
    Not retried automatically
    Approval before production

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

    template_generations.generate
templates
  • Search templates
    Source

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

    templates.search
themes
  • List themes
    Source

    Standard and custom workspace themes, for use as themeId.

    themes.list
viewer analytics
  • Get viewer analytics
    Source

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

    viewer_analytics.get
  • List viewer analytics
    Source

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

    viewer_analytics.list

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. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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

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