Skip to main content
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.

​
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 Actual Budget over SimpleFIN.

Sure

Sync transactions to a self-hosted Sure instance via its native Redbark provider.

Firefly III

Sync transactions to a self-hosted Firefly III instance over SimpleFIN.

MCP Server

Give AI agents read-only access to your banking data.
Actual Budget, Sure and Firefly III connect from their own side rather than being configured as dashboard destinations. Actual and Firefly use SimpleFIN; Sure has a native Redbark provider.

​
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

1

Choose a type

Click Add Destination and select Google Sheets, Airtable, Notion, You Need a Budget, or Webhook.
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: name a new spreadsheet for Redbark to create in your Google Drive
  • Airtable: choose a base, then a table (or create a “Redbark 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 core set of transaction fields, formatted appropriately for each platform (webhook payloads carry a few additional fields; see the webhook page):
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 re-checks every transaction from your start date and delivers any that never made it, for example because your endpoint was down or returned an error. Transactions we already recorded as delivered are not sent again.

​
Webhook replay

Replay everything, also in the sync’s Settings tab, forgets every transaction recorded as delivered to that endpoint and sends them all again from your start date. Use it when your endpoint accepted transactions it did not actually keep. A common case is an endpoint that returns a 200 before it finishes writing, or a downstream store you have since wiped. In that situation we consider the transactions delivered, so a hard resync has nothing to send and replay is the way to get them back.
Your endpoint will receive transactions it has already seen. Make sure it can handle duplicates, or clear the data on your side first.

​
Removing a destination

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