Google Sheets is the most popular Redbark destination. Transactions are written to a sheet (tab) within a spreadsheet you choose.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.
Setup
Connect your Google account
Click Add Destination, select Google Sheets, and sign in with Google. Redbark uses the
drive.file OAuth scope, which only grants access to files Redbark itself creates — it cannot see your existing spreadsheets.Create a new spreadsheet
Enter a name and click the create button. Redbark creates a new spreadsheet in your Google Drive. The first sheet (tab) is selected automatically as the write target.
Multi-account syncing
When you create a sync with multiple bank accounts, an extra step lets you choose how accounts are laid out in the spreadsheet:- Account per tab: each bank account gets its own tab in the spreadsheet. Tabs are created automatically and named after the bank account. This is the default whenever two or more accounts are selected.
- All to one tab: all accounts sync to the same sheet tab. Transactions from every account appear together.
How it works
On each sync, Redbark Sync:- Checks for headers: if the first row is empty, column headers are created automatically
- Reads existing Transaction IDs: column A is scanned to identify transactions that have already been synced
- Appends new rows: only new posted transactions are appended to the bottom of the sheet. Pending transactions are excluded by default to avoid duplicates when they later post with updated details. You can enable pending transactions per sync as an experimental setting.
Transaction columns
| Column | Type | Description |
|---|---|---|
| A - Transaction ID | Text | Unique identifier used for deduplication |
| B - Date | Date | Transaction date |
| C - Description | Text | Transaction description |
| D - Amount | Number | Transaction amount |
| E - Currency | Text | ISO 4217 currency code |
| F - Direction | Text | credit or debit |
| G - Category | Text | Transaction category (if available) |
| H - Merchant | Text | Merchant name (if available) |
| I - Account | Text | Bank account name |
| J - Status | Text | posted (or pending when the experimental include-pending-transactions toggle is enabled) |
| K - Class | Text | payment, transfer, fee, interest, or other |
| L - Post Date | Date | Date the transaction was posted |
Deduplication reads up to the 100,000 most recent rows of column A. Beyond that, duplicates become possible — split the sheet or move older rows to an archive tab if you expect to exceed this.
If you change an account mapping to a different destination account, Redbark resets the sync’s
lastDataAt and backfills the new resource so it doesn’t sit empty.Authentication
Google Sheets uses OAuth 2.0 with refresh tokens. The access token is refreshed on demand when it is within 5 minutes of expiry. If the refresh fails (e.g. you revoked Redbark’s access in your Google account), the sync is classified asdestination_auth_expired and you’ll be prompted to re-authenticate from the destinations page.
Troubleshooting
Permission denied / spreadsheet not accessible If Redbark’s access to the spreadsheet is revoked (e.g. the spreadsheet was deleted, moved out of the connected account’s Drive, or the OAuth grant was removed), the sync is classified asdestination_auth_expired and triggers a re-auth email. Reconnect from the destinations page.
Tips
- Multiple accounts: you can sync several bank accounts in one sync. Use “Account per tab” mode to keep them separated, or “All to one tab” to combine them.
- Formulas are safe: syncs only append rows and never modify existing data. Your formulas, charts, and formatting are preserved.
- Shared spreadsheets: you can share the spreadsheet with others. Only the Google account used to connect needs to grant access to Redbark Sync.