Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Content and files ]

Gamma integration for your workflows.

Connect Gamma to Collabase once and use 2 actions in your workflows. No code needed, hosted in Switzerland.

Sign-inCustom credentials
CategoryContent and files
UpdatedSeptember 2026
LicenceOpen source (MIT)
Back to the directory

Gamma in Collabase

Connect Gamma to Collabase once and use 2 actions in your workflows. No code needed, hosted in Switzerland.

[ About the service ]

An AI-powered design partner that helps users generate presentations, documents, social media posts, cards, etc., via natural language.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Gamma and connect your account.
  3. Add a trigger or an action to the workflow.
  • Log in to your Gamma account. You must have a Pro or Ultra plan to access the API.
  • Navigate to Settings & Members (click your workspace name in the top-left).
  • Go to the API Key tab.
  • Click Create API key and give it a name (e.g., "Collabase").
  • Copy the key (it starts with sk-gamma-) and paste it below.

[ Content and files ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Gamma

What can I automate with Gamma in Collabase?

Gamma brings 2 actions and 0 triggers, for example Generate Gamma and Get Generation. You combine them in a workflow without code and mix them with every other integration.

How do I connect Gamma to Collabase?

You open the integrations in the workspace settings, choose Gamma and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.

Does the Gamma integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.