Skip to content

Zapier integration

Zapier connects Wasp Asset to thousands of other apps without any code. You build a Zap: a workflow where something happening in one app (the trigger) makes something happen in another (the action). For example, you can email your team when an asset is created, or create an asset in Wasp Asset when a row is added to a spreadsheet.

  • Zapier requires the Complete edition. The Wasp AssetCloud Zapier app signs in with a public API token, and Wasp Asset events reach Zapier through Callouts. Both are Complete-edition features.
  • A Zapier account. Sign in at zapier.com.
  • An API access token and your Wasp Asset address (for example https://yourcompany.waspassetcloud.com/). See API access tokens.

This example sends a Gmail message when an asset is created. Zapier’s screens change from time to time, so the labels you see may differ slightly.

  1. In Zapier, create a new Zap.
  2. For the trigger, search for and choose Wasp AssetCloud, then choose the event, for example Asset Created. Click Continue.
  3. Connect your account: click Sign in, enter your Tenant URL (your Wasp Asset address) and your API Token, and click Yes, Continue. Zapier confirms the connection succeeded. Click Continue.
  4. Click Test trigger. Zapier finds a sample record and shows the fields it contains, so you can use them in the action. The values are sample data.
  5. For the action, choose the app you want to notify, for example Gmail, then the action, such as Send Email. Click Continue.
  6. Sign in to that app’s account.
  7. Fill in the action’s fields. Click in a field to insert values from the Wasp Asset trigger (asset tag, description, and so on). Click Continue.
  8. Click Test action to send a test, then Publish to turn the Zap on.

The Zap now appears on your Zapier home screen and runs every time the event happens.

When you turn on a Zap that uses a Wasp Asset trigger, Zapier registers a callout in your account automatically. You’ll see it on the Settings gear → Callouts page.

You can edit these callouts to narrow what reaches Zapier. For example, if your Zap fires on Asset Checked Out, you can add a filter to the callout so it fires only for check-outs to a particular employee or for a particular asset. You get the full power of callouts without handling URLs yourself.

Send data from another app into Wasp Asset

Section titled “Send data from another app into Wasp Asset”

You can also use Wasp Asset as the action, for example to create an asset whenever another system sends Zapier a record. This example uses Webhooks by Zapier as the trigger, so any system that can make a web request can feed it.

  1. Create a new Zap. For the trigger, choose Webhooks by Zapier with the event Catch Hook. Click Continue.
  2. Optionally, under Pick off a Child Key, enter the name of the part of the incoming data that holds the record. Click Continue.
  3. Copy the webhook URL Zapier shows you.
  4. Send a sample record to that URL from the other system, or from a tool such as Postman: a POST request with a raw JSON body containing the fields you’ll map, such as the asset tag, description, site, and location.
  5. Back in Zapier, click Test trigger. Zapier shows the request it received. Click Continue.
  6. For the action, choose Wasp AssetCloud and the action Create Asset. Choose the account you connected earlier and click Continue.
  7. Map each Wasp Asset field to a value from the incoming data. If Zapier can’t load the choices for a field, switch to the Custom tab and pick the value there. Click Continue.
  8. Click Test action. Zapier reports that the asset was sent to Wasp AssetCloud.
  9. Click Publish to turn the Zap on.

To confirm it worked, open History in Wasp Asset and look for the new asset’s creation.