Gemini Enterprise Gets an Asana Connector: Search, Read, and Create Tasks with Natural Language
Google's Asana data store connector for Gemini Enterprise is now in Public Preview, letting users search, read, and create Asana projects and tasks via natural language.
Google has added an Asana data store connector to Gemini Enterprise, now available in Public Preview. If your team runs its work through Asana, this is worth paying attention to.
What the Asana connector actually does
The connector gives Gemini Enterprise users two distinct capabilities: reading and writing.
On the read side, you can search across your Asana projects, workspaces, teams, and tasks using plain natural language. Think asking questions like “what tasks are assigned to me this week in the product launch project” rather than navigating menus. Gemini Enterprise pulls the relevant information from your connected Asana account and surfaces it directly in the conversation.
On the write side, you can create projects and tasks without leaving Gemini Enterprise. That means a workflow that might have previously involved switching apps, copying context, and filling in fields can now happen in a single conversational interface.
This makes it a genuinely bidirectional connector, which puts it in a slightly different category from read-only integrations.
How the setup works (and what admins need to know)
Actions and search are configured separately. That is worth flagging clearly because it is easy to assume they are part of the same setup flow.
For search, admins connect the Asana data store and configure data sync. For actions (the write capability), a separate OAuth 2.0 (3LO) app is required with action-specific scopes and redirect URIs. The good news: you can configure actions even if the connector ingestion failed, so the two are genuinely independent.
On data sync, Gemini Enterprise supports full syncs that capture the entire state of your Asana account, including additions, updates, and deletions, replacing existing data store contents. Admins can monitor connector activity using the DataConnector Request Count metric in Metrics Explorer, which reached general availability at the same time as these connector updates.
A few constraints to be aware of:
- The Asana data store is only supported in the global, us, and eu locations.
- Enforcing VPC Service Controls on existing Asana data stores is not currently supported. If you need VPC Service Controls, you would need to delete and recreate the data stores.
- It is recommended to associate only one data store with actions belonging to a single connector type.
The connector is available on the Standard, Plus, and Frontline editions of Gemini Enterprise.
Where Asana fits alongside Crossbeam and MCP
The Asana connector is joining two other connectors that also entered Public Preview recently, and together they tell a clear story about where Gemini Enterprise is heading.
Crossbeam brings in partner ecosystem data, useful for revenue and partnerships teams who need to cross-reference their pipeline against partner overlaps without hopping between tools.
Custom MCP servers allow organisations to connect Gemini Enterprise to private internal tools, custom data sources, or any MCP-compliant third-party system. This one is off by default and requires an Organisation Policy Administrator to remove the relevant organisation constraint before enabling it. It is the most flexible of the three, but also the most configuration-heavy.
Asana sits in between: a widely-used, commercially available work management tool with a well-defined set of objects (projects, tasks, teams, workspaces) that maps neatly to the kind of questions knowledge workers ask every day.
Together, these three connectors represent different points on a spectrum from structured SaaS data (Asana) to partner-facing data (Crossbeam) to fully custom private data (MCP). Admins can mix and match depending on what their teams actually need access to.
What this means for you
If you are a Gemini Enterprise user whose team tracks work in Asana, the practical upside is reducing context-switching. Instead of moving between Gemini and Asana to find a project status or spin up a new task, you can do both from the Gemini interface. That is a modest but real quality-of-life improvement for anyone who lives in both tools.
If you are an IT administrator or Workspace admin, there is some configuration work involved, particularly around the separate OAuth setup for actions. But it is a one-time setup, and the monitoring tooling now in GA means you will have visibility into connector usage once it is running.
If you are evaluating Gemini Enterprise more broadly, the trajectory here is worth noting. Google is steadily adding connectors to the platform alongside existing support for Confluence, Jira, SharePoint, and ServiceNow. The Crossbeam and MCP additions show that this is not just about indexing popular SaaS tools. The MCP connector in particular opens the door to a much wider range of enterprise data sources without waiting for Google to build a dedicated connector for each one.
Asana has been public about its ambition to connect with AI assistants across platforms, including Microsoft 365 Copilot, Claude, and Gemini. The Gemini Enterprise connector is a concrete step in that direction, giving Asana data a more active role in AI-assisted workflows rather than just sitting in a separate tab.
The feature is in Public Preview now. If you want to explore the setup, Google’s Asana connector documentation covers the full configuration steps, including the OAuth requirements for enabling actions.