Webhooks are a way to send data between services in a real-time manner, with simpler configuration than using APIs. If you are an engineer looking to use webhooks then you check out the webhooks section in our Developer Hub.

Chameleon offers support for webhooks in two ways:

  1. Update user data within Chameleon using Incoming Webhooks
  2. Send Chameleon Microsurvey responses to other services using Outgoing Webhooks

You can get to the Chameleon webhooks configuration page from the Integrations section in your Chameleon dashboard:

From within the webhooks page, you'll see two sections, corresponding to Incoming and Outgoing Webhooks.

Incoming Webhooks

To use incoming webhooks, you will need to add the Chameleon webhook URL into the configuration page for the service sending the webhook.

For example, if you would like to send data from Marketo to Chameleon, you would need to configure the webhook within Marketo, and use the Chameleon end-point webhook URL there.

There are three types of data you can update within Chameleon using incoming webhooks.

  • User properties
  • Company properties
  • User events

You should use the corresponding incoming webhook URL when adding it to the sending service. Simply hit "Copy" to grab this URL (which contains authentication for your account) and paste it into the sending service's configuration field.

Read more about limits and normalization of names in our Developer Hub here.

Outgoing Webhooks

Outgoing webhooks can deliver data about Microsurvey responses to other systems. This includes:

  • Microsurvey identity (see info here)
  • Microsurvey Response (see detailed schema here)
  • User identity (see info here)

This can be useful to consolidated user feedback or preferences into your database, or to leverage other tooling to further engage and communicate with users based on their responses.

To send Chameleon Microsurvey response data to another system, click "Add webhoook", to open a modal, where you can input the receiving system's URL:

Name your webhook to make it clear to others how it's being used, and then add the endpoint URL.

You can use the Account Secret to verify the identity of your webhook (recommended). Read more about verification here.

Did this answer your question?