Two separate things going on here, and only one is actually on Gamma's side. The rest is Zapier formatting. 1) The real fix for "people can't view it": use link sharing, not email invites. There is a public view option, but it's the External Access field, not Email Recipients. The difference:
Email Recipients = per-person invitations tied to a specific email. That person has to sign into Gamma as that exact address. That's why dgermino@gmail.com hit the "wrong account / sign up" screen. The browser was signed in as syykus@gmail.com.
External Access = view = anyone with the link can open it, no Gamma account or sign-in needed. This is what you actually want.
The "view" in your screenshot is set on Email Recipients Access Level, which is a different field than External Access. That's the mix-up. Recommended setup in your Create Generation step:
Set External Access = view
Leave Email Recipients blank (clear every email field)
Keep your final Send Outbound Email step to email the gammaUrl (from Get Generation Status) back to the sender + CC
That clears the access problem, the validation error, and the "it's required" error all at once. ⚠️ One caveat: if your workspace's sharing settings restrict external links, Gamma will quietly ignore External Access. If view links still don't work after this, check Settings → Sharing. 2) If you do want named email invites, the validation error is a Zapier formatting issue. Gamma needs each recipient to be a bare email address. Zapier is sending Damien Germino <dgermino@gmail.com> (name + brackets) from the CC field, which fails. Your successful run sent just syykus@gmail.com. The fix: add a Formatter by Zapier → Text → Extract Email Address step on the CC value before the Gamma step, then map the cleaned result into Recipients. Extract Email Address pulls one address; for multiple CCs, use Extract Pattern with an email regex. Quick answers to your other points:
No completion email to you as the owner: expected. The API doesn't notify the owner. Get Generation Status → gammaUrl plus an email-to-self step is the way to get that signal.
"Token passed as the sender email": same class of issue. That field is mapping a non-email value. Run it through the same Formatter step. If it persists, send me that run's exact From Email value.
PDF export: sounds like your multi-step zap already handles it. Export As = pdf just produces exportUrl on Get Generation Status. It never auto-emails.
If link-view still fails after step 1, send me the generationId and gammaUrl and I'll check whether workspace sharing settings are stripping External Access.
Hi Damien, thanks for the detail and screenshots. A couple things stand out. The “Wrong account” screen is likely expected if the invitation email was sent to one address, but the browser is signed into Gamma with a different address. In your screenshot, the invite appears to be for dgermino@gmail.com, while the browser was signed in as syykus@gmail.com. Gamma invitation links are tied to the invited email, so that mismatch would trigger the wrong-account page even if the access level is set to view. The validation error looks separate. Zapier appears to be passing a non-email value into the Email Recipients field, likely from the CC field when it has no data. Gamma requires every value in emailOptions.recipients to be a valid email address, so if Zapier sends something like No data, the API rejects it. For the PDF export: setting Export As = pdf does not email the PDF automatically. It tells Gamma to generate an export file. You would then use the “Get Generation Status” step to retrieve the exportUrl after the generation completes, and map that URL into a later email or storage step if you want to send/download it. Could you send one Zap run/task history link for a failed run and one run where the invite was created? The most helpful fields would be the exact Email Recipients value Zapier sent, the generationId, and the completed gammaUrl. That should let us confirm whether this is just Zap field mapping or something unexpected in the Gamma share behavior.
Hi Gregory this is great feedback! Would you mind sharing in Ideas & Requests?
Good callout ,we just shipped a server-side fix for the underlying pagination issue. For direct HTTP calls, try again after the next server release and make sure you keep looping while `hasMore` is true, passing `nextCursor` back as the `after` query param. We’re also adding a `type=custom` filter for `GET /v1.0/themes`, which should make this easier if you only need custom themes. The community n8n node may still need to be updated separately to take advantage of this, so the HTTP node will be the best way to verify the fix first.
Hi Luiza 👋 The Gamma itself should still be there, but the exportUrl for the PDF is temporary and expires after about 7 days. So for older presentations, it’s normal for the original PDF link to stop working even though the Gamma still exists. The fix is to re-export the file from Gamma, which will generate a fresh PDF. If you need the PDF to stay available long-term in Zapier, I’d recommend downloading/storing the file as soon as the generation finishes instead of relying on the original exportUrl later. Docs: https://developers.gamma.app/docs/
I pulled the trace for that generation. You're doing nothing wrong. The model received your instructions correctly and ignored them -- it saw the SWOT input and output an infographic instead of the text grid you asked for. Your setup is solid, this is just a gap in how additionalInstructions works today. I am going to flag this with the team but I want to set expectations clearly that I can't guarantee if or when this will be addressed specifically but as always we appreciate your feedback.
Hey Dan can you give me more context on what you would like me to debug exactly?
Hi Julio you can make requests for further flexibility and bulk pricing in Ideas & Requests but I dont have any other self serve pricing model to offer you at this time. If you believe your organization's usage will scale continuously you may want to reach out to our sales team for further inquiries.
Hey Julio! 👋 On the pricing question: Ultra is our highest self-serve plan, and we don't offer volume discounts on credits at this tier, so there isn't a way to get a better per-credit rate by upping the subscription right now. For the top-up pain you mentioned, the best workaround is auto-recharge, it'll add credits automatically before you hit zero, so you don't get stuck mid-generation paying the one-off top-up rate.
Open Workspace Settings (top-left menu)
Go to the Billing tab
Click Enable Auto-Recharge
Set your threshold (e.g. recharge when you drop below 2,000 credits) and the amount to add each time
Full walkthrough with a GIF: https://help.gamma.app/en/articles/12466653-how-do-i-purchase-more-credits I'll pass your volume feedback along to the team ,useful signal as we think about higher-tier options for API customers. Let me know if you run into trouble finding it.
%20(1).png){kind=avatar}