Skip to main content
VTEX is a comprehensive e-commerce platform that provides a wide range of solutions for online businesses. It offers tools for catalog management, order processing, payments, and logistics, enabling businesses to create and manage their online stores efficiently.

Configuring VTEX as a Source

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

1. Add account access

You’ll need your VTEX Application Key and Token for this connection. You can generate these in your VTEX account settings. For detailed instructions, please refer to the VTEX Application Keys Guide to ensure you have given the relevant permissions.
  • App Key: Your VTEX appKey for API authentication.
  • App Token: Your VTEX appToken for API authentication.
  • Account Name: Your VTEX account name. It can be found in the subdomain of your VTEX admin URL. For example: if your admin URL is example.myvtex.com, the value to fill in this field is example.
  • Start Date: The earliest date to sync records from the API. Please note VTEX Orders API only returns data from a maximum of 2 years ago.
  • Lookback window (days): While running incremental extraction, retrieve once again the records created up to the provided period prior to the creation of the latest record previously extracted.
  • Category tree levels (optional): The number of category tree levels to fetch. Increase this value to include deeper subcategories. Default is 10.
  • Order status filter: Whether to extract only complete orders, only incomplete ones or all of them.
  • Master data acronyms (optional): The acronyms of the master data entities to extract (e.g., CL for clients, AD for addresses). Leave empty if you don’t need to extract any master data entity.
An App key includes specific permissions, based on License Manager roles and resources selected when creating or editing the App key. Read Managing app key permissions for more details.

2. Select streams

Choose which data streams you want to sync. VTEX provides access to your store’s order information, catalog details, and more.
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 VTEX and their corresponding fields:
Stream containing detailed information about product categories.Key fields:
Stream containing the hierarchical tree structure of categories.Key fields:
Stream containing a list of all coupons from your VTEX account.
Dynamic streams for extracting VTEX Master Data entities. Each acronym you configure in the Master data acronyms field generates a separate stream named data_entity_{acronym}.Common acronyms include CL (Clients), AD (Addresses), and OD (Orders Master Data). The schema is dynamically fetched from VTEX based on each data entity’s configuration.
Stream listing inventory information for all SKUs and all warehouses.
Stream containing a list of all orders in your VTEX store.
Stream containing detailed information for each order.
Stream containing the mapping between products and their associated SKU IDs.
Stream containing a list of all products in your catalog.
Stream containing a list of all promotions of your VTEX account.
Stream containing comprehensive details for individual SKUs, including dimensions, specifications, categories, and active status.
Stream containing information about SKU kits - products that are composed of multiple other SKUs.
Stream containing pricing information for all SKUs.
Stream containing detailed information about all SKUs (Stock Keeping Units) in your catalog. SKUs represent the actual sellable variations of products.

Skills for agents

Download VTEX skills file

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