Zapier Update: Changes to Our Consumer Gmail Integration

Upcoming changes to how Zapier works with consumer Gmail accounts (those that end in @gmail.com or @googlemail.com) will affect your Zaps starting May 26, 2019. In some instances, you'll need to take action to keep them running—we'll email you if so.

In preparation for the changes, we've collected the most common questions so far. As always, if you have additional questions, please contact our team—we're happy to help!

Why are Gmail integrations on Zapier changing?

Security is of the utmost importance at Zapier. So, when Google opened up the opportunity to work with them on a new set of security standards for their Gmail API integrations, we jumped at the chance. Google is making these changes to better manage how third-party apps like Zapier earn users' permission to read, write, or send email from consumer Gmail accounts.

How do I check if these changes affect my Zaps?

To know if you'll see changes to your Zaps on May 26, 2019, ask yourselves these questions:

1. Are you using a @yourdomain.com Gmail address?

If you are using a paid G Suite account, your Zaps will not be affected. They will continue to work as expected, and you can stop reading here.

2. Are you using a @gmail.com or @googlemail.com Gmail address?

If you are using a consumer Gmail account, some of your Zaps may be affected. Continue reading for further clarification.

3. Are you sending data to Gmail from other apps?

If you are sending data to Gmail (sending email or creating drafts), your Zaps will not be affected. They will continue to work as expected, and you can stop reading here.

4. Are you sending data from Gmail to other apps?

If you are triggering on data from Gmail, your Zaps may be affected. Read on for further clarification.

5. What apps are using your Gmail data?

If you are sending data only to other Google apps (like Sheets or Docs), your Zaps will not be affected. They will continue to work as expected, and you can stop reading here.

If you are sending data only to built-in Zapier apps (like Code or Translate, with the exception of Phone/SMS), your Zaps will not be affected. They will continue to work as expected, and you can stop reading here.

If you are sending data to Google-approved apps (like Trello or Asana), you will need to reconnect some accounts. We will send you an email with instructions on how to complete these tasks by June 26, 2019.

For all other apps (like Twilio or Twitter), your Zaps may be affected. You will receive an email this week with notifications for each affected Zap that needs to be updated by May 26, 2019.

Why isn't my app a Google-approved app?

Working with Google on these security steps means we're able to continue to offer our Gmail integration. But as a connector to more than 1,500 apps, it also means that we needed to prioritize which apps we included as part of the initial security check for Google.

If your app of choice is not Google-approved, it is because it was not part of the initial batch of reviewed apps. If your Zap depends on this app's functionality, we recommend seeking an alternative app in the meantime—we also want to hear your requests for the next set of apps to review.