Send a Purchase Webhook to Funnelytics with Integromat

How to send purchases to Funnelytics using Integromat

Create a Scenario in Integromat and add the Webhook as a trigger

Step 1. Select the Webhook app as a trigger.  Choose the Custom webhook module option as the trigger event.

Step 2. Give your custom webhook a name, adding it in the "Add a Hook" 

Step 3. Copy the webhook URL from Integromat and paste it into your payment processor/cart solution.

Set your payment processor/cart solution to fire the webhook once the order is created.

Add the Iterator tool

The Iterator tool allows your Integromat scenario to read multiple products' info nested inside your webhook.

Step 1. Click on the green "Cog" icon you can find at the bottom of your scenario page.

Step 2. Select "Iterator".

Step 3. Connect it to your Webhook trigger, once done you will be able to select the element of your webhook that has the products purchased. Integromat will collect the information and send it to Funnelytics.

In the image below, we have selected the 1. resource: spreadsheet: data[] element.

Add the Aggregate to JSON module

Now that you have made all the purchased products data available to Integromat, let's ask it to put them in a way that the Funnelytics endpoint will easily digest.

To do this we need to add an Aggregate to JSON module.

Step 1. Click on the little "+" icon on the bottom of the scenario page.

Step 2. Type JSON in the window that pops up,

Step 3. Select the JSON icon

Step 4. Then hit Aggregate to JSON.

Configure the Aggregate to JSON module

Configuring this module is quite easy thanks to the built-in generator, which lets you create the layout by making it read the structure of the final code we want to create.

Step 1. Start by selecting the Source of the data from the dropdown menu, which will be the Iterator.
Step 2. Then click on the Add button to create a new data structure.

Step 3. Give it a name.

Step 4. Click on Generator.

Step 5. In the new window, select JSON in the "Content-type" dropdown menu. 

Step 6. Paste the following code in the "Sample Data" field.

{
"product_name": "my product name",
"product_id": "my product id",
"total": 0
}

Integromat will read the JSON code and will populate the "Specification" section with the three elements we need and their value type.

The last step needed is to go back to the first window of the Aggregate to JSON module and select which values shall fill those fields.

To do this just click on the field that needs to be filled and select the value from the pop-up window.

Add the HTTP Request

Let's get to the last piece of our puzzle, the HTTP Request module.

To add the module, we will once again click the little "+" icon that appears at the bottom of the scenario page, however, in this case, we will search for "HTTP", and the action will be Make a Request.

Configure the HTTP Request module

Step 1. Add https://track-v3.funnelytics.io/events/commerce to the URL field. 

Step 2. Select POST as the Method.

Step 3. Add two headers as detailed in the table below:

Step 4. Select Raw as "Body Type"

Step 5. Set JSON (application/json) as the "Content type".

Step 6. Lastly, in "Request content"  paste the following code and enter your data between the empty quotes ""

{
"email": "",
"datetime": "",
"items": 
}

Click the "Request Content" field to reveal the data mapping pop-up.

Step 1. In the webhook elements look for the one that contains the User's Email and add it between the quotation marks in front of the "email": line. In my case here is 1. resource: customer: data: email.

Step 2. Again, in the webhook elements, look for the property that contains the order creation timestamp and add it between the quotation marks in the "datetime": line.

Step 3. Add the Aggregate to JSON output in the "items": line

If your payment process/cart solution does not send out time data formatted this way you can always format it yourself, by adding this bit of code instead of the single time element,

"{{parseDate(Webhook Time Element; "YYYY-MM-DDTHH:mm:ss"; "Timezone")}}"

Something missing?

if something is missing in the documentation or if you found some part confusing, please reach out to support team, with your suggestions for improvement.

We love hearing from you!