> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking inFlow Inventory as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/inflowinventory

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

Enter your inFlow Inventory credentials to pull your inventory, customer, vendor, and order data into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to inFlow Inventory.
3.  Next, gather your inFlow Inventory credentials:
    -   **Company ID** – found on the **Integrations** page in [inFlow](https://www.inflowinventory.com/).
    -   **API key** – create one on the same **Integrations** page. API access requires a paid plan with the API add-on. The key is only shown once — copy it before leaving the page.
4.  Back in PostHog, enter the credentials and click **Next**.
5.  Select the tables you want to sync, set the sync method and frequency, then click **Import**.

Once the syncs are complete, you can start using inFlow Inventory data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `products` | Product inventory data | Full refresh |
| `customers` | Customer records | Full refresh |
| `vendors` | Vendor (supplier) information | Full refresh |
| `sales_orders` | Sales order data | Full refresh |
| `purchase_orders` | Purchase order data | Full refresh |

**Full refresh** tables reload all data on each sync.

## Sync limitations

All inFlow Inventory tables are full refresh only. The inFlow API doesn't support server-side timestamp filtering, so incremental sync isn't available.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Company ID` | text | Yes |
| `API key` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `products` | A product (inventory item) tracked in inFlow Inventory. | Full refresh | — | productId |
| `customers` | A customer in inFlow Inventory that sales orders are placed for. | Full refresh | — | customerId |
| `vendors` | A vendor (supplier) that purchase orders are placed with in inFlow Inventory. | Full refresh | — | vendorId |
| `sales_orders` | A sales order recording products sold to a customer. | Full refresh | — | salesOrderId |
| `purchase_orders` | A purchase order recording products bought from a vendor. | Full refresh | — | purchaseOrderId |
| `manufacturing_orders` | A manufacturing order that consumes component products to build finished products. | Full refresh | — | manufacturingOrderId |
| `stock_transfers` | A stock transfer that moves inventory from one location to another. | Full refresh | — | stockTransferId |
| `locations` | A location (warehouse or store) where inventory is kept in inFlow Inventory. | Full refresh | — | locationId |
| `categories` | A product category used to group products in inFlow Inventory. | Full refresh | — | categoryId |
| `stock_adjustments` | A stock adjustment that corrects or writes off inventory at a location outside of an order. | Full refresh | — | stockAdjustmentId |
| `stock_counts` | A physical stock count at a location, used to reconcile recorded inventory with counted inventory. | Full refresh | — | stockCountId |
| `product_cost_adjustments` | A change to a product's inventory cost, effective from a given date. | Full refresh | — | productCostAdjustmentId |
| `tax_codes` | A tax code that sets the tax percentages applied to order lines under a taxing scheme. | Full refresh | — | taxCodeId |
| `taxing_schemes` | A taxing scheme that defines the primary and secondary taxes and how they are calculated. | Full refresh | — | taxingSchemeId |
| `product_groups` | A product group that bundles product variants (e.g. sizes or colors) under one parent item. | Full refresh | — | productGroupId |
| `adjustment_reasons` | A reason code that categorizes a stock adjustment. | Full refresh | — | adjustmentReasonId |
| `currencies` | A currency used on orders, with its display format and conversion rates. | Full refresh | — | currencyId |
| `team_members` | An inFlow user on the account. API keys and other non-user actors are not included. | Full refresh | — | teamMemberId |