Linking Airwallex 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.
This source is currently in alpha. The interface and available tables may change.
The Airwallex connector syncs financial transactions, deposits, payment intents, 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.
Sync your Airwallex payments, payouts, balances, and billing data.
Create an API key under Developer then API keys in the Airwallex web app, and copy the client ID shown alongside it. The key needs read access to the resources you want to sync.
You'll be asked for:
- Client ID
- API key
- Environment: choose between Live and Demo.
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 Airwallex tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Client ID | text | Yes |
API key | password | Yes |
Environment | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
FinancialTransactions | The account ledger: every movement that changed an Airwallex balance. | Incremental, Full refresh | created_at | — |
Deposits | Money arriving into an Airwallex account, one row per deposit. | Incremental, Full refresh | created_at | — |
PaymentIntents | One row per attempt to collect money from a customer, with its amount, status, and captured total. | Incremental, Full refresh | created_at | — |
PaymentAttempts | Individual authorisation and capture attempts made against a payment intent. | Incremental, Full refresh | created_at | — |
Refunds | Money returned to a customer, one row per refund. | Incremental, Full refresh | created_at | — |
Customers | The customers you charge, as stored in Airwallex payment acceptance. | Incremental, Full refresh | created_at | — |
Settlements | Batches of payment activity settled into an Airwallex balance. | Incremental, Full refresh | settled_at | — |
Beneficiaries | Saved payout recipients, with their bank and entity details. | Incremental, Full refresh | created_at | — |
Transfers | Outbound payouts, with amounts, fees, conversion detail, and status. | Incremental, Full refresh | created_at | — |
GlobalAccounts | The local receiving accounts opened for your business, one row per account. | Incremental, Full refresh | created_at | — |
Invoices | Billing invoices, with totals, tax, discounts, and payment status. | Incremental, Full refresh | created_at | — |
Subscriptions | Recurring billing subscriptions and their current period and status. | Incremental, Full refresh | created_at | — |
BillingCustomers | The customers billing invoices and subscriptions belong to. | Incremental, Full refresh | created_at | — |
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.