Linking Slash as a source
This source is currently in beta. It works end to end, but you may still hit rough edges. Let us know if you do.
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
The Slash connector syncs your corporate banking data – accounts, transactions, cards, invoices, invoice series, expense reports, and contacts – into PostHog.
Slash labels API access as beta. You may need to request access from Slash support at support@joinslash.com before connecting.
Adding a data source
- Go to the sources tab of the data pipeline section in PostHog.
- Click + New source and then click Link next to Slash.
- Get an API key from your Slash dashboard. Create a read-only key for your legal entity.
- Enter your API key in PostHog. If you're using a user-scoped key (rather than an organization key), also enter your Legal entity ID.
- 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 Slash data in PostHog.
Available tables
| Table | Description | Sync method |
|---|---|---|
accounts | Slash bank accounts accessible to the API key | Full refresh |
transactions | Transactions across Slash accounts, including card payments, transfers, and fees | Incremental |
cards | Physical and virtual cards accessible to the API key | Full refresh |
invoices | Invoices for the legal entity, with their details and receiving account info | Full refresh |
invoice_series | Recurring invoice configurations for the legal entity | Full refresh |
expense_reports | Expense reports submitted for reimbursement, with merchant and review info | Full refresh |
contacts | Counterparties for the legal entity, including customers and vendors | Full refresh |
Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.
Transaction dates can change when posting occurs. Date filters may miss later changes to older transactions. Use full refresh to reconcile those changes when needed.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Legal entity ID | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
accounts | Slash bank accounts accessible to the API key. | Full refresh | — | — |
transactions | Transactions across Slash accounts, including card payments, transfers, and fees. | Incremental, Full refresh | date | — |
cards | Physical and virtual cards accessible to the API key. | Full refresh | — | — |
invoices | Invoices for the legal entity, with their details and receiving account information. | Full refresh | — | — |
invoice_series | Recurring invoice configurations for the legal entity. | Full refresh | — | — |
expense_reports | Expense reports submitted for reimbursement, with merchant and review information. | Full refresh | — | — |
contacts | Counterparties for the legal entity, including customers and vendors. | Full refresh | — | — |
virtual_accounts | Virtual accounts under each Slash account, including the primary account and closed accounts. | Full refresh | — | — |
card_groups | Active card groups that share a spending constraint. | Full refresh | — | — |
customers | Billing recipients for invoices of the legal entity. | Full refresh | — | — |
account_balances | Current balances of each Slash account. Charge card accounts have cash and credit balances. | Full refresh | — | — |