Linking Veeqo as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
Contents
This source is currently in alpha. The interface and available tables may change.
The Veeqo connector syncs orders, products, customers, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Veeqo API key to automatically pull your Veeqo inventory, order and shipping data.
You can find your API key in your Veeqo account under Settings > Users, on your user's profile. Veeqo support must enable API access for your account before the key appears there - contact them if you don't see it.
The API key gives full account access, so store it securely.
You'll be asked for:
- API key: for example
Enter your Veeqo API key.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Veeqo tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
orders | A sales order placed on any of your connected sales channels, including its line items, allocations and payment. | Incremental, Full refresh | updated_at, created_at, id | — |
products | A product in your Veeqo inventory, including its variants (sellables), images and stock information. | Incremental, Full refresh | updated_at, created_at, id | — |
customers | A customer who has placed orders on any of your connected sales channels. | Full refresh | — | — |
purchase_orders | A purchase order raised against a supplier to replenish stock, including its line items and delivery details. | Full refresh | — | — |
suppliers | A supplier you raise purchase orders against, including contact and payment details. | Full refresh | — | — |
warehouses | A physical or virtual location where you hold inventory. | Full refresh | — | — |
stores | A sales channel (store) connected to Veeqo, such as Shopify, eBay or Amazon. | Full refresh | — | — |
tags | A tag used to label and organize orders and products. | Full refresh | — | — |
delivery_methods | A delivery method offered on your orders, with its shipping cost. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.