Chameleon's Zapier integration leverages the "Webhooks by Zapier", which is a premium functionality in Zapier.

A native integration that allows you to find a Chameleon listing within Zapier is something we're aiming towards, so we encourage you to let us know about your needs.


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).


How this integration works

This integration leverages our Outgoing Webhooks functionality, which allows you to send data to other services and works based on topics. Currently, we offer 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 by leveraging these, feel free to get in touch with us and we'll explore your options together.

👉 Know more about what's possible with Chameleon's Webhooks

Example use cases

Using the above webhook topics opens a range of possible use cases for which you could leverage this Zapier integration. Some include:

  • 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 for targeting Experiences

  • Send user attributes to Chameleon to personalize content within Experiences


Setting up the integration

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

We'll outline each of these in detail below.

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 in the Outgoing Webhooks view on your Chameleon Dashboard. Here, you'll also determine 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.trychameleon.com/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 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 the Chameleon interface) 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>

Perfect, your Zap is ready to go!
You will be able to use this data being sent to Chameleon when creating a Target Audience by using "Imported properties" if sending user properties, or "Imported events" if sending user events.

👉 Learn more about setting up a target audience.


What else?

Did this answer your question?