Key Takeaways
Zapier and Wauld together automate certificate issuance, eliminating manual certificate creation and delivery workflows.
Wauld can work as both a trigger and an action app inside Zapier, making it flexible for many automation use cases.
Automated digital credentials through Wauld include verification, sharing, tracking, and branded delivery features beyond static PDFs.
Use Zapier-Wauld Integration to Automatically Issue Certificates
Picture this. A course just wrapped up. Forty people completed it. Someone on your team now has to open a spreadsheet, copy names into a certificate template, export PDFs, and send forty individual emails. That someone might be you.
If you have been issuing certificates manually, you know exactly how that afternoon feels. Wauld's Zapier integration exists to make it stop. Connect Wauld with the tools your team already uses, and certificates go out automatically the moment someone completes a course, submits a form, finishes a training, or hits any milestone you define. No batch processing. No manual work. No delays.
This guide walks you through the full setup: what the integration does, how to connect it, and how to build both directions of the workflow.
How Wauld and Zapier Work Together
Zapier connects apps through automated workflows called Zaps. Every Zap has a trigger (the event that starts things off) and one or more actions (what happens next). No code required.
Wauld works in both directions inside a Zap.
When Wauld is the trigger, the workflow starts inside Wauld. A credential gets issued, and that event kicks off an action in another app. You might want to send a Gmail confirmation, log the credential to a Google Sheet, notify a Slack channel, or update a contact in HubSpot. Wauld fires the signal; the other app does its thing.
When Wauld is the action, another app starts the workflow. Someone submits a Google Form, a new row gets added to a spreadsheet, a contact reaches a milestone in your CRM. Zapier picks that up and tells Wauld to issue a certificate. The whole thing happens in the background while you focus on running your program.
What You Can Build
Here is a quick look at the kinds of workflows you can set up.
Wauld as the trigger:
Wauld Trigger | Action App | What Happens |
New Credential Issued | Gmail | Sends a personalized email to the recipient |
New Credential Issued | Google Sheets | Logs credential data to a reporting sheet |
New Credential Issued | Slack | Notifies your internal team |
New Credential Issued | HubSpot | Creates or updates a contact record |
New Credential Issued | Airtable | Adds credential details to a database |
Wauld as the action:
Trigger App | Wauld Action | What Happens |
Google Forms | Issue Credential | Issues a certificate after a form submission |
Google Sheets | Issue Credential | Issues a credential when a new row is added |
Typeform | Issue Credential | Issues a credential after an assessment |
HubSpot | Issue Credential | Issues a credential when a contact reaches a milestone |
Webhooks by Zapier | Issue Credential | Issues credentials from a custom system |
Before You Start
You will need a Zapier account, a Wauld account, and at least one workspace, engagement, and document already created in Wauld.
If you are planning to use Wauld as the trigger, it also helps to have at least one credential already issued from the document you want to connect. Zapier uses a real past record as a sample during the test step, so having one ready makes setup smoother.
If you are using Wauld as the action, make sure your document already includes any custom attributes you want to map from the trigger app. The fields you see in Zapier come directly from your document setup in Wauld.
Generating Your Zapier Access Token
The connection between Wauld and Zapier runs through an access token. Here is how to get it.
Log in to Wauld, open Integrations from the left navigation bar, and select Zapier from the integration gallery. On the Zapier details page, click Generate Token and copy what appears.
That token is what you will paste into Zapier when it asks you to connect your Wauld account. Treat it like a password. Do not share it publicly or store it somewhere unsecured.
Part 1: Using Wauld as the Trigger App
This setup is for when you want something to happen in another app after a certificate is issued. The most common example is sending a personalized email through Gmail the moment a credential goes out.
The workflow looks like this: Wauld issues a credential, Zapier picks it up, Gmail sends an email.
Setting Up the Trigger in Zapier
Log in to Zapier, click Create, and select Zap. In the Zap editor, click the Trigger step and search for Wauld.
Select the trigger event: New Credential Issued. This is the only trigger Wauld currently supports, and it fires every time a credential is issued from the document you specify.
Zapier will ask you to connect your Wauld account. If you have connected it before, select the existing account. If this is your first time, paste the token you generated from Wauld and click Yes, Continue to Wauld. Once it connects, click Continue.
Configuring Which Document to Monitor
This is where you tell Zapier which document to watch. Select the workspace, then the engagement, then the specific document.
This matters more than it might seem. The Zap only runs for the document you select here. If you have a Certificate of Completion and a Certificate of Attendance in the same workspace, they need separate Zaps. Select the wrong document and the automation either does nothing or fires at the wrong time.
Once you have made your selections, click Continue.
Testing the Trigger
Zapier will look for recent issuances from the document you selected and pull one in as a sample record. Open it to see what Wauld is sending across. These are the fields you will map in the action step.
If Zapier comes back with no records, it just means no credentials have been issued from that document yet. The fix is simple: go to Wauld, issue a test credential from that document, then come back to Zapier and run the test again.
Once you have a sample record, select it and click Continue with selected record.
What Data Wauld Sends Across
When a credential is issued, Wauld passes a full set of fields to Zapier. These become available to map into whatever action you are building.
Credential details include the credential ID, issue time, and expire time.
Document details include the document ID, document name, document type, skills, earning criteria type, earning criteria description, and earning criteria supporting link.
Issuing authority details include the issuing authority ID, name, website, and verification status.
Recipient details include the recipient name and email.
Custom attributes appear as custom attribute name and value pairs, depending on what the selected document contains. If your document has custom fields, they show up here and can be mapped into the action just like any other field.
Part 2: Using Wauld as the Action App (Most Common)
This setup is for when another platform collects information and you want Wauld to issue a certificate based on what it receives. It is the most powerful setup for automating certificate delivery at scale.
The trigger does not have to be Google Forms. It can be Typeform, HubSpot, Google Sheets, Airtable, Webhooks by Zapier, or any other app Zapier supports. The steps are the same regardless of which trigger app you use.
Wauld connects with 500+ apps and platforms across LMSs, forms, webinar tools, community platforms, HR systems, CRMs, video conferencing platforms, payment gateways, and automation tools.
Some examples include:
Forms & Assessments: Google Forms, Typeform, Jotform, Tally, Microsoft Forms
LMS & Course Platforms: Thinkific, Teachable, Moodle, LearnDash, TalentLMS, Canvas LMS
Video Conferencing & Webinar Platforms: Zoom, Microsoft Teams, Webex, Airmeet, Livestorm, Hopin
Community Platforms: Circle, Discord, Slack, Skool, Mighty Networks
Event Platforms: Eventbrite, Meetup, Luma, Cvent
HR & Employee Training: BambooHR, Workday, SAP SuccessFactors, Deel
Automation & Workflow Tools: Zapier, Airtable, Google Sheets, Webhooks
For example:
A learner completes a course on Thinkific → Wauld automatically issues a branded certificate.
An attendee joins a Zoom webinar → Wauld sends a participation credential instantly after the session.
A user submits a Typeform quiz → Wauld generates and delivers a certificate automatically.
An employee completes onboarding in BambooHR → Wauld issues internal training credentials.
For this walkthrough, the example is Google Forms triggering certificate issuance in Wauld.
Setting Up the Trigger: Google Forms
Create a new Zap in Zapier, click the Trigger step, search for Google Forms, and select it. Choose the trigger event New Form Response, connect your Google account, and click Continue.
In the configure step, select the specific form you want to use. Depending on your setup, you may also need to select the response worksheet where submissions are stored. Choose the right one and click Continue.
The form itself should already be set up to collect everything Wauld needs. At minimum, that means the recipient's name and email address. If the Wauld document you are issuing from has custom attributes like course name, completion date, score, instructor name, or certificate level, the form should collect those too.
In the test step, Zapier pulls in a sample form response. Open it and confirm that all the fields you need are present before moving on.
Setting Up the Action: Wauld
Click the Action step, search for Wauld, and select it. Choose the action event Issue Credential, connect your Wauld account, and click Continue.
Selecting the right document
In the configure step, start by selecting the workspace, then the engagement, then the document. The document you select controls which fields appear below it. If the document has custom attributes, they show up here and need to be filled or mapped before the credential can issue correctly.
Mapping recipient details
Map the recipient name and email from the Google Form fields. These are the two fields Wauld always requires.
Credential options
Wauld includes two credential action options: Shareable and Add to LinkedIn. Both are typically set to true by default. When Shareable is on, the recipient gets a credential link they can share anywhere. When Add to LinkedIn is on, the recipient can add or share the credential directly on their LinkedIn profile. You can adjust these if your use case calls for something different.
Expiry date
If the credential should not expire, leave the expiry field blank. If it should expire, either enter the date manually or map it from a field in your form. Make sure whatever date gets mapped is in a valid format and, importantly, that it is always a future date. Wauld will not issue a credential with a past expiry date, and Zapier will log an error if the format is wrong.
Custom attributes
Finally, map any custom attributes the document requires. These come from your Wauld document setup and might include things like course name, completion date, score, instructor name, or certificate level. Each required attribute needs a value. If one is left blank or mapped to the wrong field, the credential will not issue.
Testing before you publish
Zapier will show you exactly what data it is about to send to Wauld based on the sample form response. Go through every field: workspace, engagement, document, recipient name, recipient email, expiry, credential options, and custom attributes.
One important note here: testing the Wauld action may create a real credential in Wauld using the sample data. Review everything carefully before you click Test step. If you are not ready to issue a real credential yet, you can skip the test for now, but always test before you publish the Zap live.
When the test succeeds, click Publish. From that point on, every new form submission triggers automatic certificate issuance in Wauld.
Troubleshooting
Most issues surface during setup or the first few live runs. Zapier logs errors in the task history and often sends an email notification when something fails. Here is what the common ones mean and how to fix them.
The Wauld account connection fails. The token is probably incorrect, expired, revoked, or was regenerated after you connected. Go to Wauld, open Integrations and then Zapier, generate a new token, and reconnect in Zapier.
No sample records are found during trigger testing. No credentials have been issued from that document yet. Issue one from Wauld, then come back to Zapier and test the trigger again.
The Wauld action fails because required fields are missing. Open the configure step and check that the recipient name, email, and all required custom attributes are mapped. A blank required field will cause the credential to fail every time.
There is an expiry date format error. Check what the trigger app is sending and make sure it matches a supported date format. If no expiry is needed, leave the field blank.
The expiry date is in the past. Wauld requires a future date for expiry. Check the mapped value and make sure whatever date comes through is always later than the current date.
Custom attributes changed in Wauld after the Zap was published. If you added, renamed, or removed attributes from the document, the Zap is still using the old field setup. Open the Zap, refresh the Wauld action fields, remap anything that changed, and test again.
The selected document was deleted or is no longer available. Select an active document in the Wauld trigger or action setup and republish the Zap.
Managing Zapier Access in Wauld
You can manage the connection at any time from inside Wauld by going to Integrations and then Zapier.
Regenerate Token replaces the existing token with a new one. The old token stops working immediately, so any Zaps using it will need to be reconnected in Zapier with the new token.
Revoke Token removes Zapier's access to Wauld entirely. Active Zaps will fail until you generate a new token and reconnect.
A Few Things Worth Knowing Before You Go Live
Test with realistic data. A sample record that closely mirrors what real submissions will look like will save you from surprises after you publish.
Use clear field names in your forms. Names like Recipient Name, Recipient Email, Course Name, and Completion Date are much easier to map than abbreviations or ambiguous labels.
Review your Zaps after updating a document. Adding or renaming custom attributes in Wauld does not automatically update your Zaps. Go in and check them whenever the document changes.
One Zap per document. Zapier monitors one document at a time. If you need automation across multiple documents, set up a separate Zap for each one.
What Happens After the Certificate Goes Out
The credential does not stop being useful the moment it lands in an inbox. With Wauld, every certificate has a life beyond issuance.
Recipients get a personal credential page where they can view, download, and share their certificate. They can add it to LinkedIn, send the link to an employer, or let anyone verify it instantly using a QR code. Every Wauld credential is built for this from the start.
On your end, the issuer dashboard shows you everything happening across your issued credentials: who opened theirs, how often it was viewed, and how many times it was shared or verified. You can also edit, void, or reissue credentials from the same place if something needs correcting later.
This is the difference between sending a PDF and issuing a digital credential. The PDF sits in a downloads folder. The credential keeps working.
Ready to Connect?
If you are still sending certificates manually, this integration is worth an hour of your time to set up. Once it is live, credentials go out on their own and you get the tracking and verification features that come with every Wauld certificate.
Frequently Asked Questions on Wauld and Zapier
Get answers to the most common questions about setting up, automating, troubleshooting, and scaling certificate issuance using Zapier and Wauld.
