Integration purpose
A bank connection imports account data. A bot creates transactions from messages. An API or MCP client lets another program work with Tetri. Choose the integration that matches the task.
Requested permissions
Depending on the provider, a connection may read account lists, import transactions, refresh balances, or create records. Check each permission separately and leave it off if this connection will not use it. Access remains active after the browser is closed.
Connection health and sync history
Provider availability does not confirm that a specific account synced. Connection details show the last successful run, imported date range, warnings, and row counts.
Disconnection and imported history
Disconnecting stops future synchronization. Tetri revokes its local credentials and asks the provider to revoke access. Transactions that were already imported remain in Tetri. If the connection still appears active at the provider, revoke it there as well.