Hi,
I’ve set up a Gmail connector in Gemini Enterprise and am hitting a wall where
the agent consistently returns “the tool required to send emails is currently
unavailable” despite everything appearing correctly configured. Sharing full
setup details in case others are hitting the same issue.
Setup:
- Gemini Enterprise Plus (free trial) + Standard (paid, yearly)
- Single app: VIDAR Intelligence Interface
- Gmail, Calendar, and Drive connectors — all showing Connector state: Active,
Action state: Active - OAuth configured with correct scopes (gmail.send, gmail.readonly,
gmail.modify) and redirect URI:
https://vertexaisearch.cloud.google.com/oauth-redirect - Workspace Admin toggle “Allow Gemini Enterprise to access Google Workspace
data” is enabled for Standard/Plus/Frontline - User license confirmed as Gemini Enterprise Plus
- Actions enabled at data store level (Send Email: Enabled)
- Actions enabled at user level via the connector panel in the chat UI
Behavior:
Agent can search and read Gmail successfully. When asked to send an email —
with any phrasing, including explicit “Use the Send Email action” — it returns
“the tool required to send emails is currently unavailable. I can only search
your existing emails.”
What I’ve tried:
- Deleted and recreated all three connectors (Gmail, Calendar, Drive) from
within the app via Connected data stores → New data store - Re-authenticated OAuth after fixing redirect URI mismatch (was oauth-redirect2,
corrected to oauth-redirect) - Enabled Google People API and Cloud Search API
- Started fresh chat sessions with actions enabled in connector panel
- Explicit action invocation prompts
Questions:
- Is the Send Email action actually functional on Standard/Plus trial accounts,
or is there a known restriction? - Is there a step between enabling the action at data store level and it being
surfaced to the agent that we’re missing? - The App-level Actions page shows “No actions set up yet” with a greyed-out
Add Action button and tooltip saying “Actions can now only be added by
creating a data connector” — is this expected behavior or indicative of a
configuration issue?
Any guidance appreciated. Happy to share screenshots or logs.