How to Switch to the New Gmail App in make.com
The new Gmail app in make.com is now available, and all users should start migrating their existing Gmail workflows to this updated integration as soon as possible. This guide explains what has changed, how to move your scenarios, and what deadlines you must follow to keep everything running smoothly.
Overview of the New Gmail App in make.com
The old Gmail app in make.com is being deprecated in favor of a new version that uses the latest Gmail API. The new app provides improved reliability and complies with updated Google policies.
You should start moving any workflows that still rely on the legacy Gmail app to the new integration to avoid interruptions in email automation.
Key Changes Between Old and New Gmail App
The migration affects how your Gmail modules are authenticated and which app you select in your scenarios. The core email capabilities remain similar, but connections must be recreated under the new app.
Main differences in Gmail integration on make.com
- The legacy Gmail app is being replaced by a new Gmail integration.
- New scenarios should use only the new Gmail app in make.com.
- Existing scenarios on the old app must be updated and reconnected.
- All connections need to be authenticated again with Google using the new app.
Although the modules will look familiar, you should review each scenario after migration to ensure that triggers, filters, and mapping still behave as expected.
Migration Timeline and Support Details
The new Gmail app is already released and ready for production use. The legacy Gmail app will remain available for a limited time to help you transition.
Support period for the legacy Gmail app in make.com
- You can continue to run existing scenarios on the old Gmail app for now.
- Support will gradually be reduced as the new integration becomes the standard.
- At a later date, the deprecated app will stop working and may be removed from the scenario editor.
Because timelines may evolve, always refer to the official announcement and status information on the Gmail app update page for the latest details.
Preparation Before Migrating Gmail Scenarios
Before changing any live workflows, prepare an inventory of every scenario that uses the legacy Gmail app in make.com. This will help you plan testing and avoid missing critical automations.
Step 1: Identify scenarios using the old Gmail app
- Open your make.com dashboard.
- Review your list of scenarios and look for modules labeled with the legacy Gmail app icon or name.
- Note each scenario, its purpose, and whether it is business critical.
Focus first on high-impact use cases such as customer communication, order confirmations, and internal alerts.
Step 2: Communicate with stakeholders
- Inform your team that the Gmail integration is being updated.
- Agree on a testing window and possible downtime, if any.
- Document any specific requirements or custom logic that must be preserved.
Clear communication makes the move to the new Gmail app in make.com smoother and reduces the risk of missed notifications.
How to Switch a Scenario to the New Gmail App in make.com
Once you have a plan, start migrating scenarios one by one. The safest way is to duplicate an existing scenario and update the copy to use the new Gmail app.
Step-by-step migration workflow
- Duplicate the old scenario
- In make.com, locate the scenario using the old Gmail app.
- Create a duplicate so your original workflow remains intact as a backup.
- Replace legacy Gmail modules
- Open the duplicated scenario in the editor.
- For each legacy Gmail module, click to edit it.
- Remove the old module and add the equivalent module from the new Gmail app.
- Create a new Gmail connection
- When prompted by the new Gmail module, create a fresh connection.
- Allow make.com to access your Gmail account using the Google consent screen.
- Save the connection and confirm that the module loads the appropriate fields.
- Remap fields and settings
- Compare the old and new modules side by side.
- Remap sender, recipients, subject, body, labels, and attachments as needed.
- Recreate filters or search queries if the module configuration has changed.
- Validate triggers and filters
- Check any triggers that start the scenario, such as new email or label-based triggers.
- Review router branches, filters, and conditions referencing Gmail fields.
- Run test executions
- Turn on the scenario in test mode or run a manual execution.
- Send a test email or trigger event to confirm behavior.
- Check logs, email output, and downstream modules for errors.
- Switch over to the new scenario
- Once tests pass, disable the old scenario.
- Enable the new scenario that uses the updated Gmail app in make.com.
- Monitor logs closely for the first hours or days.
Best Practices for a Smooth Gmail Migration
A structured approach will help keep your email automation stable while adopting the new Gmail app in make.com.
Testing and validation tips
- Test with multiple Gmail accounts if your organization uses shared inboxes or aliases.
- Verify that HTML formatting, attachments, and signatures render correctly.
- Confirm that error handling paths still behave as expected.
Operational recommendations for make.com users
- Document which scenarios have been fully migrated to the new Gmail app.
- Schedule periodic reviews to ensure no legacy Gmail modules remain.
- Keep a change log so your team knows when each workflow was updated.
If you manage large automation stacks or need expert guidance on migration strategy, configuration audits, or scaling your automations, you can also consult specialists such as Consultevo for personalized support.
Troubleshooting Common Issues in make.com Gmail Migration
During the switch to the new Gmail app in make.com, you may encounter configuration or permission problems. Addressing them early keeps your scenarios reliable.
Authentication and permission problems
- If the new Gmail connection fails, confirm that you are logged into the correct Google account.
- Ensure that the Google account has not restricted access to third-party apps.
- Recreate the connection if scopes or permissions were changed.
Module configuration mismatches
- Compare legacy and new modules to confirm that all required fields are mapped.
- Update search queries or labels if the module requires a slightly different syntax.
- Re-test each path that previously depended on Gmail-specific outputs.
If problems persist, review the official documentation, verify that you are using the latest version of the app, and check the update notes on the new Gmail app announcement page.
Staying Up to Date with make.com Changes
Because platforms evolve, staying informed about updates to Gmail and other apps in make.com helps you avoid surprises and keep your workflows compliant.
- Subscribe to product update feeds or newsletters.
- Periodically review key scenarios that rely on external services like Gmail.
- Maintain documentation for critical automations so changes are easy to track.
By following the steps in this guide and keeping an eye on official announcements, you can successfully transition to the new Gmail app in make.com and maintain reliable, modern email automation across your organization.
Need Help With Make.com?
If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.