Supported destinations
| Destination | Syncs to | Authorization |
|---|---|---|
| Notion | Databases within a page | OAuth |
| Airtable | Tables within a base | OAuth |
| Google Sheets | Sheets within a spreadsheet | OAuth |
| Coda | Sync tables within a doc | API token (via Coda Pack) |
What data can sync
The data types available depend on which bank connections you have: From Plaid, GoCardless, and Mercury connections:- Accounts — balances and account details across all your institutions
- Transactions — spending, income, and transfers with merchant names and categories
- Holdings — investment positions with current values (Plaid only)
- Investment transactions — buys, sells, and dividends (Plaid only)
- Customers — your Stripe customer records
- Products and prices — your product catalog
- Subscriptions — active and past subscriptions with line items
- Invoices — invoice records with line items
How syncs work
When you create a destination, Finta sets up the tables and fields in your chosen tool automatically. Your first sync runs immediately after setup. After that, syncs happen automatically whenever your bank reports new activity. New transactions, updated balances, and investment changes flow into your destination without any manual work. You can also trigger a manual sync anytime from the destination page.Coda works differently. Coda destinations use the Finta Coda Pack with sync tables. Instead of Finta pushing data, you sync from within your Coda doc by clicking the sync button on the Finta pack tables.