Can You Use Power Automate with Google Workspace? Gmail, Drive & Sheets Explained

Power Automate and Google Workspace: which apps it reaches

Microsoft documents connectors for Gmail, Google Calendar, Google Contacts, Google Drive, Google Sheets and Google Tasks, and all six are listed as Standard in Power Automate. The Gmail page names the same six as the Google services a consumer account can use in a flow. This table puts what Microsoft documents for each one side by side.

Microsoft last updated the Gmail, Drive, Sheets, Calendar, Contacts and Tasks pages between November 2025 and September 2026. Google Docs, Forms, Chat, Meet and Google Directory aren't on the list, and we found no connector for them in Microsoft's documentation.

Our read: the six connectors are good enough when a flow reacts to something in Microsoft 365 and touches Google on the way out, such as sending a message or adding a row. They are weak when a Google event has to start the flow. Drive, Sheets and Google Forms, where much Google-side work begins, can't start one.

Power Automate and Gmail

The Gmail connector covers the basics of mail automation. Its trigger, When a new email arrives, can filter by label, sender, recipient, subject, importance, starred state and attachments. The six current actions are send, reply, search, get details, move to trash and delete. That is the whole list, so a flow can't add a label, archive a message, mark it as read or save a draft without leaving the connector.

Two numbers decide how far it scales. Microsoft caps the connector at 90,000 work units a day and 60 API calls per minute per connection. Sending an email costs 100 work units and a reply costs 105 or more, so sending alone works out to about 900 emails a day before the allowance runs out. The new-email trigger costs 10 units plus 5 per attachment for each message, and even an empty check costs 5.

The trigger also has a documented weak spot. Microsoft says it may skip emails when more than 300 arrive in a 30-second interval, and that on Google Workspace accounts it may intermittently skip emails with attachments, because the Gmail API can take a long time to process them. The suggested workarounds are to keep emails small and attachment-free, to forward the Workspace mailbox to a consumer Gmail account and trigger on that one, or to call the Gmail API through a custom connector.

One restriction applies to consumer accounts only. Flows that use an @gmail.com or @googlemail.com address can connect to a limited list of services, and a flow outside the list is saved in a disabled state. Google Workspace accounts aren't affected.

For sending notifications from a Microsoft-centred flow, Gmail is fine. For mail triage it falls short, because a flow that can't label or archive can't do what triage means.

Power Automate and Google Drive

The Drive connector has actions and no triggers. The page lists eleven: copy, create, update and delete a file, extract an archive, get a file's content or metadata by ID or by path, and list the files in a folder or in the root. Nothing starts a flow when a file lands in a folder or changes, so a "when a file is added" flow has to run on a schedule and list the folder itself.

The connector also stopped being a tabular data source, so it can't feed the Excel connector. The limits are 100 API calls per minute per connection, 10 MB of content length and 1,000 MB transferred per minute per connection.

Shared Drives are the bigger gap. Microsoft's Sheets documentation says spreadsheets in shared drives can't be selected on any platform. On the community forum, a Microsoft employee answered a user who couldn't pick a shared folder with the note that there doesn't seem to be support for shared drives in Power Automate, and pointed to a feature request. We go through the workarounds in our Zenphi vs Power Automate comparison.

We think the missing trigger matters more than any limit in the table. Most Drive automation starts with a file arriving, and a schedule is a poor substitute for that.

Power Automate Google Drive to OneDrive

Copying files from Google Drive to OneDrive is possible, and the direction decides how the flow works. OneDrive has a "when a file is created" trigger, so Microsoft's templates for copying from OneDrive to Google Drive fire as files arrive. Drive has no trigger, so the other direction runs on a schedule. Microsoft Tech Community threads refer to a template named "Copy files from Google Drive to OneDrive on a daily basis".

The pattern is to list the Drive folder, get each file's content and create the file in OneDrive. The Drive connector's 10 MB content length makes large files the first thing to test, and because a scheduled run lists the folder again each time, the flow needs its own way to skip files it has already copied.

Folders are the next snag. In a 2022 Microsoft Q&A thread, a user asked how to copy folders with their files instead of loose files, and a Microsoft community moderator suggested using the Graph API to recreate the folder in OneDrive and the Drive connector to copy the files. A Graph call means an HTTP action.

For a whole-drive move, a flow is the wrong tool. Microsoft's Migration Manager migrates files, metadata and permissions from Google Drive to OneDrive and SharePoint, and Microsoft's admin guide says it moves files from personal and shared drives. Setting it up takes a Google Workspace super administrator to install the Microsoft 365 Migration app. Our rule of thumb: a flow for a small recurring copy, a migration tool for anything you would call a project.

Power Automate and Google Sheets

Sheets gets six actions: get rows, get a row, insert, update and delete a row, and list the sheets in a file. There is no trigger here either, so "when a row is added" is another job for a scheduled flow.

Throttling is the limit that bites first: 100 API calls per connection per 300 seconds. A poster on the Power Platform Community looped over 545 items, inserting one row per item, and the flow failed with a 429 throttling error after about ten minutes. At 100 calls per five minutes, 545 single-row inserts need at least 27 minutes, which is our arithmetic, not a Microsoft figure. The fix suggested in that thread was a Delay action after each call.

The connector page lists a few more quirks. Simultaneous modifications from other flow runs, parallel for-each loops and manual edits aren't supported. Get rows returns 256 rows unless you raise the top count. Column names are encoded, so a column called "Order date" arrives as Order_x0020_date. Shared spreadsheets don't appear in the file picker, so you paste the spreadsheet ID instead.

We would avoid using a sheet as the database behind a looping Power Automate flow. The throttle and the lack of support for simultaneous edits make it a fragile choice.

Power Automate and Google Calendar

Calendar is the best covered of the six, with five triggers (event added, updated, deleted, any change, and event starts) and six actions: create, update, delete, get, list events and list calendars. Triggers poll every 90 seconds, so a reminder flow isn't instant, and the list-events action returns only the first page of arbitrarily ordered events. The limit is 100 API calls per minute per connection. With Tasks, it is one of the two connectors that pair a full set of triggers with a workable list of actions, and the polling delay is the main caveat.

Google Contacts and Tasks

Google Contacts

Contacts offers a create action, a get action and a trigger for contact changes, within 100 API calls per minute. Get my contacts has no pagination and returns at most 1,024 contacts, so anything beyond that is left out of the result.

Google Tasks

Tasks has five triggers and five actions, and it is throttled at 30 API calls per minute, half of Gmail's 60, with triggers polling every 60 seconds. The create action takes a list, a title, notes and a due date. There is no assignee field, so a flow can't hand a task to someone else.

Power Automate and Google Forms

There is no Google Forms connector. The Microsoft Forms connector reads Microsoft Forms, not Google Forms, and we found no connector for Google Forms in Microsoft's documentation. Responses land in a Google Sheet, so the native route is the scheduled flow described above, reading the sheet for new rows. Reading the form itself, including its questions, goes through Google's Forms API, which means an HTTP request or a custom connector. Intake and approval flows tend to start from a form, which is why this is the gap we would flag first.

Docs, Chat and the Admin console

The same gap covers Google Docs, Chat, Meet and Google Directory. We found no connector for any of them in Microsoft's documentation, so a flow that generates a Google Doc, posts to a Chat space or reads Workspace users and groups has to call Google's APIs itself, with an HTTP request or a custom connector.

Both routes are premium. Microsoft's licensing FAQ lists custom connectors among the premium features, and its limits page says you must have a premium or trial license to run any flow that uses a custom connector. The HTTP connectors are classed as premium too. For an automated or scheduled flow only the owner needs a Premium license, but for an instant flow every person who runs it does. Premium costs $15 per user per month, paid yearly, on Microsoft's pricing page.

How to connect a Google account

Connecting is the easy part. The decisions around it are what your IT team ends up owning.

Check your own flow

Pick what your flow starts from and what it does. The checker shows which blocks the Standard Google connectors cover, which need a workaround and which need a premium license. The verdicts come from the Microsoft documentation above. They are a planning aid, not a guarantee that a connector will behave the same way in your tenant.

When to keep it and when to switch

If a Microsoft-centered process touches Google in one or two places, such as sending a Gmail message or adding a Sheets row, the Standard connectors are a reasonable answer and need no premium license. Keep Power Automate for that.

The picture changes when Google is where the process lives. Triggers on Drive, Sheets and Forms, Docs from a template, Directory and Admin actions and Shared Drives are all in the last two columns of the checker. A team that forces Power Automate onto that work often ends up on a premium plan just to rebuild what a Google-native tool includes.

There are two routes from there. Google Workspace Studio covers simple, personal automations, and we compare it with Power Automate in a separate guide. For processes that cross departments, Zenphi is built Google Workspace-first: it triggers on files added to a folder, Google Directory events and incoming email, generates documents from Google Docs templates, and still has native actions for SharePoint, OneDrive and Outlook, so a flow can cross both ecosystems. The full comparison covers where Power Automate is the better choice.

FAQ

Sources

• Microsoft Learn — Gmail connector (updated September 22, 2026)
• Microsoft Learn — Google Drive connector (updated July 17, 2026)
• Microsoft Learn — Google Sheets connector (updated April 25, 2026)
• Microsoft Learn — Google Calendar connector (updated November 25, 2025)
• Microsoft Learn — Google Contacts connector (updated November 14, 2025)
• Microsoft Learn — Google Tasks connector (updated November 14, 2025)
• Microsoft Learn — Power Automate licensing FAQ
• Microsoft Learn — Limits of automated, scheduled and instant flows
• Microsoft Learn — HTTP with Microsoft Entra ID connector (Premium class)
• Microsoft Learn — Migrate Google Workspace to Microsoft 365 with Migration Manager
• Microsoft Learn — Connect to Google with Migration Manager
• Microsoft Q&A — Google Drive folders with content to OneDrive Business (2022)
• Microsoft Tech Community — Copy files from Google Drive to OneDrive for Business
• Microsoft — Power Automate pricing
• Google Workspace Admin Help — Control which third-party and internal apps access Google Workspace data
• Power Platform Community — Throttling error (429) with the Google Sheets connector
• Power Platform Community — Shared Google Drive folder

Connector limits, licensing terms and prices were checked on September 30, 2026 and can change.