How Certifier integrates with Formstack
Formstack-Certifier integration works via Google Sheets: every form submission automatically adds a new row to your connected sheet, and Certifier detects that row to issue a credential.
Quick column mapping ensures that the correct information is displayed on the certificate. You can map questions from your forms to specific columns, so important details like recipient name, title, and date are all applied to the credential before it's issued and delivered.
Certifier to Formstack workflows
Available workflows (1)
Setup steps
- 1
In Formstack, start from an empty form and add two required fields: Recipient Name and Recipient Email.
- 2
From the form's Integrations tab, add Google Sheets and link it to a fresh spreadsheet for the responses.
- 3
In Certifier, design and publish the credential template you'll be issuing.
- 4
Under Integrations, create a new automation, choose the Formstack template, and connect it via Google Sheets.
- 5
Set the trigger to watch that sheet for new rows, then configure the Issue Credential action — mapping columns to name, email, and any other fields you want on the credential.
- 6
Save and activate, name your automation, then submit a test form response to confirm the credential issues are addressed correctly.
Resources and manuals
Certifier has native forms now
Collect responses and issue certificates in one place.
Key benefits
Automated issuance from Formstack
Whether Formstack sends 10 responses a week or 500 in a day, Certifier processes each row as it arrives — you don't need to batch, schedule, or manually trigger anything.
Instantly shareable
Recipients can show off what they earned the same day they earn it — post it to LinkedIn or add it to their profile's Licenses & Certifications, with nothing to design, export, or figure out on their own.
Quick setup
For Certifier-Formstack integration, you don’t need developers or third-party connectors. Pick a template, map your columns, and the automation is live – all in under 10 minutes.
Is this integration right for you?
If submitting a form is what should earn someone a credential, this integration is for you.
Training and L&D teams
When a Formstack quiz or completion form gets submitted, the credential goes out the same day — no waiting for someone to compile a spreadsheet and issue a batch at the end of the week.
Events and webinars
Turn a Formstack check-in or feedback form into the trigger for attendance certificates, so every attendee has their credential before they leave the session.
Online course creators
Connect a module-completion form to Certifier once, and every student who finishes gets their certificate automatically, whether one enrolls or a hundred.
Frequently asked questions
Yes, the integration itself is free on every Certifier plan. What varies by plan is how many credentials you can issue (up to 250 credentials/year on the Starter plan).
No. Recipients never log into Certifier or create an account to get their credentials. They fill out your Formstack form as usual, and once the certifier issues the credential, it arrives by email with a link that takes recipients to their credentials. There, they can verify certificates or badges, download, and share them.
Yes. Recipient Name and Recipient Email are the only two fields Certifier requires to issue a credential, but you're not limited to them.
Any other question on your Formstack form — a course name, a completion date, a score, a job title — can flow into its own column in the connected spreadsheet and get mapped onto the credential template during setup. If you want a field on the certificate, add a column for it before you activate the automation, since columns can't be rearranged or added after activation without breaking the mapping.
That row won't turn into an issued credential. Certifier needs a validly formatted email address to deliver a credential, so a blank field or a typo (missing "@", a cut-off domain, and so on) causes that row to be skipped rather than processed with bad data.
Typically, a few minutes from the moment a row lands in your spreadsheet to the moment the credential goes out — it isn't instantaneous, but it isn't a manual queue either. The bigger factor to plan around isn't speed, it's timing your own actions: avoid adding, deleting, or reordering rows while a submission is still being processed, since that's what causes duplicate or skipped credentials, not the processing time itself.
