Zapier integration

Zapier is an integrated app that we offer out of the box. Setting up zapier allows us to send JSON payloads to your Zapier endpoint. Within Zapier, you can decide how to distribute our various message types.

You can repeat this as often as you want, although only once per account. We do send different payloads per message type, allowing you to distribute accordingly.

From the dropdown, you can install an app. Zapier will be amongst the default integration options. After clicking on Zapier, a popup will be shown.

Providing the Zapier endpoint

In the popup, you should provide the endpoint of your Zapier configuration. This could be an existing endpoint. See the screenshot below, which is showing the popup and the two form fields:

  • an input for your Zapier endpoint URL.

Setting up Zapier

Before performing the above step within RUMvision, you first need a Zapier Webhook URL. The steps below describes how to set up Zapier and get a Webhook URL. This excludes the registration and login process within Zapier.

While you don't necessarily need to know technical details of (Zapier) Webhooks, you could learn more about webhooks by reading Zapier's helpdesk.

Creating a Zap

Within your Zapier dashboard, create a new Zap from the "Create" dropdown button.

Configure a trigger

When on desktop, a new screen will show up at the right with the option the configure a trigger and action. The action part is up to you, as you can decide how to distribute any incoming information send by RUMvision.

However, the trigger is the part that is going to receive the information. If you see the options as illustrated in the above screenshot, click on "trigger".

Choose webhook

A pop-up will then appear. Search for "webhook" in this pop-up and select "Webhooks by Zapier".

Webhook event

The pop-up will disappear and a new panel will appear at the right. In the "App & event" panel you'll see your choice being confirmed. There's a required field called "Event". Over here, select "Catch hook".

This is a Webhook that will perform your action instantly once it has been received by Zapier. it will wait for any new POST, PUT or GET requests to your Zapier Webhook URL.

Webhook url

Zapier should now have created a personal Zapier Webhook URL as well. Navigate to the "Test" panel that can be found at the right. You should then see an interface as illustrated in the screenshot below:

This is the URL you should copy and then paste into RUMvision when adding Zapier to your apps.

Configuring filter conditions

Once you shared your Zapier Webhook URL with RUMvision, we'll be sending all message types you subscribed to to that specific URL. However, you might want to perform different actions with different message types. This is where filters and conditions come into play.

Add a step

You might have added a final (or multiple) action already. Such as sending the information to an e-mail address via Gmail. But you might not want to do this for all incoming messages. To achieve this, you should add another step that instructs Zapier to only continue when a specific condition is met. The screenshot below is illustrating how that would look like.

You can start doing the same by clicking on the plus-sign saying "Add a step".

Choose action

An pop-up will open where you can choose your action. This same screen can be used to configure your final action(s), such as sending via Gmail or forwarding details to Trello. However, to actually add a condition, you will need to use filters.

Search for "filter" in the pop-up. You should be presented with an option called "Filter by Zapier".This is illustrated in the screenshot below.

Click on that action, which will close the pop-up and will lead you to a new panel at the right.

Configure the condition

The panel that opens allows you to configure statements. It is convenient to have received a first message of a specific message type. But you could also start with a test as described in the next chapter.

Learn more about the formatting of our JSON payloads in our Webhooks section.

If you have familiarized yourselves with our various JSON payloads already and are familiar with statements and conditions, you might be able to configure multiple conditions without needing to wait for our various message types.

For this example, let's assume that a user made a change to their tracking configuration while using our JavaScript integrity security measure. This means that the site owner needs to update their installed snippet to apply the new security hash. Luckily, Zapier can be used to forward such a task to your in-house (maybe already automated) process or send the new snippet to your tag manager implementation partner.

Writing the condition is illustrated in the screenshot below.

When nothing was supplied yet, the three fields will be blank with the following placeholders (in order of the fields):

  1. Choose field
    Based on our payload for changes in SRI hash, you should use the action
  2. Choose condition
    Then select "contains" or "equals".
  3. Enter text or insert data
    Over here, fill in hash as we'll use that as the value for action

When pressing the purple "Continue" button at the bottom, Zapier should automatically run a test and provide you with feedback. As can be seen in the screenshot, our test was successfull and this would be ready for production.

Forward to mail, Trello or ..

After adding filters, you would want to do something with our message details. We've mentioned a few scenarios already.

Different scenarios

You might want to:

  • adding information to Trello;
  • forward a message to your own webhook;
  • or -as most of our payloads will contain a formatted message (msg) as well, forward any request with a msg field to an e-mail address.

Pre-filled messages

Whatever your need is, Zapier offers the ability to re-use the information in our payload to pre-fill your e-mail messages, Trello tickets and other tasks within the same user interface as illustrated and shown in the earlier Zapier sections.

App options

After installation, you can test, pause or delete the webhook.

Testing the webhook

You can test the webhook by sending a test message. You should be able to see this option when going to the apps dropdown menu. Over there, click on "send test message" to send a test message right away. Testing Zapier also allows you to test a bit more within the Zapier dashboard. For example, when you're still in the "Test" panel within your Zapier dashboard, you should see your test message.

For example, when configuring your "action" (which comes after the trigger), you could use Gmail to re-use and send specific fields to an e-mail address.

Pausing the webhook

Via the same dropdown menu, you will be able to delete the whole connection between RUMvision and your Zapier Webhook. Instead of deleting it, you can also disable notifications. This might be convenient when you just want to pause reports and messages, without needing to delete it all together.

The screenshot below is illustrating where you can find the dropdown menu with its options:

Deleting the Zapier webhook

When deleting the Zapier webhook, a message will be send to the webhook that was used during the configuration. The webhook will be removed and will no longer receive notifications.