1. Home
  2. Connect Any App With Smart Webhooks

Connect Any App With Smart Webhooks

You may have seen “webhooks” mentioned in apps you use, and wondered what they are and if you should use them. The answer is, probably, yes. Webhooks are a way in which apps send information to other apps.

In Nudgify, we have a Smart Webhooks feature which makes it extra easy to send information from other apps to Nudgify. You can then show this information in Purchase Nudges, Sign-ups Nudges, or Review Nudges.

What are Webhooks?

There are two ways in which apps can communicate with each other: via polling and via webhooks. With polling, you actively need to keep checking if something new has happened yet. With webhooks, you get notified automatically when something new happens.

Simply put, polling is you actively asking your colleague for updates every day. Some days they have an update for you, other times, you ask but they have nothing new to report. Webhooks is automatically receiving an update from your colleague every time they have something new to share. You don’t have to ask.

An app that gives updates to another app via a webhook, has, as it were, that apps “phone number”. That is how it knows where to send the updates to. This “phone number” is a URL, also called a “Webhook URL”, or “endpoint”.

Webhooks are incredibly useful for a lot of different scenarios, and as such, a lot of apps support webhooks. This is great, because it allows all these apps to communicate easily with Nudgify!

For apps, supporting webhooks is like owning a phone. If I own a phone, and you own a phone, we can communicate! All you need in order to call me, is my phone number! Similarly, if Nudgify supports webhooks, any app that also supports webhooks can “call” Nudgify. All you need to do, is give Nudgify’s “phone number” (Webhook URL) to the app you’d like to connect to Nudgify.

What are Smart Webhooks in Nudgify?

When you use Nudgify, you can use webhooks to notify Nudgify every time something happens in another app that you use. For example, every time you have a new purchase in ClickFunnels, or someone submits a JotForm, or you receive a new review via Stamped.io. You can then show this information in your Nudges.

Nudgify’s Smart Webhooks feature makes it extra easy to set up a webhook connection, and show the information you want in your Nudges. In this article, you read how you can use Smart Webhooks to connect your data to your Purchase Nudges, Sign-ups Nudges, and Review Nudges.

Which apps can I connect via Smart Webhooks?

Smart Webhooks allow you to connect data from any app to Nudgify. The only requirement is that the app you want to connect supports webhooks. A lot of apps do not only support webhooks, but also offer a simple, code-free way to add a webhook. A simple Google search of “webhooks” + “app name” will tell you quickly if the app you’d like to connect supports webhooks. If it does, you probably find the relevant webhook instructions as one of the first hits in the search results.

To make it easier, we have created specific instructions on how to set up a Smart Webhook with some popular apps:

How do I create a Smart Webhook?

To create a new Smart Webhook, navigate to Integrations > Smart Webhooks

create webhook

Step 1: Select data type
Select the data type you’d like to connect. Is it data you want to show in Purchase Nudges, Sign-up Nudges, or Review Nudges?

webhooks data type

Step 2: Name your Smart Webhook
Give your Smart Webhook a name. We recommend naming it after the app that you are connection, e.g. “ClickFunnel Sign-ups”.

Step 3: Copy paste your Webhook URL
You now see the unique Webhook URL for the Smart Webhook you’re creating. This Webhook URL is the “phone number” that you’ll need to give the app you want to connect. This way, your other app will know where to send the updates (e.g. new orders, sign-ups etc) to. You need to copy this Webhook URL and paste it in the right place in the app you want to connect to Nudgify.

webhook url

This is different for each app you want to connect. The best way to find out what to do with the Webhook URL you just copied, is to Google “webhooks” + “app name”. This should present you with the webhook instructions for the app you’re connecting. For many apps, this will look something like this example from Webflow:

  • You can select the type of event your app should update Nudgify about, in this example “Form submission”
  • You have a field where you can paste the Nudgify Webhook URL

This way, every time a new Form submission comes through, Webflow will tell Nudgify about it and send some relevant data (such as the name of the person who submitted the form and when it was submitted).

Step 4: Send sample data to your Webhook
Now that your Smart Webhook URL has been saved, your app has Nudgify’s “phone number” and knows what type of updates Nudgify is interested in. Now it’s time to send a test update to Nudgify via the webhook, and see what information comes through in the update. This is an important step in the process of setting up your Smart Webhook, because it lets you “map” which information you want to show in the Nudge.

Depending on the type of event it is (a new order, a sign-up, a review), different data can come through via the webhook, such as the name of the customer, the name of the product they purchased, the number of stars in the review etc.

You can send sample data to your webhook by triggering the event that you selected for your webhook. If this is a form submission, to a test submission of your form. If this is a new purchase, place a test order. Once you’ve triggered this event, click the Check for data button in Nudgify. If you’ve indeed triggered the right event, the update including the relevant information was sent to your Smart Webhook in Nudgify and the data will appear below your Webhook URL.

webhook data received

If no data was found, this means that you haven’t triggered the right event, or you have not set up the Webhook URL for that event. You can double check and adjust your set-up, and then click Check for data again.

webhooks no data

Step 5: Map your sample data
In this step, you tell Nudgify which pieces of data to use in your Nudge. Which bit of sample data is the customer name? Which bit is the name of the product they purchased? And so on. You use the drop downs to select the right bit of sample data for each field.

Mapping the data is something you do one time. Once you have “mapped” the sample data for your Smart Webhook, any new purchases/sign-ups/reviews that this webhook sends to Nudgify will show the correct bits of data in the correct places of the Nudge.

Note: Nudges can only display data that is sent by the third party app you connect via the webhook. If the app you connect does not provide e.g. the location of the customer, then Nudgify won’t be able to display the location in a Nudge.

Step 6: Save your Smart Webhook
In this last step, you see an overview of your Smart Webhook: the name of your Smart Webhook, its data type, the Webhook URL, and your data mapping.

webhooks overview

To save your webhook, click “Save”. You can always return to this overview and make changes to the set-up of this Smart Webhook by clicking the pencil icon on the Smart Webhooks page.

edit smart webhook

That’s it! You’ve created your Smart Webhook!

Step 7: Show your Smart Webhook data in Nudges
Congratulations, you have created a Smart Webhook! On your Data Feeds page, you can see the data that is connected to Nudgify via your Smart Webhook in the relevant Data Feed tab (Purchases, Sign-ups, or Reviews).

You can now display this data in Purchase, Sign-up, and Review Nudges respectively, by selecting your Smart Webhook as the data source when you set up the Nudge. For example, if you created a Smart Webhook for Purchases, this Smart Webhook now appears in the dropdown among the Data Sources you can select for this Nudge.

webhook data source

When you select it as the data source, the Nudge will display the data that comes through to Nudgify via your Smart Webhook.

What if not all the bits of data are there?

Smart Webhooks allow you to connect any third party app that also supports webhooks. Every app will handle webhooks slightly differently and send different bits of data along with the webhook. For example, some apps might send the First Name and Last Name of the person who signed up, other apps might send the Full Name. Some apps might not send a name at all.

As a general rule, Nudgify is not able to show any data that is not there. So if the third party app does not send the customer name along via the webhook, then we are unfortunately not able to display the customer name in the Nudge. Below, you find an overview of the impact if different bits of data are missing:

Data Type: Purchases

Data fieldDescriptionImpact if missing
DateThe date we use to show in the Nudge how long ago the purchase took placeWe use the moment the order came through to Nudgify via the webhook as the "fallback" date
EmailThe email address of the user to identify that there has been a new purchaseRequired! We use the email address as identifier. Without the email, we can't show the purchase in Nudges
Order IDThe order-id we use to identify which items are part of the same orderRequired! Without the Order ID, we can't show the purchase in Nudges
First NameThe first name of the customer, to show in the NudgeWe do not display the customer name in the Nudge, unless you use the "Full Name" field
Last NameThe last name of the customer, to show in the Nudge (we only show the initial of the last name)We do not display the customer name in the Nudge, unless you use the Full Name field
Full NameThe name of the customer, to show in the NudgeWe do not display the customer name in the Nudge, unless you use the First + Last Name fields
CityThe city of the customer, which we show in the NudgeWe do not display the City in the Nudge, unless you use the IP Address field
StateThe state of the customer, which we show in the Nudge (for US)We do not display the State in the Nudge, unless you use the IP Address field
CountryThe country of the customer, which we show in the Nudge (note for the US we use State instead)We do not display the Country in the Nudge, unless you use the IP Address field
IP AddressThe ip address of the customer, to show the location in case City/State/Country are not availableWe do not display the customer's location in the Nudge, unless you use the City/State/Country fields
Product IDThe id we use to identify the product that was orderedWe do not display any product information
Product Variation IDThe id we use to identify the variation (colour, size etc.) of the product that was orderedWe do not take into account different variants of the product
Product NameThe name of the product that was ordered, to show in the NudgeWe do not display the product name in the Nudge
Product Page LinkThe product page that we link to from the item name in the NudgeWe do not link to the product page from the product name in the Nudge
Product Image URLThe product image that we show in the NudgeWe do not display the product image in the Nudge

Data Type: Sign-ups

Data fieldDescriptionImpact if missing
DateThe date we use to show in the Nudge how long ago the sign-up took placeWe use the moment the sign-up came through to Nudgify via the webhook as the "fallback" date
EmailThe email address of the user to identify that there has been a new sign-upRequired! We use the email address as identifier. Without the email, we can't show the sign-ups in Nudges
First NameThe first name of the user, to show in the NudgeWe do not display the user's name in the Nudge, unless you use the "Full Name" field
Last NameThe last name of the user, to show in the Nudge (we only show the initial of the last name)We do not display the user's name in the Nudge, unless you use the Full Name field
Full NameThe name of the user, to show in the NudgeWe do not display the user's name in the Nudge, unless you use the First + Last Name fields
CityThe city of the user, which we show in the NudgeWe do not display the City in the Nudge, unless you use the IP Address field
StateThe state of the user, which we show in the Nudge (for US)We do not display the State in the Nudge, unless you use the IP Address field
CountryThe country of the user, which we show in the Nudge (note for the US we use State instead)We do not display the Country in the Nudge, unless you use the IP Address field
IP AddressThe ip address of the user, to show the location in case City/State/Country are not availableWe do not display the user's location in the Nudge, unless you use the City/State/Country fields

Data Type: Reviews

Data fieldDescriptionImpact if missing
DateThe date we use to show in the Nudge how long ago the sign-up took placeWe use the moment the sign-up came through to Nudgify via the webhook as the "fallback" date
RatingThe number of stars of the review, to show in the NudgeRequired! Without the rating, we can't show the reviews in Nudges.
Name of ReviewerThe name of the reviewer, to show in the NudgeWe do not display the reviewer's name in the Nudge
Image of ReviewerThe image of the reviewer, to show in the NudgeWe display a star icon in the Nudge instead of an image of the reviewer
Review TitleThe title of the review, to show in bold in the NudgeWe do not display a review title in the Nudge, just the main review text
LanguageLanguage of the reviewWe try to only display reviews in the language you selected for your Nudges. If this is missing, we display reviews in any language
Review TextThe text of the review itself, to show in the NudgeWe do not display a review text in the Nudge

 

 

Updated on June 17, 2022

Was this article helpful?