Incoming Webhook Auth with Secret Key

Hello All,

Newbie Make Connector here coming from Zapier.

It’s clear that Make.com is a lot more complicated than Zapier, but i’m here for the ride.

I’m trying to connect webhooks with WooCommerce to automatically dispatch orders to slack. I was able to do it with thje WooCommerce only but it doesn’t give instant outputs.

So now i’m trying to use webhooks to do so… And it’s very complicated.

I followed this forum: Incoming Webhook Authentication

It noted that I have to input my secret key to postman so that the data can be received over the cloud. Is this necessary? Would i have to buy a subscription with Post Man? Might not be as worth it as I thought to switch from Zapier.

Thanks in advance,

Hey!!! Welcome to the Make Community!

And welcome to Make! Yes, it’s more complex than Zapier! But if you are patient, and follow the Make Academy trainings, or follow the trainings of one of our great partners, you will see how far you can go with Make :sunglasses:

You don’t need to implement any specific Key mechanism with your webhook, unless it’s requested by WooCommerce (I don’t know enough this application).

And, at Make, you have a pre-built Webhook Module for WooCommerce; have you tried it?


You can use it for different events in Woocommerce, including “Order Created”.

Please note that this module will only appear if you are editing the Start of the scenario

Try the following

If you are still stuck, let us know.

Cheers

Benjamin

3 Likes

Hello and welcome!

You do not need a Postman subscription. As @Benjamin_from_Make mentioned, Make already has a pre-built Woo Commerce webhook, which I believe (?) includes an authentication mechanism, so you don’t need to do what I did. Make did not have a pre-built webhook for my source application, so I needed to build my own custom Make webhook. You can take a look at the Woo Commerce Webhook Documentation to see the steps needed to connect WooCommerce to Make.

Here is why I referenced Postman: I use Postman to test my webhooks and scenarios (using mock customer/order/API key/secret values for security), and in this case, also for demonstration purposes. I like to include authentication to protect customers’ data as much as possible. @samliew was a great help showing me how to do this with a custom Make webhook in the Incoming Webhook Authentication that you referenced. The screenshot examples from the Incoming Webhook Authentication post show my Postman setup with mock API key and password values just to demonstrate how the API key/secret from a source application (in this case Postman for testing) maps to the custom Make webhook and the filter used for authentication at the very beginning of my scenario. Once I know the custom Make webhook, authentication, and scenario is running properly, I connect the real source application, including the source application API key/secret (password) to Make, and run a couple of final tests from the real source application.

As another security-related aside: I really like the “Data is Confidential” feature in Make, but I only turn it on once final testing is complete.

Hope this helps clarify, and have a great weekend!

-Kari

3 Likes