Add preflight validation before generation starts
Johnathan Lightfoot
It would be helpful to validate a generation request before credits are used. A dry-run or validation endpoint could check whether the request is likely to succeed.
The validation could return estimated credits, estimated generation time, card count warnings, invalid theme or folder IDs, unreachable image URLs, template issues, and unsupported export options.
This would help builders catch problems before starting the generation.
Nik Payne (Gamma design)
Hey Johnathan Lightfoot, this is a really thoughtful request, thank you. Preflight validation before credits get burned (with estimates + warnings like bad IDs/URLs/export options) makes a ton of sense, I’ll pass this to the team.
Quick question so we scope it right: in your workflow, what’s the most common “oops” you’d want the preflight to catch before you hit generate (ex: invalid folder/theme IDs, unreachable image URLs, or something else)?
Johnathan Lightfoot
Nik Payne (Gamma design) For me, the most common "oops" preflight should catch is bad or incomplete upstream data before generation kicks off.
In n8n, the input is usually coming from Airtable, a form submission, a database row, or an AI-generated brief. So the request technically exists, but the important fields are missing, empty, malformed, or just too thin to make a decent deck.
Nik Payne (Gamma design)
Johnathan Lightfoot: Thank you!