> ## Documentation Index
> Fetch the complete documentation index at: https://docs.redbark.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Destinations

> Choose where your data is synced

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

<Columns cols={3}>
  <Card title="Google Sheets" icon="table" href="/google-sheets">
    Sync transactions to a spreadsheet.
  </Card>

  <Card title="Airtable" icon="grid-2" href="/airtable">
    Sync transactions to an Airtable base.
  </Card>

  <Card title="Notion" icon="book" href="/notion">
    Sync transactions to a Notion database.
  </Card>

  <Card title="You Need a Budget" icon="wallet" href="/ynab">
    Sync transactions to a You Need a Budget plan.
  </Card>

  <Card title="Webhook" icon="webhook" href="/webhook">
    Receive transactions via HTTP POST to your own endpoint.
  </Card>

  <Card title="Actual Budget" icon="piggy-bank" href="/actual-budget">
    Sync transactions to a self-hosted Actual Budget instance via Docker.
  </Card>

  <Card title="Sure" icon="piggy-bank" href="/sure">
    Sync transactions to a self-hosted Sure instance via Docker.
  </Card>

  <Card title="MCP Server" icon="robot" href="/mcp-server">
    Give AI agents read-only access to your banking data.
  </Card>
</Columns>

<Info>
  Actual Budget and Sure run as separate Docker tools rather than dashboard destinations.
</Info>

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

<Steps>
  <Step title="Choose a type">
    Click **Add Destination** and select Google Sheets, Airtable, Notion, You Need a Budget, or Webhook.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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
  </Step>
</Steps>

## 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](/webhook) page):

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

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

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