Introduction
Connectors let Gamma's AI use content from the tools you already work in, such as Notion, Slack, Granola, and Linear, as source material when generating or editing a gamma. We're regularly adding new connectors, so check the product for the latest list.
Getting set up takes three steps: an admin enables connectors for the workspace, each member connects their own accounts, and then anyone can reference them in the AI agent.
🔷 Note: This article covers inbound connectors - connecting your other tools into Gamma so its AI agent can use them as context while you create. If instead you want to create gammas from inside another tool (ChatGPT, Claude, Glean, Atlassian, or automation platforms like Zapier), that's an outbound connector.
➡️ How do I use Gamma with outbound connectors?
Available inbound connectors
Gamma supports inbound connectors for many popular tools, including Notion, Slack, Granola, HubSpot, Linear, Atlassian, Stripe, and more. We're regularly adding new connectors, so check My connectors in the product for the latest list.
Step 1: Connect your accounts
Each person connects their own accounts. Your connections are personal to you - connecting an account doesn't give other members access to your data.
Go to My connectors (gamma.app/settings/my-connectors).
Find the connector and select Connect.
A secure popup opens for you to sign in and authorize access. Once it finishes, the connector shows a Connected badge with the account you linked.
From the three-dot menu (…) next to a connected account you can open About this connector (to review exactly what Gamma can read) or Disconnect at any time.
Step 2: Use connectors with the AI agent
After connecting an account, open the Connectors menu in the AI agent (available both when generating a new gamma and when editing an existing one), select the sources you want, and ask in natural language. The agent only uses connectors you've connected, and only reads a source when you reference it.
Some examples:
Sales / QBR deck: "Build a quarterly business review deck for Acme using their HubSpot deals and the latest Fathom call summaries."
Customer success: "Create a renewal-risk one-pager for Acme from their HubSpot account activity and recent Slack threads in #acme."
Marketing / product launch: "Turn this Notion PRD and the linked Linear project into a launch announcement deck for the GTM team."
Exec / ops weekly update: "Summarize this week's revenue and subscription changes from Stripe into a business-review update."
Developer / sprint recap: "Make a sprint recap report from my team's work in Linear - group it by completed issues, in-progress work, and carryover."
Admin controls (Enterprise)
On the Enterprise plan, workspace admins can control which connectors are available in their workspace.
Go to Workspace settings > Sharing (gamma.app/settings/sharing).
Find the Workspace connectors section.
Use the main switch to allow or block connectors for the workspace, then toggle individual connectors on or off.
🔷 Note: Turning a connector off blocks new connections and disconnects existing accounts in the workspace, so you'll be asked to confirm before disabling.
What Gamma can access
Connectors are designed to be read-only and minimal:
Read-only. Gamma never writes to, deletes from, or shares content from a connected tool.
Only what you can already see, enforced by delegated access, not a Gamma service account.
Gamma can only read what your own account in that tool can read: the channels you're in, the files you can open, the records you have rights to.
Each connection uses the OAuth 2.0 authorization-code flow with PKCE (per-user, per-workspace), so Gamma acts strictly as the connecting user via delegated authorization. There is no shared service account or elevated integration identity - every request to the provider carries that user's own access token, so the provider's native authorization model (its RBAC / ACLs / sharing rules) is the enforcement point.
Gamma cannot see anything the user couldn't, and cannot escalate privileges across users or workspaces.
Read-only by design. Every connector is configured read-only with an explicit allowlist of read tools, filtered by each tool's read-only annotation. Write, update, and delete operations are never exposed to the Gamma agent.
Least-privilege scopes. Only read scopes are requested at consent; granted scopes are recorded per connection.
Encryption at rest. Access and refresh tokens are encrypted before being stored and are never returned to the client.
Admin governance. Workspace admins allowlist which connectors are permitted; disabling a connector immediately disconnects all linked accounts org-wide.
Token lifecycle. Tokens refresh server-side; on expiry or revocation the connection drops to an error state and the user must explicitly re-consent.
Only when referenced. Content is pulled in only when you reference that source while generating or editing, not in the background.
Pricing & credits
Connecting and managing connectors is free. Generating or editing with the AI agent uses credits as usual; referencing a connector doesn't cost anything extra. In other words, you pay the same per-slide / per-image / per-edit credits you'd pay for that generation or edit anyway. Pulling in context from a connector adds no separate charge, and the connector tool calls themselves aren't metered.
FAQs & Common Issues
A connector isn't in My connectors.
We may not support that tool yet - we're regularly adding new connectors, so check back soon.
If you're in an Enterprise workspace, your admin may have disabled it. Ask them to enable it in Sharing settings.
I'm seeing the message "Not enabled in your workspace". Why?
Your workspace is on the Enterprise plan and an admin has not enabled this connector. Ask a workspace admin to enable it in Sharing settings.
I'm seeing the message "Permissions not granted". Why?
The sign-in finished without granting the access Gamma needs. Select Try again and approve the requested permissions.
I'm seeing the message "Session expired". Why?
Your authorization expired. Select Reconnect to sign in again.
I'm seeing the message "Last fetch failed". Why?
A recent sync didn't complete. Select Details for more, then try again.
I need to use outbound connectors with Gamma, not inbound.
This is also possible! Learn about outbound connectors here: