Skip to main content

Zapier

Self Hosted
Not available in WorkAdventure Self Hosted
 Free
Not available in WorkAdventure SaaS Free Plan
 Premium
Available in WorkAdventure SaaS Premium Plan

WorkAdventure provides a Zapier app. Your zaps can create / retrieve / delete members, and start when something happens in your world: a recording is ready, a visitor signs up, someone changes their consent.

Note

Zapier is great for "no-code" integrations. If you are a developer, you can create / retrieve / delete members directly in WorkAdventure using our REST API.

How to bind WorkAdventure to Zapier​

Go to your Zapier account in "My Apps". Click on "+ Add connection"

My Apps zapier

Search the "WorkAdventure" application and click on it. A new tab "Connect an Account | zapier" will open. In this tab you need to fill:

  • the World Slug
  • the Authorization token

Zapier connection page

All the pieces of information you need to find to fill this screen are located in the WorkAdventure admin dashbord, in the Developers > API keys / Zapier page (in the left sidebar).

In this page, you will need to:

  1. Create a new token: In the "API Tokens" section, create a new token.
  2. Enable the "Inbound API"

When this is done, the Zapier section of the "developer account" will contain all the data you need.

Copy and paste the token and the world slug to the Zapier configuration page.

Click on Yes, Continue and your Zapier connection to WorkAdventure will be setup 🚀

Zapier my app connected

Create your zap​

To create your zap, go in "Zaps" and follow the instructions to create your first zap with Zapier. WorkAdventure provides the following actions:

  • Create or update a member: if a member with this email already exists, all their fields are overwritten
  • Update a member: only the fields you fill in are changed
  • Delete a member
  • Find a member by UUID or email (a search: it does not fail when the member does not exist)
  • List the members and/or visitors of your world

Members returned by these actions include their private access link to each room of your world, ready to send by email.

Start a zap from a WorkAdventure event​

WorkAdventure provides these triggers, fed by its webhooks. Zaps start the moment the event happens:

  • New Recording: a recording of a meeting is ready. Its download link is valid for 7 days, so copy the file (to Google Drive, for instance) rather than the link.
  • New Visitor: a visitor signed up.
  • New Consent Decision: someone gave, refused or withdrew their consent to one purpose (newsletter, events…). Stop using their data for that purpose when Granted is false or empty.
  • New Member Connection: someone connected to your world. Your zap runs once they are in, so it cannot change their tags for this connection (an n8n workflow can). If your SSO exposes OAuth access tokens, they are part of the event, and Zapier keeps them in your zap history.

When you test the trigger in Zapier, it shows a sample event. Turning the zap on creates a webhook in your world, which you can see in Developers > Webhook settings. Turning it off deletes it. If WorkAdventure disables that webhook after repeated failed deliveries, re-enable it on its page. If you delete it or generate a new secret, turn the zap off and on again. Test events sent from the webhook's page in WorkAdventure don't start the zap.

The analytics subscription has no trigger: it sends many events per hour, and each one would count as a Zapier task.

:::info Need help 🆘

Contact us or write us to [email protected]:::