Skip to main content
A destination is where your bank data is written: a Google Sheets spreadsheet, a YNAB 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.

YNAB

Sync transactions to a YNAB 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.
Actual Budget and Sure run as separate Docker tools rather than dashboard destinations.

​
Destinations list

Each destination card shows:
  • Destination type icon (Google Sheets, YNAB, or Webhook)
  • Name: the spreadsheet, plan name, or webhook hostname
  • Subtitle: the specific sheet or account within (webhook shows the endpoint URL)
  • Open button: link to open the destination directly in its app

​
Adding a destination

1

Choose a type

Click Add Destination and select Google Sheets, YNAB, 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: choose a spreadsheet, then a sheet (tab)
  • YNAB: 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:
FieldDescription
Transaction IDUnique identifier used for deduplication
DateTransaction date
DescriptionTransaction description
AmountTransaction amount
DirectionCredit or debit
CategoryTransaction category (if available)
MerchantMerchant name (if available)
AccountBank account name
StatusPosted (only settled transactions are synced)
ClassPayment, transfer, fee, interest, or other
Post DateDate the transaction was posted
Transactions are deduplicated using their Transaction ID. Re-running a sync does not create duplicate entries.

​
Removing a destination

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