---
title: "Connect KnoCommerce to Rig — Rig guide"
description: "Connect KnoCommerce to Rig with an API client ID and secret, and sync post-purchase survey responses next to your orders and customers."
canonical: "https://rig.so/guides/connect-knocommerce"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect KnoCommerce to Rig

Sync your KnoCommerce survey responses, surveys and questions into Rig, so you can read what customers told you after checkout next to their orders. KnoCommerce connects with an API client ID and client secret.

## Before you start

- You need access to the **Settings** area of the KnoCommerce dashboard, where API clients are created.
- Your KnoCommerce plan must include API access. If it does not, KnoCommerce refuses the credentials with a plan error when Rig checks them.

## Step 1: Create a KnoCommerce API client

1. Sign in to the KnoCommerce dashboard.
2. Go to **Settings** and open **API Access**.
3. Create a new client. If the screen asks which permissions to give it, choose the scopes for **Responses**, **Surveys** and **Questions**.
4. Copy the **Client ID** and the **Client secret** somewhere safe. Treat the secret like a password.

Check the scope names
KnoCommerce's API reference lists the scopes `ATTRIBUTION`, `QUESTIONS`, `RESPONSES`, `SURVEYS` and `WEBHOOKS`. Rig reads responses, surveys and questions, so the other two are not needed.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **KnoCommerce**, open the card and click `Connect`.
3. **Client ID**: paste the client ID from KnoCommerce.
4. **Client secret**: paste the client secret that was issued with it.
5. **API base URL (optional)**: leave it empty. Rig then uses `https://app-api.knocommerce.com`.
6. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
7. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

KnoCommerce lands in its own `knocommerce` schema in your warehouse:

- **Responses**: every survey response, with the customer's ID, email and shop and the answer to each question. The linked order is attached, so a response joins to the order that triggered it.
- **Surveys**: the survey catalogue.
- **Questions**: the question catalogue behind each survey.

Responses sync incrementally by their update time, so edited answers are picked up. Surveys and questions are small tables that Rig reloads in full.

## Good to know

- KnoCommerce swaps the client ID and secret for a token that lasts about an hour. Rig renews it during a sync, so a long first sync is not cut short.
- Each answer is stored in its own table keyed back to the response, so a question's answers can be counted without unpacking a nested column.
- Rig reads survey data only. It does not use the webhook or attribution scopes.
- To disconnect KnoCommerce, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Capture the attribution your pixels miss
- Segment customers by why they bought, not just what
- Track responses over campaigns and time

[More ideas for using KnoCommerce](https://rig.so/integrations/knocommerce)

## KnoCommerce documentation

- [KnoCommerce API reference](https://developers.knocommerce.com/)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-knocommerce)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)