Last week we laid out the general idea of the possibilities that webforms can bring to the Flexfer CRM. In today’s blog, we are going to discuss how to set up an endpoint in the Flexfer CRM so it can accept data from a Jotform webform.
During this post, I will assume you already know how to build a Jotform webform, or have one standing by. Try them, it’s free!
The Endpoints screen allows you to easily set up new Endpoints and review or edit your older and currently active Endpoints. This screen can be found in the left menu bar, where the option looks as follows:
When creating a new Endpoint, you will need to set it up with some relevant information: what text do you wish to be used for the webhook, and what kind of Endpoint do you wish to make? In order to make a Jotform endpoint, of course you will need to choose the Jotform option. However, you can also choose to make a more generic json data endpoint that can receive data from any webform that can send json-formatted data.
After having set up the Endpoint, your screen will look like this:
Clicking on the ‘copy link’ button will automatically copy the address of your Endpoint to your clipboard. This allows you to take the address to, in this case, Jotform, so they know the address to which the form has to send the submissions.
Setting this up is a simple matter of going to the ‘Integrations’ screen in Jotform and pasting the Endpoint address in the Webhooks option. After confirming, your Jotform webform is ready to send data to the Flexfer CRM Endpoint.
To set up the Jotform data for automation, you will need to tell the Endpoint what data to expect and how to interpret this. This is the easiest by actually filling the webform out with sample data and sending this sample data to the Endpoint.
As long as the Endpoint is not set ‘Active’, it will receive this data and set it in the ‘Sample’ block on the endpoint page, which means the following form:
Will look like this in the Endpoint screen:
At this point, you can start creating Variables to contain the data from the Webform, or to contain static data specific to the Endpoint. You can do this by clicking on the ‘Add’ button at the top of the screen, which opens a pop-up asking you for a name, variable type, and, if possible, a default value for the variable.
If you select the ‘Lead’ datatype, it will allow you to match to several tables in the Match step of the Workflow, which we will discuss in the future. It also allows you to contain data coming from most types of contact forms. When you insert one, the ‘Map Variable’ column will look like this:
The fieldnames are all columns from the Leads table. When you click on any of these fieldnames, a pop-up window will open to allow you to set the contents of this field in the Leads variable. It will allow you to set this using Liquid syntax, using the path to a single field, or using a constant.
Information about Liquid can easily be found here.
Using Liquid syntax, you could enter the data like this:
Notice how the ‘sample’ underneath shows you how this field would be filled with the sample data that was entered by filling out the form. This way, you will always be sure that you have properly entered the datafields.
If you wish to fill the field using a Path, you select the Path radio button and simply select the path to the datafield using the dropdown menu, which is filled with the data from the sample. This looks like this:
Again, when you have selected a field, you can see the sample content of that field underneath, so you know for sure you selected the field you wish to use.
A Constant value will simply allow you to always enter a given value into the column for this variable, which looks like this:
A filled out Lead variable would, as such, look something like this:
You can continue filling up a variable with all the data, or introducing new variables for more data. For example, in the given webform was space for a Chamber of Commerce number, which was not available in the Lead type variable. For this, you could include a new variable of the type ‘String’ to contain the Chamber of Commerce number.
Next week, we are going to discuss linking this Endpoint to a Workflow and preparing the Workflow to use the data for several steps of automation. The week after, we will discuss examples of this automation and the different types of automation that can be utilized with the Workflow.