Linking Mono 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.
The Mono source is currently in alpha. It has been tested against Mono's API documentation but not yet battle-tested with live production workloads. If you run into issues, please let us know.
The Mono connector syncs your open banking data into PostHog, including customers, linked bank accounts, and transactions.
Mono is an African open banking platform that lets businesses access financial data from their customers' bank accounts.
Prerequisites
Before connecting Mono to PostHog:
- You need a secret API key from your Mono app. Copy it from the Mono dashboard.
- Your customers must link their bank accounts through Mono before you can import transactions.
Adding a data source
- Go to the Data pipeline page and select the Sources tab.
- Click + New source and select Mono by clicking the Link button.
- Enter your Secret API key from the Mono dashboard.
- Enter a Transaction start date in
YYYY-MM-DDformat. This is the earliest date from which transactions are imported. It must be before today. - Click Next.
- Select the tables you want to import, set the sync method and frequency, then click Import.
The data warehouse then starts syncing your Mono data. You can see details and progress in the data pipeline sources tab.
Configuration
| Option | Type | Required |
|---|---|---|
Secret API key | password | Yes |
Transaction start date | text | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
customers | Customers registered with the Mono business. | Full refresh | — | — |
accounts | Bank accounts linked to the Mono business. | Full refresh | — | — |
transactions | Transactions from linked bank accounts within the selected date range. | Incremental, Full refresh | date | — |
Sync modes
The transactions table supports incremental syncing using the date field. All other tables use full refresh.
| Table | Sync method | Notes |
|---|---|---|
customers | Full refresh | |
accounts | Full refresh | |
transactions | Incremental or full refresh | Uses date as the cursor for incremental syncs |
Incremental syncs fetch transactions with a date at or after the last synced value, with a one-day overlap to capture late-arriving data. Full refresh syncs reload all data from the configured start date.
Incremental syncs only pick up new transactions going forward. If a customer links a new bank account, you need to run a full refresh to import that account's historical transactions. The same applies if you need to capture changes outside the one-day overlap window.
Available tables
| Table | Description |
|---|---|
customers | Customers registered with the Mono business |
accounts | Bank accounts linked to the Mono business |
transactions | Transactions from linked bank accounts within the selected date range |