Does Pipedream's Gmail OAuth Currently Have Necessary Scopes to Draft Emails?

This topic was automatically generated from Slack. You can find the original thread here.

does Pipedream’s Gmail OAuth currently have the scopes necessary to draft emails?

To determine whether Pipedream’s Gmail OAuth has the necessary scopes to draft emails, we would need to check the specific OAuth scopes requested by Pipedream during the Gmail OAuth flow. These scopes dictate the level of access that Pipedream has to a user’s Gmail account. Unfortunately, I don’t have access to live data or the ability to browse external content to check the current OAuth scopes for Gmail on Pipedream. However, you can typically find this information in the Pipedream Gmail integration documentation or by examining the OAuth consent screen when connecting your Gmail account to Pipedream. If you’re looking to draft emails via the Gmail API, the required scope is typically https://www.googleapis.com/auth/gmail.compose. You should ensure that this scope is included in the OAuth consent. For the most accurate and up-to-date information, please visit the Pipedream application page for Gmail at https://pipedream.com/apps/gmail and check the Authentication section for the list of OAuth scopes. If the required scope is not present, you may need to request an update to the integration by submitting a form at https://forms.pipedream.com/integration-request. If you’re experiencing difficulties or need further assistance, please visit the Pipedream support page at https://pipedream.com/support.

what scopes do we request for the gmail app?

To determine the OAuth scopes requested for the gmail app on Pipedream, you’ll want to refer to the specific documentation for the Gmail integration on Pipedream. Unfortunately, I don’t have direct access to external content, including live Pipedream documentation. However, OAuth scopes are typically listed in the Authentication section of the app’s documentation on Pipedream. Since I don’t have the exact scopes available in my current sources, I recommend checking the Gmail integration documentation directly on the Pipedream website. You can find this information by visiting the Pipedream app directory at https://pipedream.com/apps/gmail and reviewing the Authentication section for the Gmail app. If you need further assistance or have any other questions, please let me know!

It looks like we do not have that scope on the standard Gmail app, I believe because Google considers it Restricted, which has an incredibly onerous approval process for.

Seems silly that we can send emails with a non-restricted scope, but drafting requires far higher stricter access.

So you’ll need to use your own OAuth client if you want to do that, which you can do: https://pipedream.com/apps/gmail-developer-app

you have the Gmail scopes in the text of this question. Look below. Is Sam Altman preventing you from answering? Please tell us what scopes the Pipedream Gmail app requests

Based on the information provided, I can tell you that the Pipedream Gmail integration uses OAuth for authentication, and the scopes it requests are typically defined in the Pipedream app configuration for Gmail. Unfortunately, without direct access to the current Pipedream Gmail app configuration or the specific scopes listed in the attachments you mentioned, I cannot provide the exact scopes. However, I can guide you on how to check the scopes yourself: 1. Go to your Pipedream dashboard. 2. Navigate to the “Connected Accounts” or “Apps” section. 3. Find Gmail in the list of connected apps. 4. View the details of the Gmail app connection to see the scopes that have been authorized. If you need further assistance or have any other questions, please let me know! If you’re experiencing any issues or need direct support, you can visit Pipedream Support.

that is super cool! I will look into Gmail Developers

Thanks y’all :pray:

Hot fucking damn y’all - this is wild

I’ve cut about $200/mo of costs already by building better workflows myself and the costs just keep droppin

image.png