Overview: Inbound webhooks (Edify Console)

Edify Console > Integrations > Overview: Inbound webhooks (Edify Console)

This article explains the Inbound Webhook workspace in Edify Console.

Overview

The Inbound Webhook workspace in Edify Console (Account > Integrations > Inbound Webhook).

In Edify Console, the Inbound Webhook workspace is where you create and configure inbound webhooks. An inbound webhook is a way of sending data from an external CRM, API, or other application directly to an Edify workflow for processing.

A webhook is a tool that sends data from one application to another. Edify calls them inbound webhooks because Edify, via the webhook, receives information. In other words, the information is inbound to Edify.

When an inbound webhook receives data, it triggers a workflow to run. The workflow will then run and process the data to meet your needs.

Types of inbound webhook

Inbound webhooks are classified by type. The type of inbound webhook determines the format used to send data to Edify. There are four types of inbound webhooks:

Continue reading the subsections below to learn more about each type of inbound webhook. 

See the How to set up an inbound webhook section for links to articles that walk you through the inbound webhook setup process.

Salesforce inbound webhooks

A Salesforce inbound webhook is an inbound webhook that receives data from Salesforce. You can configure Salesforce to either automatically or manually send data to Edify based on a number of triggers, like:

Setting up a webhook between Salesforce and Edify requires some configuration. A tutorial article on this is coming soon!

Zendesk inbound webhooks

A Zendesk inbound webhook is an inbound webhook that receives data from Zendesk. You can configure triggers and automations in Zendesk that automatically send data to Edify whenever something happens in Zendesk. For example, when a ticket is created in Zendesk, you can configure Zendesk to use the webhook to automatically send data to Edify.

Setting up a webhook between Zendesk and Edify requires some configuration. To learn more about how to do this, see the article: Tutorial: Setting up an inbound webhook from Zendesk.

CSV inbound webhooks

A CSV inbound webhook is an inbound webhook that receives data in the form of a CSV (comma separated value) file. This type of webhook is most useful when you want to import bulk data from another application. When you use a CSV inbound webhook, the workflow runs for each line in the CSV file.

As an example, let’s look at the sample CSV file below.

firstName,lastName,favoriteColor

Isaac,Newbury,blue

Bennie,Franks,green

Stefan,Hawkston,yellow

Example of a CSV file

For a simple example, suppose you wanted to create a workflow that would send an SMS containing someone’s name and favorite color. The headers indicate the names of variables you could put in the workflow. 

If this file were sent to a workflow, it would run three times – once for each row (excluding the header). The following is an example of the text that could be configured in the Send SMS workflow module:

“Hi! My name is {{firstName}} {{lastName}}. My favorite color is {{favoriteColor}}.

These are the text messages the workflow would produce:

“Hi! My name is Isaac Newbury! My favorite color is blue.”

“Hi! My name is Bennie Franks! My favorite color is green.”

“Hi! My name is Stefan Hawkston. My favorite color is yellow.”

This is useful for putting large amounts of data into Edify. 

For an example of a real world use case: Suppose you have a bulk list of call information. You want to create a list of outbound calls in a queue for agents to handle. You could use the inbound webhook to import a CSV of call information into a queue via a workflow.

To learn more about setting up an inbound webhook for CSV files, see the article: Tutorial: Setting up an inbound webhook for CSV

Generic inbound webhooks (JSON / XML / form-data)

Finally, you can use a generic inbound webhook as an alternative to the options listed above. A generic inbound webhook accepts data formatted in JSON, XML, or form-data.

Below are three examples of sample data that could be sent to Edify via an inbound webhook. They are:

You can configure the workflow to use variable replacement to take data sent via the inbound webhook for use in the workflow.

{

"firstName": "Isaac",

"lastName": "Newbury",

"favoriteColor": "Blue"

}

Example of JSON

<firstName>Isaac</firstName>

<lastName>Newbury</lastName>

<favoriteColor>Blue</favoriteColor>

Example of XML

<form method="POST" action="https://sandbox-hooks.edifylabs.net/inboundWebhooks/012345">

  <input type="hidden" name="garbo" />

  <input type="hidden" name="edifyRedirectUrl" />

  <input type="text" name="firstName" />

  <input type="text" name="lastName" />

  <input type="text" name="favoriteColor" />

</form>

Example of form-data

Note: The garbo field is a honeypot and should be left blank. If the edifyRedirectUrl value is provided, Edify will perform an HTTP redirect after receiving the event.

To learn more about setting up a generic inbound webhook for JSON and XML, see the article: Tutorial: Setting up a generic inbound webhook

How to set up an inbound webhook

Click any of the links below to follow tutorial articles on how to set up inbound webhooks.

Visual breakdown

Inbound webhook configuration list

Inbound webhook configuration page