Linking e-conomic 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 e-conomic connector syncs your Visma e-conomic accounting data into PostHog, so you can analyze your financials alongside your product data.
Prerequisites
You need a Visma e-conomic agreement and an app registered in the e-conomic Developer portal, so you can obtain both authentication tokens.
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.
When linking e-conomic, you'll need:
- App secret token – your app's secret, from the e-conomic Developer portal.
- Agreement grant token – issued when an e-conomic user grants your app access to their agreement.
Both tokens grant read access to the whole agreement. e-conomic has no per-resource scopes.
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.
Configuration
| Option | Type | Required |
|---|---|---|
App secret token | password | Yes |
Agreement grant token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | A debtor (customer) you sell to. Holds billing details, payment terms and the customer's running balance. | Incremental, Full refresh | lastUpdated | — |
customer_groups | A grouping of customers, typically used to assign a common sales account. | Full refresh | — | — |
products | A product or service you sell, with pricing and inventory references. | Incremental, Full refresh | lastUpdated | — |
product_groups | A grouping of products that share sales accounts and inventory settings. | Full refresh | — | — |
suppliers | A creditor (supplier) you buy from, with payment and contact details. | Full refresh | — | — |
supplier_groups | A grouping of suppliers, used to assign a common cost account. | Full refresh | — | — |
accounts | An account in the chart of accounts, including its type and current balance. | Full refresh | — | — |
accounting_years | A financial (accounting) year and the date range it covers. | Full refresh | — | — |
journals | A journal used for grouping and posting entries. | Full refresh | — | — |
currencies | A currency available in the agreement. | Full refresh | — | — |
payment_terms | A set of payment terms (credit days and type) applied to invoices. | Full refresh | — | — |
departments | A department used to tag entries for dimensional reporting. | Full refresh | — | — |
departmental_distributions | A rule for distributing an entry across multiple departments. | Full refresh | — | — |
units | A unit of measure that products can be sold in (e.g. hours, pieces). | Full refresh | — | — |
vat_zones | A VAT zone determining how VAT is applied to customers and suppliers. | Full refresh | — | — |
employees | An employee in the agreement, used as a sales person on invoices. | Full refresh | — | — |
invoices_booked | A booked (finalized, immutable) sales invoice with its amounts and customer reference. | Incremental, Full refresh | bookedInvoiceNumber | — |
invoices_drafts | A draft (not yet booked, editable) sales invoice. | Full refresh | — | — |
Troubleshooting
- If your tokens are invalid or have been revoked, check your app secret token and agreement grant token, then reconnect.
- If your tokens do not have access to some data, re-grant the app access to the agreement, then reconnect.
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.