Answer capsule: To auto generate certificates from Jotform, connect your Jotform account to CertFusion using a full-access Jotform API key, open the certificate design you want to automate, choose Jotform as the recipient source, select your form, and map the name and email questions to certificate fields. Every new submission then creates a certificate recipient automatically.
If you collect course registrations, webinar sign-ups, or completion confirmations through Jotform, the certificate step is usually where the manual work creeps back in. You export a spreadsheet, tidy the columns, paste names into a certificate tool, and repeat it next month.
You only need to set the connection up once. After that, Jotform hands each submission straight to CertFusion, and your recipient list builds itself.
The whole setup takes about five minutes.
From the CertFusion dashboard, click your account icon in the top right and choose Manage Integrations.

Scroll down the integrations list until you reach Jotform. If you haven't linked it before, it will show as Not connected with a green Connect button.

CertFusion asks for a Jotform API key. This is what lets it read your forms and register the webhook that pushes submissions across.

Leave this dialog open — you'll come back to it in a moment. The View Jotform API key guide link opens Jotform's own instructions if you'd rather follow those.
In a new tab, go to your Jotform account and open My Account → API. If you've never created a key, the API Keys table will be empty.
Click Create New Key.

Jotform generates the key immediately — but note the Permissions column. New keys default to Read Access.

Read Access lets CertFusion see your forms, but not register the webhook that delivers new submissions. Open the Permissions dropdown on that row and switch it to Full Access.

If you skip this, the connection will appear to work but no recipients will ever arrive.
Copy the key, switch back to your CertFusion tab, paste it into the API Key field, and click Connect.

Jotform now shows as Active in your integrations list, connected under your Jotform account email.

EU and HIPAA Jotform accounts are detected automatically — you don't need to configure a different endpoint.
Connecting the account is only half the job. Now you tell CertFusion which form feeds which certificate.
Open Certificate Templates, pick the design you want to automate, and go to its Recipients tab. Click Add Recipients, then choose Jotform under Or import from your tools.

The Jotform to Certificates panel opens, confirming which Jotform account is linked.

Pick your form from the Select Form dropdown, then click Configure Webhook.

This is the part that matters most. CertFusion needs to know which Jotform question holds the recipient's name and which holds their email.

Above the field mapping is an Auto Issue toggle, and it changes the behaviour meaningfully:
You can change this later without redoing the mapping.
Click Save Configuration. The webhook goes live immediately, and CertFusion confirms it with a summary of exactly what's wired up.

Never trust an integration you haven't tested. Open your form in Jotform, switch on Preview Form to get the live link, and fill it in as an attendee would.

Submit it. From the learner's side, that's the entire experience — they see a thank-you page and nothing else.
Back in CertFusion, open the design's Recipients tab and hit the refresh button. Your test submission is already there, pulled straight from the form.

With Auto Issue off, the status reads Pending and waits for you. With it on, the certificate is already on its way.
Why do I need a full-access Jotform API key instead of a read-only one? CertFusion registers a webhook on your form so Jotform can push new submissions across. Registering a webhook is a write action, so a read-only key can't do it. Read-only keys let CertFusion list your forms but never deliver any submissions.
Will existing submissions be imported? No. The webhook applies to new submissions from the moment you save the configuration. To bring in past entries, export them from Jotform as a CSV and use CertFusion's CSV import instead.
Can one Jotform form feed more than one certificate design? Each webhook configuration links one form to one certificate list. If a single form should produce different certificates, configure the webhook separately on each design, or split the routing with a form field and separate forms.
What happens if someone submits the form twice? Each submission creates a recipient entry. If duplicates are a concern, enable Jotform's own submission limits or unique-response settings on the form itself before it reaches CertFusion.
Does this work with Jotform EU and HIPAA accounts? Yes. CertFusion detects EU and HIPAA-compliant Jotform accounts automatically from the API key — there's no separate setting to change.
Can I map more than just name and email? Yes. Any custom placeholder in your certificate design appears in the mapping screen as an optional field. Course name, cohort, date, and score are all common ones.
Schema suggestion: this post fits HowTo schema for the seven setup steps, plus FAQPage schema for the questions above. Marking up both improves eligibility for step-by-step rich results and FAQ snippets.
The same setup, start to finish, in under three minutes — from connecting the API key to seeing a test submission land in CertFusion.
Discover more insights and stories that might interest you