Zapier Integration

Wauld’s Zapier integration helps you connect Wauld with the other tools your team already uses, such as Gmail, Google Sheets, Slack, HubSpot, Typeform, Airtable, and many more. Instead of manually moving information between systems, you can create automated workflows that issue credentials, notify teams, update records, or send recipient information to another app when credentials are issued.

For example, you can:

• Send an email through Gmail whenever a credential is issued in Wauld.

• Add issued credential details to a Google Sheet for reporting.

• Notify a Slack channel when a new credential is issued.

• Issue a Wauld credential automatically when someone completes a form, course, training, or onboarding workflow in another platform.

Zapier is built around automated workflows called Zaps. A Zap connects apps together using a trigger and one or more actions. A trigger is the event that starts the Zap, and an action is what Zapier performs after the trigger happens.

Wauld currently supports:

Before You Begin

Before setting up the integration, make sure you have access to both Wauld and Zapier. You will need a Zapier account, a Wauld account, and permission to access the Integrations section in Wauld.

You should also have at least one workspace, engagement, and document already created in Wauld. If you are using Wauld as the trigger app, it is helpful to have at least one previously issued credential from the selected document. This allows Zapier to fetch a sample record during testing. If you are using Wauld as the action app, the selected document should already include the recipient fields and any custom attributes you want to map from the trigger app.

To connect Wauld with Zapier, you will need to generate a Zapier access token from Wauld. This token allows Zapier to communicate with your Wauld account.

How Wauld Works with Zapier

Wauld can be used in Zapier in two ways:

1. Wauld as the trigger app

2. Wauld as the action app

When Wauld is used as the trigger app, the Zap starts when a credential is issued in Wauld. This is useful when you want to notify someone, update a record, or send credential information to another system after issuance.

When Wauld is used as the action app, another app starts the Zap, and Wauld issues a credential based on the information received from that app. This is useful when credential issuance depends on a form submission, course completion, spreadsheet entry, CRM update, or another external event.

Part 1: Using Wauld as the Trigger App

Use Wauld as the trigger app when you want another app to do something after a credential is issued in Wauld. For example, you may want to send a Gmail email to the recipient whenever a credential is issued.

The Zap would work like this:

In this workflow, Wauld sends credential details to Zapier whenever a credential is issued from the selected document. Zapier then uses that information to perform the next action, such as sending an email through Gmail.

Trigger Setup: Wauld

Zapier generally organizes setup into three main stages:

1. Setup

2. Configure

3. Test

Log in to your Zapier account and click Create. From the available options, select Zap.

This opens the Zap editor, where you can configure the trigger and action for your automation.

Setup

In the Zap editor, click the Trigger step. Zapier will open the app library.

Search for Wauld and select it.

Zapier will then ask you to select the trigger event. Choose: New Credential Issued

This event starts the Zap whenever a new credential is issued from the selected Wauld document.

Next, Zapier will ask you to connect your Wauld account. If your Wauld account is already connected, select the existing account and continue. If this is your first time connecting Wauld to Zapier, you will need to generate a Zapier token from Wauld.

Generate the Zapier Token in Wauld

To generate your token:

1. Log in to Wauld.

2. Open Integrations from the left navigation bar.

3. In the integration gallery, select Zapier.

4. On the Zapier details page, click Generate Token.

5. Copy the generated token.

Return to Zapier, paste the token into the connection field, and click Yes, Continue to Wauld.

Once the token is accepted, Zapier will connect your Wauld account and return you to the Zap editor. Click Continue.

Configure

The configure step tells Zapier which Wauld document it should monitor for new credential issuances.

You will need to select the workspace, engagement, and document. First, choose the workspace where the document exists. Then select the engagement that contains the document. Finally, select the specific document that should trigger the Zap when a new credential is issued.

This is an important step because the Zap will only run for the document you select here. For example, if you select a “Certificate of Completion” document, the Zap will run when credentials are issued from that document. It will not automatically run for other documents unless you create separate Zaps or configure them separately.

Once the workspace, engagement, and document are selected, click Continue.

Test

In the test step, Zapier fetches sample credential data from recent issuances for the selected Wauld document. This sample data is used to configure the next action in the Zap.

If the selected document has previous issuances, Zapier will show sample records. You can open a record to review the information Wauld is sending to Zapier. After reviewing the record, select the sample you want to use for setting up the action and click Continue with selected record.

If Zapier does not find any sample records, issue a test credential from the selected document in Wauld and then return to Zapier to test the trigger again.

Data Shared by Wauld When a Credential Is Issued

When a credential is issued, Wauld can share information such as credential details, document details, issuing authority details, recipient details, and custom attribute values.

The information shared may include the following fields:

1. Credential Information

   1. ID

   2. Issue Time

   3. Expire Time

2. Document Information

   1. Document ID

   2. Document Name

   3. Document Type

   4. Document Skills

   5. Document Earning Criteria Type

   6. Document Earning Criteria Description

   7. Document Earning Criteria Supporting Link

3. Issuing Authority Information

   1. Issuing Authority ID

   2. Issuing Authority Name

   3. Issuing Authority Website

   4. Issuing Authority Verification Status

4. Recipient Information

   1. Recipient Name

   2. Recipient Email

   3. Custom Attribute Name

   4. Custom Attribute Value

Custom attribute fields depend on the document selected in Wauld. If your document includes custom attributes, those fields will appear in Zapier and can be used in the action step.

Action Setup: Gmail

Setup

After testing the Wauld trigger, click the Action step in the Zap editor.

Search for Gmail and select it.

Zapier will ask you to choose an action event. Select: Send Email

This tells Zapier to send an email through Gmail whenever the Wauld trigger runs.

Next, connect your Gmail account. If your Gmail account is already connected, select it and continue. If not, follow Zapier’s prompts to sign in and allow the required permissions.

Click Continue.

Configure

In the configure step, you will create the email that Gmail should send. You can type static text and also insert dynamic fields from the Wauld trigger record.

For example, the To field can be mapped to the recipient email from Wauld. The subject can include the document name, and the body can include the recipient name, issuing authority name, issue time, and other credential details.

A sample configuration could look like this:

A sample email body could be written like this:

Hi [Recipient Name],

Your credential, [Document Name], has been issued by [Issuing Authority Name].

Issue Time: [Issue Time]

You can log in to Wauld to view, download, and share your credential.

Thank you.

When configuring the email body, use Zapier’s field selector to insert values from the Wauld trigger. This ensures that each email is personalized based on the credential that was issued.

Test

In the test step, Zapier uses the selected sample credential record from Wauld and sends a test email through Gmail.

Before testing, review the mapped fields carefully. Make sure the recipient email is correct, the subject line is clear, and the email body includes the correct Wauld fields.

Click Test step to send the test email. After the test is complete, check the inbox to confirm that the email was delivered and that the mapped values appeared correctly.

If everything looks correct, click Publish. Once the Zap is published, Gmail will automatically send an email whenever a new credential is issued from the selected Wauld document.

Part 2: Using Wauld as the Action App

Use Wauld as the action app when another app should trigger credential issuance in Wauld.

For example, you may want Wauld to issue a credential when someone submits a Google Form.

The Zap would work like this:

In this workflow, Google Forms collects the recipient and completion details. Zapier then sends that information to Wauld, and Wauld issues the credential using the mapped data.

Trigger Setup: Google Forms

Google Forms is a useful trigger app when credential issuance depends on submitted information. For example, a training team may collect completion details through a form after a workshop, webinar, onboarding session, or assessment.

The form can collect information such as name, email address, course name, completion date, completion score, instructor name, and certificate level. Zapier can then send this data to Wauld and issue a credential automatically.

Setup

Create a new Zap in Zapier and click the Trigger step. Search for Google Forms and select it.

Choose the trigger event, such as: New Form Response

This means the Zap will start whenever a new response is submitted through the selected Google Form.

Next, connect your Google account. If the account is already connected, select it and continue.

Configure

In the configure step, select the Google Form that should trigger the Zap. Depending on your Google Forms and Zapier setup, you may also need to select the response worksheet where form submissions are stored.

The selected form should contain the fields needed to issue a credential in Wauld. At minimum, the form should collect the recipient’s name and email address. If the Wauld document includes custom attributes, the form should also collect the values for those attributes.

Example form fields:

After selecting the form and response source, click Continue.

Test

In the test step, Zapier fetches a sample form response. This sample response is important because it provides the data you will map into the Wauld action.

Open the sample record and check whether all required fields are available. Make sure the response includes the recipient name, recipient email, and any custom attribute values needed for the Wauld document.

Once the sample record looks correct, continue to the action step.

Action Setup: Wauld

Setup

In the action step, search for Wauld in the app library and select it.

Zapier will ask you to choose an action event. Select:Issue Credential

This action allows Zapier to issue a credential in Wauld using data from the trigger app.

For example, if Google Forms is the trigger app, the Wauld action can use the form response data to issue a credential to the person who submitted the form.

Next, connect your Wauld account. If your Wauld account is already connected, select it and continue. If it is not connected, generate a token from Wauld by going to Integrations > Zapier, clicking Generate Token, and copying the token into Zapier.

Configure

The configure step is where you define exactly which credential should be issued and what data should be used for issuance.

First, select the Workspace where the document exists. Then select the Engagement that contains the document. After that, select the Document you want Wauld to issue.

The selected document controls which fields appear in the action setup. If the document has custom attributes, those attributes will appear in Zapier and must be filled or mapped before the credential can be issued correctly.

Next, configure the recipient details. You can type recipient values manually, but in most automated workflows you should map these fields from the trigger record.

Example mapping from Google Forms:

After recipient details, configure the credential actions. Wauld may include options such as Shareable and Add to LinkedIn. These options are usually set to true by default, but you can change them if needed.

If Shareable is true, the recipient can share the credential using a credential link. If Add to LinkedIn is true, the recipient can add or share the credential on LinkedIn, depending on the available credential sharing options.

Next, configure the expiry time. If the credential should not expire, leave the expiry field blank. If the credential should expire on a specific date, either enter the date manually or map it from the trigger app.

For example, if your Google Form includes a “Credential Expiry Date” field, you can map that field to the expiry time in Wauld. Make sure the date is in the correct format. If the date format is invalid, Zapier may show an error during testing.

Finally, map the custom attributes required by the selected Wauld document. These fields depend on how the document was created in Wauld.

Example custom attribute mapping:

Each required custom attribute should be completed. If a required field is left blank or mapped incorrectly, the credential may fail to issue.

Test

In the test step, Zapier shows the data that will be sent to Wauld based on the sample record selected from the trigger setup.

Review every mapped field before running the test. Check the workspace, engagement, document, recipient name, recipient email, expiry time, credential actions, and custom attributes.

If everything looks correct, click the Test step. Zapier will send the sample data to Wauld and issue a test credential.

Testing the Wauld action may create a real credential in Wauld using the sample data, so review the data carefully before running the test. If you do not want to issue a test credential, you can skip the test, but testing is recommended before publishing the Zap. After the test is successful, publish the Zap.

Once published, whenever the trigger app receives a new record, Zapier will send the mapped data to Wauld and Wauld will issue the credential automatically.

Extras

Other Common Wauld Zapier Workflows

Wauld can be used in different automation flows depending on whether it is the trigger app or the action app.

When Wauld is the trigger app, the workflow starts in Wauld. This is useful when something should happen after a credential is issued.

When Wauld is the action app, the workflow ends with credential issuance. This is useful when another platform collects or confirms the information needed to issue a credential.

Troubleshooting

Most Zapier-related errors are shown directly in Zapier during setup, testing, or Zap runs. If a published Zap fails, Zapier may also send an email notification with details about the failed run and the reason for the error.

• Wauld Account Connection Fails

  • If Zapier cannot connect to Wauld, the token may be incorrect, expired, revoked, or regenerated. Go to Wauld, open Integrations > Zapier, and generate a new token. Then return to Zapier and reconnect the Wauld account using the new token.

• No Sample Records Are Found

  • If Zapier does not find sample records while testing the New Credential Issued trigger, there may be no recent issuances for the selected document.

  • To fix this, issue a test credential from the selected document in Wauld and then test the trigger again in Zapier.

• Required Fields Are Missing

  • If the Wauld action fails because required fields are missing, review the configure step. Make sure the recipient name, recipient email, and all required custom attributes are filled or mapped from the trigger record.

• Expiry Date Format Is Incorrect

  • If the expiry field is mapped incorrectly, Zapier may show a date format error during testing. Check the date value coming from the trigger app and make sure it is in a supported format before sending it to Wauld.

  • If no expiry is required, leave the expiry field blank.

• Expiry Date Is in the Past

  • If the expiry date is set to a past date, the credential will not be issued. Wauld requires the expiry date to be a future date.

  • To fix this, review the expiry field in the Wauld action configuration and make sure the mapped date is later than the current date. If the credential does not need to expire, leave the expiry field blank.

• Custom Attributes Changed in Wauld

  • If you update the Wauld document after publishing the Zap, the Zap may need to be updated. For example, if you add new attributes, rename fields, or remove existing attributes, Zapier may still be using the older field setup.

  • Open the Zap, review the Wauld action configuration, refresh the fields if needed, and test the Zap again.

• Document Is Deleted or No Longer Available

  • If the selected Wauld document is deleted or becomes unavailable, the Zap may fail. In this case, select an active document in the Wauld trigger or action setup and publish the updated Zap.

Managing Zapier Access in Wauld

You can manage Zapier access from the Zapier details page in Wauld.

Go to: Wauld > Integrations > Zapier

From this page, you can regenerate or revoke the Zapier access token.

• Regenerate Token

  • Use Regenerate Token when you want to replace the existing token with a new one.

  • When you regenerate the token, the old token is revoked and a new token is created. Any Zap using the old token may stop working until the Wauld account is reconnected in Zapier using the new token.

• Revoke Token

  • Use Revoke Token when you want to remove Zapier’s access to Wauld.

  • After the token is revoked, Zapier will no longer be able to access Wauld using that token. Any active Zaps connected with the revoked token may fail until a new token is generated and connected.

Best Practices

1. Test with sample records before publishing - Always test your Zap using realistic sample data before turning it on.

2. Use clear field names - If you are using forms or spreadsheets as triggers, use simple field names such as Recipient Name, Recipient Email, Course Name, Completion Date, and Score.

3. Keep required Wauld fields mapped - Recipient name, recipient email, and required custom attributes should always be mapped correctly.

4. Review Zaps after document updates - If you update the selected Wauld document, review any related Zaps to make sure the fields still match.

5. Use test credentials carefully - Testing the Wauld action may issue a real credential in Wauld using the sample data. Review the test record before running the test.

6. Monitor Zapier errors - Failed runs and field mapping issues are usually shown in Zapier. Review Zapier task history and error emails if a Zap does not work as expected.

7. Protect your Zapier token - Treat the Wauld Zapier token like a password. Do not share it publicly or store it in unsecured locations.

Summary

The Wauld Zapier integration allows you to automate credential workflows between Wauld and other applications.

You can use Wauld as a trigger when you want another app to perform an action after a credential is issued. You can use Wauld as an action when you want another app to trigger credential issuance in Wauld.

By connecting Wauld with Zapier, you can reduce manual work, improve reporting, notify teams, and automatically issue credentials based on activity in other systems.