A destination is where your bank data is written: a Google Sheets spreadsheet, an Airtable base, a Notion database, a You Need a Budget plan, or a webhook endpoint. You can connect multiple destinations and create separate syncs for each.Documentation Index
Fetch the complete documentation index at: https://docs.redbark.co/llms.txt
Use this file to discover all available pages before exploring further.
Supported destinations
Google Sheets
Sync transactions to a spreadsheet.
Airtable
Sync transactions to an Airtable base.
Notion
Sync transactions to a Notion database.
You Need a Budget
Sync transactions to a You Need a Budget plan.
Webhook
Receive transactions via HTTP POST to your own endpoint.
Actual Budget
Sync transactions to a self-hosted Actual Budget instance via Docker.
Sure
Sync transactions to a self-hosted Sure instance via Docker.
MCP Server
Give AI agents read-only access to your banking data.
Actual Budget and Sure run as separate Docker tools rather than dashboard destinations.
Destinations list
Destinations are grouped by type. Each group renders as a table — one table per type (Google Sheets, Airtable, You Need a Budget, Webhook, Notion) — with rows for Name, Detail, Status, and a per-row action menu. The group header shows the type label and a group-level status badge.Adding a destination
Choose a type
Click Add Destination and select Google Sheets, Airtable, Notion, You Need a Budget, or Webhook.
Authenticate or configure
For most destinations, sign in with your account for the chosen service. Redbark Sync will request permission to read and write data. For Webhook, enter your HTTPS endpoint URL instead.
Select a target
Pick the specific resource to write data to:
- Google Sheets: choose a spreadsheet, then a sheet (tab)
- Airtable: choose a base, then a table (or create a Transactions table)
- Notion: choose a database, or create one in a page you’ve shared
- You Need a Budget: choose a plan (account mapping is configured when you create a sync)
- Webhook: generate and copy your signing secret
Data fields by sync type
Transaction fields
All destinations receive the same set of transaction fields, formatted appropriately for each platform:| Field | Description |
|---|---|
| Transaction ID | Unique identifier used for deduplication |
| Date | Transaction date |
| Description | Transaction description |
| Amount | Transaction amount |
| Currency | ISO 4217 currency code for the amount |
| Direction | Credit or debit |
| Category | Transaction category (if available) |
| Merchant | Merchant name (if available) |
| Account | Bank account name |
| Status | Posted (only settled transactions are synced) |
| Class | Payment, transfer, fee, interest, or other |
| Post Date | Date the transaction was posted |