> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking Slash as a source

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

The Slash connector syncs your corporate banking data – accounts, transactions, cards, invoices, invoice series, expense reports, and contacts – into PostHog.

**Slash API access**

Slash labels API access as beta. You may need to request access from Slash support at [support@joinslash.com](mailto:support@joinslash.com) before connecting.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Slash.
3.  Get an API key from your Slash dashboard. Create a read-only key for your legal entity.
4.  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**.
5.  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 reconciliation**

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 | — | — |

### Still have questions?

Ask PostHog AI

### Was this page useful?

HelpfulCould be better