Productboard connector FAQ
This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Productboard from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Productboard ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports features, products, components, feature statuses, notes, companies, users, members, release groups, releases, objectives, key results, initiatives, teams, feature and component relationships, and entity and note field definitions. See Supported source tables.
How far back can the connector ingest data?
For the notes table, the first sync ingests notes updated on or after start_datetime, which defaults to 2020-01-01T00:00:00Z. Each later sync ingests notes updated after the last run. The connector reingests all other tables in full on every run.
Which authentication methods does the connector support?
The connector supports Productboard Server-to-Server OAuth, which uses a JSON Web Token (JWT) signed with your private key. It doesn't support OAuth U2M, basic authentication, or API tokens.
How does the connector store custom fields?
Productboard returns built-in and custom field values together, with custom fields keyed by ID. The connector stores them in the fields column as VARIANT. To look up a custom field's name and type, join on field_definitions or note_field_definitions.
Does the connector capture deleted records?
Only for notes. When a note is archived in Productboard, the connector marks it deleted in the notes table. The connector doesn't detect permanently deleted notes. Full-refresh tables reflect the current state on every sync.