'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Gmail Sending Errors in Power Automate for Desktop
Question details
Users are unable to send emails via Gmail through Power Automate for Desktop, despite the software successfully reading incoming messages.
- Product
- Power Automate for Desktop
- Device & OS
- not provided
- Scenario
- Setting up automated desktop flows that involve sending outbound emails using a Gmail account.
- Observed behavior
- The flow fails during the email sending step, returning errors that state sending is unavailable or that the provided username and password are incorrect.
Verify that your Gmail account is active, log into it through a web browser to clear any pending security alerts, and ensure that 2-Step Verification is enabled on your Google account.
Configure App Passwords and Verify SMTP Settings
Use a dedicated Google App Password and correct SMTP port configurations to bypass strict security blocks placed on third-party applications.
Google often blocks standard password authentication from third-party automation tools to protect user accounts. Generating a 16-character App Password specifically for Power Automate resolves standard 'incorrect password' errors.
Navigate to your Google Account settings, go to the Security tab, and ensure 2-Step Verification is turned on. Then, search for 'App passwords' in the settings bar and generate a new password, labeling it as 'Power Automate'.
Open your desktop flow and double-click the 'Send email' action. Enter your full Gmail address as the username and paste the 16-character App Password (without spaces) into the password field.
Set the SMTP server to 'smtp.gmail.com'. Set the server port to 465 and enable SSL, or set the port to 587 and enable TLS. Save the action and run a test flow.
Consult the Power Automate Community for Connector Issues
If standard SMTP configuration fails, the issue may stem from temporary connector limitations or Microsoft updates requiring specialized community assistance.
Boost Your Workflow Efficiency with WPS Office
While troubleshooting Microsoft Power Automate flows, you might also be looking for a lighter, cost-effective office suite to handle your daily tasks. WPS Office provides an all-in-one, robust solution for your document processing needs without the steep learning curve.
- 1. Download the Installer: Visit the official WPS Office website and download the free version for your operating system.
- 2. Install the Suite: Run the setup file and follow the on-screen prompts to complete the lightweight installation process.
- 3. Create and Edit Files: Open WPS Office to instantly start working on your documents, spreadsheets, and presentations with a familiar interface.
Frequently Asked Questions
Why does Power Automate report my correct Gmail password as incorrect?
Google's security policies actively block third-party applications from logging in using standard account passwords. You must enable 2-Step Verification and create a dedicated App Password for Power Automate to authenticate successfully.
What are the correct SMTP settings for sending Gmail in Power Automate?
The outgoing mail server should be configured as 'smtp.gmail.com'. You can either use port 465 with SSL enabled, or port 587 with TLS enabled. Make sure the 'Enable SSL/TLS' option in your flow action matches the chosen port.
Is it better to use the native Gmail connector or the standard SMTP action?
The native Gmail connector is generally easier to set up via OAuth, but it is sometimes subject to strict API limits or corporate Google Workspace policies. If the native connector fails, falling back to the 'Send email' (SMTP) action using an App Password is a highly reliable alternative.
