Skip to content
FastBI Docs Docs
Pricing examples Open app

Choose a connector

Connections give FastBI access to a source. Open Connections → Add connection and choose the provider. The setup wizard follows three steps:

  1. Access configuration: enter credentials or complete the provider’s authorization flow.
  2. Connector choices: choose the databases, accounts, reports, or other source settings FastBI should use.
  3. Name your connection: enter a display name and a slug where offered, then save.

Use Back to review earlier choices without losing your inputs. Only the final save creates the connection and starts its synchronization or import. Athena uses the equivalent labels AWS access, Athena settings, and FastBI connection.

Add connection menu showing warehouse, database, and advertising providers
Choose a provider from the connection-type menu. Scroll to see more providers.
Step two of PostgreSQL setup with a database field
After configuring access, choose the source settings for this connection.
Step three of PostgreSQL setup with display name and Save and test
Name the connection in the final step, then save and test.

Warehouses and databases

Section titled “Warehouses and databases”

Advertising and app sources

Section titled “Advertising and app sources”
  • Advertising connectors — Meta Ads, Google Ads, and TikTok Ads.
  • App Store Connect — app metadata and Lake synchronization for report analysis.
  • Google Play — authentication, report selection, daily Lake synchronization, and import troubleshooting.
  • Firebase — Firebase context associated with a BigQuery connection.

MCP and files

Section titled “MCP and files”
  • MCP integrations — connect an external MCP data source or an AI client to FastBI.
  • Files and Lake — upload files with Private or Organization visibility.

Credentials and cancellation

Section titled “Credentials and cancellation”

Uploaded service-account JSON and private keys used to validate access are not saved as files in FastBI’s upload library. Cancelling an unsaved setup discards the entered credentials. Temporary Meta and Google Play authorization is removed on cancellation and expires after 15 minutes if setup is abandoned. If authorization expires, start again.

When editing a saved connection, leave credential fields blank where the form offers to keep the existing credentials. Cancelling an edit preserves the saved connection. Your original credential file on your computer is not deleted.

After connecting

Section titled “After connecting”

Wait for synchronization and inspect Catalog or the provider’s enrichment data. Catalog synchronization discovers metadata; it does not mean every source has been copied into Lake.

If a connection fails, check credentials, source permissions, network access, and the error shown in FastBI. Never paste passwords, private keys, or access tokens into an analysis conversation.