Google Drive and Google Calendar are listed separately in the connection Marketplace. Connect the service your task actually needs, and read the permissions shown by Google.
Ask for the service in chat
Ask the agent for the Google Drive or Google Calendar connection card, naming the task and account you intend to use. For example: “Show the Google Drive connection card. Wait while I authorize it; do not edit or share any files.” Review the permissions, return to Clero, and verify the required tool access.
Find the service in Settings
- Open Settings → Connect Apps → Marketplace.
- Search for Google Drive or Google Calendar.
- Inspect the card and choose the intended Google account during any authorization flow.
A Google sign-in to Clero is not, by itself, evidence that these integrations are connected. Check the Connected tab.
Work with Drive files
Clero’s published policy describes access to files it creates and files explicitly selected for it, rather than all files in a Drive account. Start with the specific file your task needs. Google API scope details.
If a file cannot be found, check that it has been selected or made available through the supported connection flow. Do not assume a filename mentioned in chat gives the agent access to the file.
When asking for a document update, identify the source, the requested change, and whether the result should be a proposed revision or an edit to the original.
Work with Calendar
The policy describes calendar-list access, availability checks, and management of a Clero-created calendar. It does not justify assuming unrestricted access to every event in every calendar. Use the current connection disclosure to establish the scope for your account.
For a scheduling request, provide the intended date, time zone, duration, and participants. Confirm the destination calendar and whether invitations will be sent before creating an event.
Keep access and sharing separate
A connected account does not mean a recipient can open the result. Before sharing a document or invitation, check the intended people and permissions separately.
The documentation demo verified the catalog entries, not the provider authorization flow or end-to-end file and calendar operations. Troubleshoot the exact unavailable operation rather than granting more access by default.