Wauld’s Make integration helps you connect Wauld with the other tools your team already uses. Instead of manually moving information between systems, you can create automated scenarios that send credential information to other apps, notify teams, update records, or issue credentials in Wauld based on activity from another platform.

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 a new row is added in Google Sheets.

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

Make workflows are called scenarios. A scenario is made up of one or more modules. Each module performs a specific task, such as watching for a new event, sending data to another app, creating a record, or issuing a credential.

Wauld currently supports:

The Make integration is connected at the account level in Wauld. Once your Wauld account is connected to Make, Make can access the supported workflows for the connected Wauld account and the available workspaces under that account.

This integration is available to users on all Wauld plans, including the Free plan.

Before You Begin

Before setting up the integration, make sure you have access to both Wauld and Make. You will need a Make 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 a document that can be used for testing credential issuance. 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 another app.

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

How Wauld Works with Make

Wauld can be used in Make in two ways:

1. Wauld as the trigger module

2. Wauld as the action module

When Wauld is used as the trigger module, the scenario starts when a credential is issued in Wauld. This is useful when you want to send credential data to another app, notify someone, update a record, or start another automated process after issuance.

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

Part 1: Using Wauld as the Trigger Module

Use Wauld as the trigger module 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 scenario would work like this:

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

Trigger Setup: Wauld

Log in to your Make account and click Create a new scenario from the home screen.

This opens the scenario editor. The first module opens automatically and asks you to select an app.

Setup

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

From the list of available Wauld modules, select: Watch New Credential Issued

This module starts the scenario whenever a new credential is issued from the selected Wauld document.

After selecting the module, Make will show the webhook setup screen. If you already have a webhook configured, you can select it from the list. If you do not have one yet, click Add to create a new webhook.

In the webhook form, enter a webhook name. Use a name that helps you identify the document or workflow later. Example: Certificate of Completion Issuance Webhook

Next, select the Wauld connection that should be used for this webhook. If you already have a Wauld connection added, select it from the connection dropdown. If you do not have a connection yet, click Add next to the connection field.

When you add a new connection, Make opens the connection form. Enter a connection name and paste the Wauld access token into the access token field.

To generate the access token in Wauld:

1. Log in to Wauld.

2. Open Integrations from the left navigation bar.

3. In the integration gallery, select Make.

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

5. Copy the generated token.

Return to Make, paste the token into the access token field, and save the connection.

Once the connection is added, you will return to the webhook setup screen.

Configure

After selecting or creating the Wauld connection, continue configuring the webhook.

You will need to select the following fields:

First, select the workspace where the document exists. Then select the engagement that contains the document. Finally, select the document that should trigger the scenario when a new credential is issued.

This step is important because the scenario will run only when credentials are issued from the selected document. For example, if you select a “Certificate of Completion” document, the scenario will run when credentials are issued from that document. It will not automatically run for other documents unless those are configured separately.

After selecting the workspace, engagement, and document, click Next.

You will return to the webhook screen. The newly created webhook should now be selected at the top, and you may see a webhook link displayed below it.

Click Save to save the Wauld trigger module.

Test

To test the Wauld trigger, Make needs to capture sample data from an actual credential issuance. In Make, click Run once. This puts the scenario in listening mode.

Then go to Wauld and issue a test credential from the selected document. You can add test recipient details, continue to the preview screen, and issue the credential.

After the credential is issued, return to Make. The Wauld trigger module should capture the credential data sent from Wauld.

You can open the captured output in Make to review the data. This sample data can be used to configure the next module in the scenario.

Data Shared by Wauld When a Credential Is Issued

When a credential is issued, Wauld sends credential, document, issuing authority, recipient, skills, earning criteria, and custom attribute information to Make.

The information shared may include the following fields:

Credential Information

• ID

• Issue Time

• Expire Time

Document Information

• Document ID

• Document Name

• Document Type

• Document Skills

• Document Earning Criteria Type

• Document Earning Criteria Description

• Document Earning Criteria Supporting Link

Issuing Authority Information

• Issuing Authority ID

• Issuing Authority Name

• Issuing Authority Website

• Issuing Authority Verification Status

Recipient Information

• Recipient Name

• Recipient Email

Custom Attribute Information

• Custom Attribute Name

• Custom Attribute Value

Custom attribute fields depend on the document selected in Wauld. If your document includes custom attributes, those fields can be used in the next module of the scenario.

Wauld sends the complete credential payload to Make, including credential, issuer, recipient, skills, earning criteria, and attribute information. However, Make may have restrictions in how some repeated fields are captured and made available during scenario setup. Because of this, when a document has multiple skills, multiple earning criteria, or multiple attributes, Make may show only one value from each of those sections in the mapping options.

At this stage, it is recommended to use the Wauld trigger with documents that have one skill, one earning criterion, and one attribute value. If a document contains multiple skills, earning criteria, or attributes, some values may not appear in the mapping options for the next module, even though they are included in the payload sent by Wauld. This can lead to incomplete workflow setup in Make.

Action Setup: Gmail

After testing the Wauld trigger, you can add another module to decide what should happen when the trigger runs. In this example, Gmail will send an email when a new credential is issued in Wauld.

Setup

In the scenario editor, click the plus icon after the Wauld module.

Search for Gmail and select it. From the list of available Gmail modules, select: Send an Email

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

If your Gmail account is already connected to Make, select the existing connection. If not, follow Make’s prompts to connect your Gmail account and allow the required permissions.

Configure

In the Gmail module, configure the email that should be sent when a credential is issued.

You can type static text and also map dynamic fields from the Wauld trigger output. For example, the To field can be mapped to the recipient email from Wauld. The subject can include the document name, and the email 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 Make’s mapping panel to insert values from the Wauld trigger output. This ensures that each email is personalized based on the credential that was issued.

After configuring the Gmail module, click Save.

Test

To test the Gmail module, click Run once in Make.

Then go to Wauld and issue another test credential from the selected document. After the credential is issued, return to Make and check whether the scenario ran successfully.

If the Gmail module is configured correctly, Make will send an email using the credential data received from Wauld.

After the test is complete, check the inbox to confirm that:

• The email was delivered.

• The recipient email was mapped correctly.

• The subject line appears correctly.

• The email body includes the correct Wauld fields.

• The mapped values appear as expected.

If something is incorrect, update the Gmail module configuration, save the module, and run the scenario again.

Once everything works as expected, turn on the scenario using the scenario toggle. After the scenario is turned on, Make will automatically run it whenever a credential is issued from the selected Wauld document.

Part 2: Using Wauld as the Action Module

Use Wauld as the action module when another app should trigger credential issuance in Wauld. For example, you may want Wauld to issue a credential when a new row is added in Google Sheets.

The scenario would work like this:

In this workflow, Google Sheets stores the recipient and credential details. Make sends that information to Wauld, and Wauld issues the credential using the mapped data.

Trigger Setup: Google Sheets

Google Sheets is useful when credential issuance depends on structured data in a spreadsheet. For example, an admin may add rows for recipients who completed a course, attended a workshop, or passed an assessment.

The sheet can include information such as name, email address, course name, completion date, completion score, instructor name, certificate level, and expiry date. Make can then use this row data to issue a credential in Wauld automatically.

Setup

Create a new scenario in Make. Click the first module and search for Google Sheets. Select the Google Sheets module: Watch New Rows

This means the scenario will start whenever a new row is added to the selected sheet.

If your Google account is already connected to Make, select the existing connection. If not, follow Make’s prompts to connect your Google account.

Configure

In the Google Sheets module, select the spreadsheet that should trigger the scenario. You may need to configure fields such as:

The selected sheet should contain the fields needed to issue a credential in Wauld. At minimum, the sheet should include recipient name and recipient email. If the Wauld document includes custom attributes, the sheet should also include columns for those values.

Example sheet columns:

After selecting the spreadsheet and sheet, click Save.

Make may show a Choose where to start modal. Select All if you want Make to start from existing rows, or select the preferred option based on your workflow. Then click Save.

Test

Before configuring the Wauld action, capture sample data from Google Sheets. Click Run once in Make.

Then go to the selected Google Sheet and add a new row with test data. Include values for recipient name, recipient email, and any custom attributes that should be used for the credential.

Return to Make. The Google Sheets module should capture the row data. This sample data will be available for mapping in the Wauld action module.

Action Setup: Wauld

Setup

After the Google Sheets module is saved and tested, add the Wauld action module. Click the plus icon after the Google Sheets module. Search for Wauld and select it. From the list of available Wauld modules, select: Issue Credential

This action allows Make to issue a credential in Wauld using data from the trigger module.

For example, if Google Sheets is the trigger module, the Wauld action can use row data to issue a credential to the person listed in the sheet.

Next, select your Wauld connection. If your Wauld account is already connected, select the existing connection. If it is not connected, click Add to create a new connection.

To create a new Wauld connection:

1. Enter a connection name.

2. Go to Wauld.

3. Open Integrations from the left navigation bar.

4. Select Make from the integration gallery.

5. Click Generate Token.

6. Copy the generated token.

7. Return to Make and paste the token into the access token field.

8. Save the connection.

Configure

The configure step defines which credential should be issued and what data should be used for issuance.

First, select the document location in Wauld:

The selected document controls how the credential should be issued. If the document includes custom attributes, those attributes should be added and mapped in the Make module.

If the selected Wauld document has custom attributes, go to the Custom Attributes section and click Add item.

Make will show two fields:

For each custom attribute used in the Wauld document, add a separate item.

Example custom attribute mapping from Google Sheets:

Make sure the attribute name matches the custom attribute name used in the Wauld document. If the attribute name is incorrect, the value may not be applied correctly during issuance.

If custom attributes are not added in Make, credentials issued from this scenario may be issued with empty values for those custom attributes.

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

Example mapping from Google Sheets:

Make sure the recipient email is mapped to a valid email address. If the recipient email is missing or invalid, the credential may fail to issue.

Next, configure the credential action fields.

Select Yes or No based on your credential workflow.

For example, select Yes for Shareable if recipients should be able to share their credential. Select Yes for Add to LinkedIn if recipients should be able to add or share their credential on LinkedIn.

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

For example, if your Google Sheet includes an Expiry Date column, you can map that column to the expiry date field in Wauld.

Make sure the expiry date uses the correct format required by the Wauld Make module. If the date format is incorrect, Make may show an error during testing or the credential may fail to issue. Learn more.

The expiry date must also be a future date. If the expiry date is in the past, the credential will not be issued.

After all required fields are configured, click Save.

Test

To test the Wauld action, click Run once in Make.

Then add a new test row in the selected Google Sheet. Make should detect the new row, pass the data to the Wauld action module, and issue a credential in Wauld.

After the scenario runs, review the execution in Make and confirm that the Wauld module completed successfully.

Also check Wauld to confirm that:

• The credential was issued.

• The recipient name is correct.

• The recipient email is correct.

• The custom attributes were filled correctly.

• The expiry date is correct, if used.

• The credential action settings are correct.

Testing the Wauld action may create a real credential in Wauld using the sample row data, so review your test data carefully before running the scenario.

If the test is successful, turn on the scenario using the scenario toggle. After the scenario is turned on, Make will automatically run it whenever the configured trigger event occurs.

Other Common Wauld Make Workflows

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

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

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

Troubleshooting

Most Make-related errors are shown directly in Make during setup, testing, or scenario runs. If a scenario fails, review the scenario execution history in Make to see where the error occurred and what message was returned.

Wauld Connection Fails

If Make cannot connect to Wauld, the access token may be incorrect, expired, revoked, or regenerated.

Go to Wauld, open Integrations > Make, and generate a new access token. Then return to Make and update or recreate the Wauld connection using the new token.

Wauld Trigger Does Not Capture Data

If the Wauld trigger does not capture data during testing, make sure you clicked Run once in Make before issuing the credential in Wauld.

Make must be listening when the credential is issued. After clicking Run once, go to Wauld, issue a test credential from the selected document, and then return to Make to check the captured data.

Also confirm that the credential was issued from the same workspace, engagement, and document selected in the Wauld trigger module.

Only One Skill, Earning Criterion, or Attribute Appears

Wauld sends the complete credential payload to Make, including skills, earning criteria, and attributes. However, Make may only make one value available in the mapping options when multiple values exist in these sections.

To avoid incomplete mapping during scenario setup, use the Wauld trigger with documents that have one skill, one earning criterion, and one attribute value.

Required Fields Are Missing

If the Wauld action fails because required fields are missing, review the action module configuration. Make sure the recipient name, recipient email, and required custom attributes are filled or mapped from the trigger module.

Custom Attributes Are Empty on Issued Credentials

If custom attributes are not added in the Make Wauld action module, credentials issued from the scenario may show empty custom attribute values.

To fix this, open the Wauld action module, go to the custom attributes section, click Add item, enter the exact attribute name used in the Wauld document, and map the correct value.

Custom Attribute Name Is Incorrect

If the custom attribute name entered in Make does not match the attribute name used in the Wauld document, the mapped value may not be applied correctly.

Check the Wauld document and confirm the exact custom attribute names. Then update the Make action module and test the scenario again.

Expiry Date Format Is Incorrect

If the expiry date is mapped incorrectly, Make may show a date format error during testing or the credential may fail to issue. Learn more

Check the date value coming from the trigger module and make sure it is in the format required by the Wauld Make module. If no expiry is required, leave the expiry date 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 date field in the Wauld action module and make sure the mapped date is later than the current date. If the credential does not need to expire, leave the expiry date field blank.

Document Was Updated After Scenario Setup

If you update the Wauld document after turning on the scenario, the scenario may need to be reviewed. For example, if you add new custom attributes, rename existing attributes, or remove attributes, the Make module may still use the older configuration.

Open the scenario, review the Wauld module, update the field mappings if needed, save the module, and run the scenario again.

Document Is Deleted or No Longer Available

If the selected Wauld document is deleted or becomes unavailable, the scenario may fail.

In this case, open the Wauld trigger or action module, select an active document, save the module, and test the scenario again.

Managing Make Access in Wauld

You can manage Make access from the Make details page in Wauld. Go to: Wauld > Integrations > Make

From this page, you can regenerate or revoke the Make 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 Make connection using the old token may stop working until the connection is updated with the new token.

Revoke Token

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

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

Best Practices

1. Test with sample data before turning on the scenario
   Always test your scenario using realistic sample data before enabling it.

2. Click Run once before testing trigger modules
   When testing Wauld as the trigger, Make should be in listening mode before you issue the test credential in Wauld.

3. Use clear field names in connected apps
   If you are using spreadsheets or forms as triggers, use simple field names such as Recipient Name, Recipient Email, Course Name, Completion Date, Score, and Expiry Date.

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

5. Use exact custom attribute names
   When adding custom attributes in the Wauld action module, enter the exact attribute names used in the selected Wauld document.

6. Review scenarios after document updates
   If you update the selected Wauld document, review any related Make scenarios to make sure the fields still match.

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

8. Monitor Make execution history
   Failed runs and field mapping issues are usually shown in Make. Review the execution history if a scenario does not work as expected.

9. Protect your Make access token
   Treat the Wauld Make access token like a password. Do not share it publicly or store it in unsecured locations.

Summary

The Wauld Make 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 Make, you can reduce manual work, improve reporting, notify teams, and automatically issue credentials based on activity in other systems.