Skip to main content

Integrations & Data Sources

📦 Integrations is where you connect analytics data. BI supports automated ETL sync from platforms and direct connections to your own databases.


📍 Accessing Integrations​

BI → Integrations (/app/avantbi/integrations)

The page shows all data sources as cards (or a table view). Use Add data source to connect something new.


➕ Adding a data source​

Add data source opens a two-path chooser:

OptionUse when
Add integrationYou want automated sync from Square, Cheerfy, Factorial, Deliverect, or internal ERP data
Connect databaseYou have PostgreSQL, MySQL, or SQL Server you want to query directly

📋 ETL integrations (automated sync)​

Available integrations depend on your tenant subscription:

IntegrationDataCredentials required
ERPLogstock / inventory, sales, procurement, production, etc.None — appears when the ERP (Logstock) module is enabled; syncs from your tenant database
SquareLocations, catalog, ordersAccess token, API base URL
CheerfyRestaurant loyalty / CRMToken, organization code
FactorialHR — employees, teams, leaves, expensesAPI key, base URL
DeliverectMulti-channel delivery orders (webhook-driven)Client ID, client secret, account ID, API base URL
tSpoonLabKitchen / inventory / recipe managementUsername, password, optional API base URL
info

Integration availability can change between releases. If an integration you expect is missing, contact your administrator.

Connecting an ETL integration​

  1. Add data source → Add integration.
  2. Select the platform card.
  3. Review requirements on the Get started step.
  4. Enter credentials on the Requirements step.
  5. Test connection → Add integration.
  6. The first sync starts automatically when the integration is enabled.

Integration detail page​

Open any connected integration to:

  • Browse tables synced into the analytics warehouse.
  • Open a table detail view to inspect columns (useful when writing SQL).
  • Review Sync health: next run, last run, status, and error messages.
  • Sync now — trigger an immediate incremental sync.
  • Run historical sync — full backfill (only shown when supported for that integration).
  • Disconnect — disable the integration.

Integration detail with sync health and table list


📋 Direct database connections​

Connect PostgreSQL, MySQL, or SQL Server for live querying (no warehouse sync).

  1. Add data source → Connect database → Get Started.
  2. Choose Database Engine.
  3. Enter Connection Details — host, port, database, username, password, a friendly name, and optionally Use SSL. Add database connection dialog
  4. Test Connection — you must get a successful test before Add Database becomes available. Editing any credential after a successful test requires re-testing. Test Connection step showing a successful test
  5. Optionally choose Explore tables after saving to browse schemas immediately.

On the connection detail page:

  • Pick a schema (when the engine exposes multiple schemas).
  • Browse tables and open table details.
  • Remove connection from the ⋮ menu when no longer needed.

Credentials are stored encrypted.

info

Each tenant can have up to 10 direct database connections.

warning

A connection can't be removed while any saved query still uses it — update or delete those queries first.

info

The product labels new connections read-only, but this isn't enforced by AvantBI itself — the app doesn't block write statements sent through a saved query on a direct connection. Use a read-only database user on your side for real protection, exactly as the connection wizard recommends.


⚙️ Managing integrations​

ActionWhere
View all sourcesIntegrations list (card or table toggle)
Search / filterToolbar on Integrations list
Re-syncIntegration detail → Sync now
Troubleshoot failed syncIntegration detail → Sync health error panel
Remove ETL integrationIntegration detail → ⋮ → Disconnect
Remove DB connectionConnection detail → ⋮ → Remove connection

🚫 Scope notes​

  • ERP integration only appears if your tenant has the Logstock module enabled.
  • Direct DB queries run against your database in real time — large unfiltered queries may be slow; use parameters and limits in SQL.
  • Sync schedules are managed by the platform; you trigger manual syncs from the UI but do not edit cron expressions directly.