Connect your data and apps
Connections make external sources available to dashboards and Ask. Configure them under Settings → Connections.
| Connection | Dashboards | Ask |
|---|---|---|
| PostgreSQL | Query with SQL blocks | Yes |
| Snowflake | Query with SQL blocks | Yes |
| Connected apps | Call tools with MCP blocks | Yes, when the app exposes tools |
| GitHub | Use repository code as context | Manage verified queries and guidance |
PostgreSQL
Section titled “PostgreSQL”Under Connections → Data, provide a connection string:
postgresql://user:password@host:5432/databaseAfter the connection succeeds, its tables and views appear in the dashboard catalog. SQL blocks can query the connection by name, and Ask can use it as a source.
Snowflake
Section titled “Snowflake”Under Connections → Data, provide either a Snowflake connection string or the account locator (org-account), user, password, warehouse, database, schema, and optional role.
BitBoard authenticates for each query; it does not keep a persistent Snowflake session open.
Connected apps
Section titled “Connected apps”Under Connections → Apps, connect a supported app:
- Amplitude
- Linear
- Notion
- PostHog
- Ramp
- Stripe
Connected apps expose tools through MCP. A dashboard can call them with an MCP block, and Ask can use an app when it has tools available. The tools you see depend on the connected provider and your authorization.
GitHub repositories
Section titled “GitHub repositories”Under Connections → Code, connect the repository that contains your analytics code and Ask configuration.
Dashboard agents can use the indexed repository as context. Ask uses a repository’s bitboard/ directory for verified queries and guidance.
Credential handling
Section titled “Credential handling”Connection credentials are encrypted at rest. BitBoard uses them to make authorized requests and does not return stored credentials to the application after they are saved.