Gamma helps create beautiful, interactive content and presentations using AI. This integration enables programmatic generation via Gamma’s API.
Gamma helps create beautiful, interactive content and presentations using AI. This integration enables programmatic generation via Gamma’s API. On Nagent, Gamma is exposed as a fully-configurable ai content generation integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Gamma into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Gamma to automate the kinds of tasks ai content generation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Gamma into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Gamma, with input parameters and output schema. Drop these into any step of an agent built in Helix.
GAMMA_CREATE_FROM_TEMPLATETool to create new Gamma content based on an existing template. Use when you need to generate content with a predefined structure/layout by providing custom instructions and prompt. The API creates content asynchronously. This action polls the generation status and returns the gammaUrl when complete, or a generationId if the 2-minute timeout is reached.
Input parameters
Text instructions, image URLs, and guidance for adapting the template. Supports 1-100,000 tokens. Can include content to fill into the template and specific customization instructions.
Unique identifier of the gamma template to use as the base for content generation. This determines the structure and layout of the generated content.
Theme identifier obtained from the List Themes API. Use the 'id' field (e.g., 'chisel', 'alien', 'aurora'), NOT the 'name' field which contains human-readable theme names. If not specified, uses the template's default theme.
Additional export format for the generated content. Options: 'pdf' (static document) or 'pptx' (editable PowerPoint). Download links expire after a period—download promptly.
Array of folder IDs where the generated gamma should be stored. Use List Folders API to get available folder IDs.
Image generation options for template content. Docs: https://developers.gamma.app/docs/image-models
Access control options for the generated content. Docs: https://developers.gamma.app/docs/how-does-the-generations-api-work#sharingoptions
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GAMMA_GENERATE_GAMMAGenerate a Gamma presentation, document, webpage, or social media content using AI. Documentation: https://developers.gamma.app/docs/generate-api-parameters-explained The API creates content asynchronously. Poll the returned generationId to check status.
Input parameters
Output type. 'presentation' (slide deck), 'document' (continuous page/report), 'webpage' (web page), 'social' (Instagram/TikTok/LinkedIn posts). Default: 'presentation'
Visual theme identifier defining color palette and typography. To use the default theme, omit this field entirely — do NOT pass 'default' as a value. IMPORTANT: Theme IDs cannot be guessed - you MUST retrieve them using the List Themes API first. Standard themes use lowercase words ('alien', 'aurora'), hyphens ('default-dark', 'blue-steel'), or alphanumeric IDs ('ag4mc9ggtxi8iyi'). Custom workspace themes use 'theme_' prefix ('theme_abc123xyz'). DO NOT use underscore-separated words like 'corporate_blue' - these are invalid. Both standard (global) and custom (workspace-specific) themes are supported.
Additional download format alongside Gamma URL. 'pdf' (static document) or 'pptx' (editable PowerPoint). Links provided in GET response expire after time—download promptly.
Number of cards to create (when cardSplit='auto'). Pro users: 1-60, Ultra users: 1-75. Default: 10
Content transformation mode. 'generate' (AI expands brief inputs into full content), 'condense' (summarizes long text to fit slides), 'preserve' (keeps exact wording, adds structure).
Card division logic. 'auto' (AI splits into numCards slides, ignores \\n---\\n), 'inputTextBreaks' (splits at each \\n---\\n marker, ignores numCards). Default: 'auto'
Target folder(s) for storing the generated gamma. Retrieve available folder IDs using the List Folders API. Multiple folders can be specified.
Text and image URLs to generate gamma from. Can be brief (few words) or extensive (pages). Token limits: 100,000 tokens (~400,000 characters). Image URLs can be included where they should appear. Use '\\n---\\n' to control card splits.
Card layout options. Docs: https://developers.gamma.app/docs/how-does-the-generations-api-work#cardoptions
Text generation options. Docs: https://developers.gamma.app/docs/how-does-the-generations-api-work#textoptions
Image options for gamma generation. Docs: https://developers.gamma.app/docs/how-does-the-generations-api-work#imageoptions
Sharing and access control options. Docs: https://developers.gamma.app/docs/generate-api-parameters-explained
Extra specifications for content, layouts, etc. Character limits: 1-2000.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GAMMA_GET_GAMMA_FILE_URLSRetrieve generation status and file URLs. Poll this endpoint every ~5 seconds until status is 'completed'. Docs: https://developers.gamma.app/reference/get-generation-status
Input parameters
The generationId obtained from the POST generations endpoint. Must contain only letters and numbers (alphanumeric characters).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GAMMA_LIST_FOLDERSTool to retrieve a paginated list of folders in your Gamma workspace. Use when you need folder IDs to organize generated content or to search for specific folders by name.
Input parameters
Cursor token for fetching the next page. Use the nextCursor value from the previous response. Pagination is forward-only.
Number of items to return per page. Maximum: 50.
Search by name (case-insensitive). Filters results to items matching the search term.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
GAMMA_LIST_THEMESFetch the list of themes available in your workspace. Returns both standard (global) and custom (workspace-specific) themes in a paginated format. Use this to discover available theme IDs and names for use with the Generate API. Filter by name using the query parameter.
Input parameters
Cursor token for pagination. Use the nextCursor value from the previous response to fetch the next page.
Maximum number of themes to return per page. Must be between 1 and 50.
Search themes by name. Filter the list to only themes matching this query string.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 35 agents privately built on Nagent that already use Gamma.
Build on Nagent
Connect Gamma to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Gamma, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Gamma is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Gamma is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Gamma steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Gamma event fires, the agent kicks off automatically.
Every Gamma action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Gamma ships with 5 pre-built ai content generation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Gamma together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Gamma-based workflows tailored to your business.