Databricks Lakeflow Connect adds Jira, Confluence, OpenAI connectors

The post frames the problem plainly: a typical company's productivity stack is spread across project trackers, wikis, document stores, inboxes and AI tools, and extracting that data has meant custom pipelines that are slow to build and hard to maintain. Databricks positions Lakeflow Connect as the alternative, with each connector set up through a point-and-click UI or a simple API and data incrementally ingested as managed tables in Unity Catalog, with no infrastructure for the customer to provision. The breadth matters because the post ties it to two use cases that otherwise stay out of reach: AI agents grounded in internal knowledge, and visibility into operational analytics.

Customer examples in the post point at how the connectors are being used. Toyota Finance Australia uses the Jira connector as a fully managed pipeline that the company says handles API complexity and schema changes automatically. VaxCare feeds its Confluence knowledge base into Databricks to ground a chatbot. M3 Accounting reports the GitHub connector was up in minutes and saves about an hour a week, while its SharePoint-fed knowledge assistant was pulling live content within a week. Orizon moved one million tickets from 168 projects with daily syncs it describes as 100% successful.

The AI-usage angle is a separate thread: as generative tools spread across teams, the post says questions arise about spending, adoption and compliance. The OpenAI connector brings in usage, costs, API keys, projects, users and audit logs for attributing spend by team, and the Anthropic connector brings in audit logs, users and roles plus claude.ai chat content. Databricks says this supports a single view of AI usage trends and return on AI investments. The post also notes new connectors are still rolling out.