Skip to main content
Konfidency is a product reviews and reputation platform for e-commerce. It collects and moderates customer reviews, questions and answers, and NPS survey responses for online stores, helping brands showcase social proof and understand customer sentiment. This connector extracts data from the Konfidency Reviews Admin API.

​
Configuring Konfidency as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Konfidency option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll authenticate with Konfidency using OAuth2 credentials (client credentials flow). You can request these from your Konfidency account manager. The following configurations are available:
  • Client ID: The OAuth2 client ID for the Konfidency Reviews Admin API.
  • Client Secret: The OAuth2 client secret for the Konfidency Reviews Admin API.
  • Customer: Your Konfidency customer identifier, used as the API path prefix (e.g. brandili).
  • Start Date: The earliest record date to sync. This applies to the incremental streams (reviews and NPS responses).
Once you fill the configuration, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select all streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Konfidency and their corresponding fields:
Product reviews submitted by customers. Synced incrementally using the created timestamp.Key Fields:
  • _id - Unique identifier of the review
  • sku - SKU of the reviewed product
  • name - Display name of the review author
  • rating - Star rating given by the reviewer, from 1 to 5
  • text - Free-text body of the review
  • status - Moderation status (published, removed, filtered, pending)
  • created - Timestamp when the review was created (incremental replication key)
  • moderated_at - Timestamp when the review was moderated
Engagement:
  • helpful - Number of users who marked the review as helpful
  • unhelpful - Number of users who marked the review as unhelpful
  • verified - Whether the review comes from a verified purchase
  • recommended - Whether the reviewer recommends the product
Order & Product (JSON-encoded):
  • order_id - Identifier of the order associated with the review
  • order_name - Customer name from the associated order
  • order_email - Customer email from the associated order
  • order_phone - Customer phone from the associated order
  • pictures - List of picture URLs attached to the review
  • product - Product details (name, sku, url, image, brand, mpn, gtin, categories, specifications)
  • seller_info - Seller information (id, name) for marketplace orders
Product questions and answers submitted by customers. Synced as a full table.Key Fields:
  • _id - Unique identifier of the question
  • status - Moderation status (published, removed, filtered, sent)
  • created - Timestamp when the question was created
  • customer - Konfidency customer identifier
  • sku - SKU of the product the question refers to
  • name - Display name of the person asking
  • text - Free-text body of the question
  • email - Email of the person asking
Nested (JSON-encoded):
  • reply - Reply object (text, created, helpful, unhelpful)
  • product - Product details (sku, brand, categories, image, name, url, variants, status, sum_ratings, total_reviews)
NPS survey responses collected from customers. Synced incrementally using the created timestamp.Key Fields:
  • _id - Unique identifier of the NPS response
  • customer - Konfidency customer identifier
  • survey_id - Identifier of the survey the response belongs to
  • request_id - Identifier of the survey request sent to the customer
  • rating - NPS score given by the respondent, from 0 to 10
  • comment - Free-text comment left by the respondent
  • partial - Whether the response was only partially completed
  • created - Timestamp when the response was recorded (incremental replication key)
  • send_date - Timestamp when the survey was sent to the customer
Respondent & Order:
  • name - Name of the respondent
  • phone - Phone number of the respondent
  • order_id - Identifier of the order associated with the response
Product groups that bundle related SKUs together. Synced as a full table.Key Fields:
  • _id - Unique identifier of the product group
  • customer - Konfidency customer identifier
  • name - Display name of the product group
Nested (JSON-encoded):
  • skus - List of SKUs that belong to the group
  • products - List of product details (sku, brand, categories, image, name, url, variants)

​
Skills for agents

Download Konfidency skills file

Konfidency connector documentation as plain markdown, for use in AI agent contexts.