KnoCommerce supports webhooks for real-time survey events. This means whenever a customer completes a survey, KnoCommerce can POST the response data to an external URL you specify. Make.com, a no-code automation platform, can catch these webhooks and use them to trigger workflows (called Scenarios) instantly.
By integrating KnoCommerce webhooks with Make, you can automatically funnel survey response data into other tools or actions – for example, posting a Slack message, adding a row to a Google Sheet, or even invoking an OpenAI API call for analysis.
This guide will walk you through configuring a KnoCommerce webhook for survey responses and setting up Make.com to trigger various actions when a new response comes in.
Table of Contents
Slack: Send Survey Responses to Slack
Google Sheets: Log Responses in a Spreadsheet
OpenAI: Analyze Responses with AI
Prerequisites
Before you begin, make sure you have the following:
KnoCommerce account (Pro plan or above): You'll need access to our API + webhooks
Make.com account (any plan): Make’s free plan is sufficient for basic webhook scenarios.
Accounts for target integrations (depending on what you plan to do with the data - like Slack, Google Sheets, OpenAI, etc.)
Setting Up a Webhook in Make.com
First, we'll configure Make.com to catch the webhook that KnoCommerce will send. This involves creating a scenario in Make and adding a webhook trigger module.
Click "Create a new scenario."
For the trigger, select the the Webhooks module.
This should be towards the top of the modal, but you can also use the search bar and type "Webhooks" and select the Webhooks app.
Select the option for “Custom Webhook”
In the Custom Webhook module's settings panel, click “Create a webhook” to create a new webhook. Give it a descriptive name (e.g., "KnoCommerce Survey Response") and save
Once the webhook is created, copy the URL that Make provides. It will look something like
https://hook.us1.make.com/abcdef123456...(each webhook has a unique URL). Keep this URL handy – you'll need to provide it to KnoCommerce in the next step.
At this point, your Make scenario is waiting for data. We’ll configure KnoCommerce to send survey responses to this URL. Once a survey submission is sent, Make will catch it and you can proceed to process the data in subsequent steps.
Configuring the Webhook in KnoCommerce
Next, we'll configure KnoCommerce to send survey response events to the Make webhook URL. KnoCommerce webhooks are set up via the API using your account’s API credentials (currently, there isn’t an in-app UI to add webhooks, so you’ll use the REST API).
Navigate to Settings > API Access
Create a new API entry (for example, name it "Make.com Integration").
Set the Redirect URL to a placeholder (e.g.,
https://www.make.com/)Select all permission scopes
Save to retrieve your Client ID and Client Secret for the API
Follow our instructions here for how to property authenticate with these details
Once authenticated, call the KnoCommerce API endpoint to create a new webhook subscription. In the API request, you'll specify:
Topic: Use
"response/create"(this topic corresponds to “survey response created” events, so the webhook triggers whenever a new survey response is submitted)URL: Use the Make.com webhook URL you copied earlier (this tells KnoCommerce where to POST the data)
Ensure the API response indicates the webhook was created. You can also list your webhooks via the API to double-check the details (this step is optional). Once configured, KnoCommerce will send a POST request to the provided URL every time a new survey response is recorded.
Tip: If you are not comfortable making API calls manually, you can use tools like Postman to assist, or ask a developer on your team for help. The key is to register the webhook with topic response/create pointing to your Make.com URL.
Building the Make Scenario
With Make catching incoming survey data and KnoCommerce sending it, you can now build out the rest of your scenario – i.e. what to do with the survey response data once it arrives in Make.
Send a test webhook: Before adding a lot of modules, it’s wise to test the setup. Submit a survey response to a KnoCommerce survey. This should cause KnoCommerce to fire the webhook. In Make.com, click the “Run once” button on your scenario to listen for incoming data, and verify that Make receives the webhook. You should see a successfully received bundle of data (the survey response JSON) in the Make scenario flow. This also allows Make to automatically determine the data structure of the incoming webhook (so you can map fields in the next steps)
Adding modules: Once the webhook trigger has successfully received data, you can start adding modules after the webhook in your scenario. This is where you define the actions to take with the survey response data. Make supports thousands of apps and actions – you can add filters, transformations, and connections to other services. For example, you might add:
A Slack module to post a message
A Google Sheets module to save the data
An email module to notify your team
An OpenAI module to analyze the response
You can also use Make’s built-in tools (like the Iterator, Array aggregator, or JSON tools) if you need to transform the data before sending it elsewhere.
Map the data to fields: When configuring each new module, you’ll use Make’s mapping interface to insert data from the webhook. Mapping ensures the data from the survey response is placed into the correct spots in the action (e.g., the content of a Slack message or the cells of a Google Sheet row).
Activate the scenario: After setting up your scenario and testing it with sample data, turn on the scenario (set it to active). Because the trigger is an instant webhook, you don’t need to schedule it – it will run automatically whenever a new survey response comes in.
Screenshots
Mapping the response data
By completing the steps above, you have set up a Make.com scenario triggered by a KnoCommerce survey webhook. Every time a new survey response is submitted, the data will flow into Make and execute whatever actions you’ve configured, in real time. Next, we’ll explore a few specific integration examples to illustrate what you can do with this setup.
Integration Examples
Once your basic webhook->Make pipeline is working, the possibilities are endless. Here are a few common integration examples using survey response data:
Slack: Send Survey Responses to Slack
One popular use case is to notify your team in Slack whenever a new survey is completed. For example, after a customer submits a post-purchase survey, you might want a Slack channel to receive the highlights of their response (so your team can react quickly to feedback).
Google Sheets: Log Responses in a Spreadsheet
Another common integration is logging each survey response to a Google Sheet. This can create a running list of all responses in a spreadsheet, which is useful for record-keeping or further analysis (especially for teams that prefer working in Sheets).
OpenAI: Analyze Responses with AI
For a more advanced integration, you can send survey feedback to OpenAI to perform language analysis, generate summaries, or categorize responses. For example, you could automatically generate a brief summary of a long-form survey answer or detect sentiment (positive/negative) using OpenAI’s models.
Additional Resources
Make.com Webhooks Documentation: To learn more about how webhooks work in Make (custom vs. app webhooks, data structures, etc.), see Make’s official docs on Webhooks.
KnoCommerce API Documentation: Refer to the KnoCommerce Developers Docs for technical details on authenticating and managing webhooks via API.