With our Zapier integration, you can trigger Chameleon events to send data to Zapier, as well as repurpose your Zapier data with Chameleon for efficient guidance.


Availability & Usage

🧪 BETA for all plan levels

💲 Zapier webhooks

📍 Ready to use in Tours, Microsurveys

🧑‍💼 Chameleon Admins (*if roles are enabled)


You can leverage Zapier to include Chameleon into your workflow and have it communicate with other tools. By leveraging our Zapier integration, you will be able to use Zapier as a:

  • Data destination, to send Chameleon data (e.g. Microsurvey scores) to Zapier and use it as triggers.

  • Data source, to get Zapier data into Chameleon (using Chameleon as an action).


Quick access


How this integration works

With the Zapier Integration, you can set up Zaps to trigger whenever a user performs an action, as well as to update user attributes in Chameleon. You can trigger Zaps for the following topics:

  • Microsurvey submitted

  • Button clicked *

  • Tour started *

  • Tour completed *

  • Tour exited *

  • Tour snoozed *


Note: The above topics marked with * are only available on the Growth Plan. If you'd find value in leveraging these, feel free to get in touch with us and we'll explore your options together.


You can also use Zapier Actions to update in Chameleon:

  • a user's profile;

  • company data.

This allows you to further personalize the Experiences your users see and create a better user journey.

Example use cases

You can Leverage the Zapier integration to:

  • Send Chameleon Microsurvey responses to other tools or systems. You can even send responses to an email address.

  • Trigger other systems based on Chameleon data, for example, to send an email when a Tour is completed or dismissed.

  • Send product events to Chameleon to use when targeting Experiences.

  • Send user attributes to Chameleon to personalize content within Experiences.


Setting up the integration

To configure and use this integration, go to the Integrations page in the Dashboard, find Zapier and click "Configure" to set up your data flow, by enabling the toggle.

Configuring your Zap

There's no other configuration needed to connect Zapier to Chameleon, and you can go on to add and configure the triggers from your Zapier dashboard. Search for Chameleon and choose the 2nd result -- with the Chameleon logo.

Next, you'll have to pick the event from Chameleon that will trigger your Zap, from Microsurvey responses to Tour button clicks.

As we want to help you keep essential information on your radar, next, you'll pick from a dropdown list the specific Experience you want to leverage with your Zap. Clear naming conventions across the board will go a long way here. 😉

Once you've set up your event and trigger, you can also test out your Zap to ensure it works as expected. Green lights? Perfect, your Zap is ready to go!


Note: The data you'll preview here is not an accurate depiction of your Chameleon data.


Leverage Zapier Actions

After you've set up a Zap, you can configure an Action that will trigger once the Zap has started. This helps you send essential data to Chameleon about the users who trigger that Zap, and you can further leverage that down the road. With this option, you can update a user's profile in Chameleon, as well as company (group-level) data.

You can also use this option to filter out feedback you'd want to jump on. For example, if you have a rating Microsurvey set up, you could choose to update the profile of those who gave a poor rating, so you can better engage your users.


Send data using Webhooks

You can also leverage Webhooks to connect Zapier, but this is a premium functionality in Zapier.

Having in mind that data can flow bidirectionally between Zapier and Chameleon, there are two different routes you can take:

  • Setting up Chameleon as a Zapier Trigger

  • Setting up Chameleon as a Zapier Action

Using Chameleon as a Zapier Trigger

You can send Chameleon data to Zapier. To do this, you will use “Webhooks by Zapier” as the trigger application. Search for this in your Zapier account:

Then select the action application. Depending on your use case, this could be “Send emails...”, “Get Slack notifications...”, “Make Hubspot form submissions...”, etc.

You will then see the following configuration section for the Webhook:

Here, you are presented with your own Custom Webhook URL, which you will need to paste into the Outgoing Webhooks section on your Chameleon Dashboard. Click "Add webhook" and also pick which topics you want to send to Zapier and select an identifiable name for your webhook endpoint.

Once you've saved your webhook, it's time to test if everything's working. Go ahead and use a test Chameleon Experience to see if data is flowing from Chameleon to Zapier.


Note: Upon refreshing Zapier, you should also see a 'ping' payload, which is sent as a check to confirm that everything's working.


Once connected, this will then send a webhook to Zapier whenever an action related to your webhook topic occurs within Chameleon. For example, for the Microsurvey submitted topic, information relative to the completed Microsurvey is sent to Zapier, such as:

  • User ID of individual that completed the Microsurvey

  • Microsurvey details (e.g. Microsurvey name, type, etc.)

  • Response details (e.g. button text, input text, page URL, etc.)

Using Chameleon as a Zapier Action

You can also push data to Chameleon from Zapier. This is done by selecting “Webhooks by Zapier” and configuring “POST” events to Chameleon’s APIs.

To configure this, you can use the following details:

  • URL: This should correspond to the webhook endpoint URL, which you can grab from your Chameleon Dashboard. These are unique per account and look like: https://api.chameleon.io/v3/observe/hooks/*****/events.

  • Payload type: JSON

  • Data: Here you can add the data that should be sent to Chameleon whenever this Zap runs. For example, this could update a user's attributes or cause Chameleon to register an event.

  • Header: No specific Headers are required. Authentication is built into the Endpoint URL (which contains your unique Chameleon token).

What data to send?

One piece of data you will need to send to Chameleon is the uid, and it must match the User ID you are sending to Chameleon as part of the installation. We will use this to map the data received via Zapier to the right user in Chameleon.

You can add other data too; add the name of the event or attribute (you will use this to search and select this event in Chameleon) and then the values for this (likely to be variables pulled from the connected Trigger app).

You can keep the other configuration parameters as-is:

  • Wrap Request In Array: No

  • File: <blank>

  • Unflatten: Yes

  • Basic Auth: <blank>

That's it, your Zap set up!

You will be able to use this data when creating an audience Segment in Chameleon by using "Imported properties" if sending user properties, or "Imported events" if sending user events.


What else?

Did this answer your question?