Which destination?:

Databricks destination connector

Additional details:

OneSignal uses Powered by Fivetran to sync our customers’ data to their Databricks destinations. Today the Databricks destination connector uses the default User-Agent string from the Databricks JDBC/ODBC driver, and it’s hard-wired in the connector. Neither the Fivetran UI nor the REST API expose a way to override or append to it.

Request: let PBF customers set (or append to) the User-Agent header on requests Fivetran makes to a Databricks destination, so we can pass a partner identifier (eg: “OneSignal”) on our traffic.
Why it matters: Databricks requires partners to identify their own traffic via the User-Agent header to qualify as a validated partner. Without this, Databricks can’t attribute the ingestion we drive to OneSignal, and our partnership with them is blocked. We expect this applies to any PBF customer pursuing Databricks partner validation.

Workarounds already evaluated and rejected by Databricks: a dedicated service principal / PAT for the embedded workspace, and encoding the tenant ID in the catalog/schema naming convention. Databricks confirmed neither satisfies their requirement.
Related: internal Fivetran Jira GTM-1002217 (opened March 2026). Ryan Waldorf and Egidio Terra at Fivetran are aware of this request.