If you're running webinars, workshops, or short courses, there's a good chance attendance or feedback already flows through a Google Form. The response sits in a linked Google Sheet the moment someone submits — which means the data you need to issue certificates already exists, updated in real time, before you've done anything at all.
The usual workflow looks like this: the form closes, someone opens the linked Sheet, copies the names and emails into a fresh CSV, uploads it to a certificate tool, and sends everything in one batch — hours or days after the event actually happened.
That gap is the problem. A certificate that arrives a week after a workshop feels like an afterthought. One that arrives the same day feels like part of the event.
Every Google Form writes its responses into a linked Google Sheet automatically — that behaviour is built into Forms itself, not something you configure. SuTan connects to that same Sheet directly, using the published-CSV link Google Sheets already provides under File → Share → Publish to web.
From there, SuTan checks the Sheet on a schedule, compares the current row count against what it saw last time, and treats any new rows as new certificates to issue. No polling every response individually, no webhook to configure on the Forms side — the Sheet is the only thing SuTan ever needs to look at.
Worth being upfront about: generating and downloading certificates from a Sheet works on the free plan, up to 20 per batch, as a print-ready PDF. Actually emailing each recipient their certificate — the part that makes this genuinely hands-off — needs a paid plan, since delivery goes out through your own Gmail or SMTP account rather than a shared sender.
That's a deliberate line, not a limitation dressed up as a feature: email deliverability depends on reputation, and reputation depends on whose mailbox is actually sending. Free tools that promise unlimited automated sending from a shared address usually pay for that promise in spam-folder placement.