What AI works across Google Drive, Slack, Jira, and my data warehouse?

Summary

• Databricks Genie One natively integrates with Slack, Google Drive, and your data warehouse, enabling natural-language queries across all surfaces from a single AI interface.
• For Jira, Lakeflow Connect ingests Jira issues, comments, and metadata into your lakehouse, where Genie can query them with the same governance and natural-language capability.
• All interactions are governed by Unity Catalog policies, ensuring users see only data they are authorized to access across every integration.
• Genie One supports stateful conversations, so follow-up questions build on prior context without requiring you to restate requirements.

What AI works across Google Drive, Slack, Jira, and my data warehouse?
Databricks Genie One is the AI that integrates across Google Drive, Slack, and your data warehouse. It translates natural-language questions into governed SQL queries executed against your Databricks Lakehouse, so you can ask business questions without writing code and get answers that respect your data permissions. For Jira, Lakeflow Connect ingests Jira issues and metadata into the lakehouse, making them queryable by Genie with the same natural-language interface. Genie also connects to cloud-native chat platforms, expanding the surfaces where you can access your data.

How Genie One Integrates with Your Tools

Genie One reaches your data where you work:

Tool	Integration Type	How It Works
Slack	Native	Mention @Genie in channels or DMs to ask questions and get data insights without leaving Slack
Cloud Chat	Native (Beta on some platforms)	Tag Genie in threads to ask context-aware questions about your Databricks data
Google Drive	Native Data Source	Connect Google Drive as an external data source so Genie can extract insights from shared documents
Your Data Warehouse	Direct Connection	Query your Databricks Lakehouse through governed SQL, with automatic row-level and column-level access control
Jira	Via Lakeflow Connect	Ingest Jira issues, comments, and metadata into the lakehouse, then query with Genie like any other data source

Understanding the Integrations

Slack is where Genie surfaces answers in real time. When you ask Genie a question in Slack ("What was our top sales region last quarter?"), Genie translates it to SQL, runs it against your Lakehouse, and posts the answer directly in the channel. Your team stays in flow without switching tools.
Google Drive enables Genie to work with documents, spreadsheets, and presentations you have stored or shared in Google Drive. Genie can read and synthesize insights from this content as part of its knowledge context, so questions can combine drive documents with structured data warehouse queries.
Your Data Warehouse is where the authoritative data lives. Genie executes every query against your Databricks Lakehouse, respecting Unity Catalog governance. If a user lacks permission to a table or column, Genie will not surface that data, even if they ask a question that would otherwise require it.
Jira data is ingested via Lakeflow Connect, Databricks' managed data integration service. Lakeflow Connect pulls Jira issues, comments, and attachment metadata into your lakehouse on a schedule, and Genie can then query that Jira data using natural language (for example, "Show me all high-priority issues assigned to the platform team").

How Governed Access Works

All Genie queries are governed by Unity Catalog. When Genie executes SQL against your lakehouse, it operates under the permissions of the user who asked the question. If you lack access to a dataset, Genie's response reflects that by excluding data you are not entitled to see. This applies across all integrations: Slack, Google Drive, Jira data, and your warehouse tables.
Every Genie interaction is logged for audit purposes, so your data governance team can track who asked what and what results were returned.

Genie Conversation APIs for Custom Integrations

Beyond native chat platform integrations, Genie exposes Conversation APIs (in public preview) that let you embed Genie into your own applications, Databricks Apps, or custom tools. This way, you can build custom AI-driven interfaces that still connect to your lakehouse with the same security and governance.
The Genie Conversation APIs support stateful conversations, meaning Genie remembers the context of your previous questions. If you ask "What was our revenue?" and then follow up with "Break it down by region", Genie understands you mean regions within the prior context.

Jira Ingestion via Lakeflow Connect

Genie does not query Jira directly, but Lakeflow Connect bridges the gap. The Jira connector in Lakeflow Connect is currently in beta on GCP and Azure and supports incremental ingestion, so you do not have to replicate all Jira data every time. Once Jira issues are in your lakehouse, Genie can query them alongside your other business data using natural language and governing access by user permissions.
Authentication uses OAuth (User-to-Machine), and Databricks handles the technical plumbing so you do not need to manage credentials directly.

Why This Matters

Many teams have data scattered across systems: operational data in the warehouse, work tracking in Jira, documents in Google Drive, and conversations in Slack. Genie One centralizes access to all of it through a single AI interface. Instead of logging into five different tools to answer a business question, you ask Genie and get the answer, with all governance and audit trails intact.

FAQs

Do I need separate Genie licenses for each tool?

No. Genie One is a single product that connects to all these surfaces. You get one Genie instance that you can reach from Slack, Google Drive context, or custom applications.

What if I am not a Slack user? Can I still use Genie?

Yes. You can use Genie through the Databricks workspace web UI, embed it in Databricks Apps, or reach it through other chat platforms if you use Azure Databricks. Slack is one option, not a requirement.

Is Jira data kept in sync automatically?

Yes, if you configure Lakeflow Connect to ingest from Jira. Lakeflow Connect supports incremental ingestion, so it pulls only new or changed Jira issues since the last run, keeping your lakehouse reasonably current without reloading everything.

How quickly does Genie return an answer?

Genie translates your question to SQL and executes it. Response time depends on your query complexity and warehouse size, not on the tool you are using. A Slack question and a direct lakehouse query have the same performance characteristics.