Destinations

Choose where your data is synced

A destination is where your bank data is written: a Google Sheets spreadsheet, a You Need a Budget plan, or a webhook endpoint.

You can connect multiple destinations and create separate syncs for each.

Supported destinations

Google Sheets

Sync transactions to a spreadsheet.

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.

Notion is a legacy destination that is no longer offered to new customers. Users who already have a Notion destination can continue to use it, and a small allowlist retains access to add new ones.

Destinations list

Destinations are grouped by type. Each group renders as a table — one table per type (Google Sheets, 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

1. Choose a type

   Click Add Destination and select Google Sheets, You Need a Budget, or Webhook. Notion is offered as well to allowlisted users and users who already have a Notion destination.

2. 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.

3. Select a target

   Pick the specific resource to write data to:

   • Google Sheets: choose a spreadsheet, then a sheet (tab)
   • 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

Transactions are deduplicated using their Transaction ID. Re-running a sync does not create duplicate entries.

Webhook hard resync

Webhook destinations expose a Hard resync action in the sync’s Settings tab. This clears the per-destination dedup state for the sync so the next run re-delivers every in-range transaction to your endpoint. Use it after you reset your downstream store or change your processing logic.

Removing a destination

Select Delete from the three-dot menu on a destination row. Any syncs using this destination are also deleted.