Gmail + Drive Automation via Google App (n8n / Make.com)
What you can automate
Gmail: search, read, label, archive, move, send emails, draft emails, attachments
Drive: upload/download, move files, create folders, share links, watch changes (platform-dependent)
How it works
Your automation tool authenticates to Google using OAuth 2.0.
A short-lived access token is used for API calls.
A long-lived refresh token is used to obtain new access tokens automatically.
Supported options
n8n: best when you want maximum control, self-hosting, advanced logic.
Make.com: fastest setup, lots of templates, great for simple flows.docs/quickstart.md
Quickstart
Option A: n8n
Create Google Cloud project + OAuth consent screen
Enable Gmail API + Drive API
Create OAuth client (Web application)
Add n8n redirect URL to Google OAuth client
Create credentials in n8n
Build workflow (examples included)
Option B: Make.com
Use built-in Gmail + Drive modules
Connect your Google account
Build scenario (examples included)
Decision rule
Use n8n if you need custom logic, self-hosting, data control, complex branching.
Use Make if you want speed, easy UI, and standard scenarios.docs/google-cloud-setup.md
Google Cloud Setup (Personal Gmail)
Step 1: Create a Google Cloud Project
Create a new project named like: personal-gmail-automation
Step 2: Enable APIs
Enable:
Gmail API
Google Drive API
Step 3: Configure OAuth Consent Screen
For personal use, select External (most common).
Fill:
App name (ex: “Personal Mail Automations”)
User support email
Developer contact email
Add scopes later (recommended).
Step 4: Add Test Users
Add your personal Gmail address as a Test user.
This is important to avoid blocked consent during testing.
Step 5: Create OAuth Client ID
Create credentials:
Type: OAuth Client ID
Application type: Web application
Add redirect URI(s) for your automation platform (n8n or Make)docs/authentication.md
Authentication details
Access token vs Refresh token
Access token: expires quickly (minutes to an hour), used for requests
Refresh token: long-lived, used to generate new access tokens
Redirect URIs
OAuth requires exact redirect URL match.
n8n: redirect URL depends on:
your n8n base URL
the credential type (Google OAuth2)
Typical patterns (examples):https://YOUR_N8N_DOMAIN/rest/oauth2-credential/callbackhttp://localhost:5678/rest/oauth2-credential/callback
Make.com:
Usually handled automatically with built-in Google connections
Custom OAuth only if you’re doing advanced/enterprise patterns
Personal Gmail and verification warnings
If your app requests “sensitive” or “restricted” scopes, Google may show warnings unless the app is verified.
For personal use, you can usually proceed via:
Test mode
Only you as a test user
Using minimal scopesdocs/n8n-setup.md
n8n Setup (Gmail + Drive)
Prerequisites
n8n instance running (cloud or self-hosted)
Public HTTPS URL recommended for stable OAuth
Step 1: Create Google OAuth credentials in n8n
In n8n:
Credentials → Add new → Google OAuth2 (or Gmail/Google Drive credential type depending on your nodes)
Enter:
Client ID
Client Secret
Auth URI / Token URI (usually defaults)
Set scopes (see below)
Click “Connect” and complete consent
Recommended minimal scopes
Gmail
Read/search only: gmail.readonly
Modify labels/archive: gmail.modify
Sending: gmail.send
Drive
Safer: drive.file (app-created or app-opened files)
Full access: drive (avoid unless truly needed)
Recommended scope sets (pick one)
Set A: Save attachments to Drive + label emailgmail.modifydrive.file
Set B: Full mail processing + folder managementgmail.modifygmail.senddrive
Node mapping
Gmail node: Search → Get message → Download attachments → Modify labels
Drive node: Create folder → Upload file → Move file → Share linkdocs/make-setup.md
Make.com Setup (Gmail + Drive)
Default approach (recommended)
Use built-in modules:
Gmail: Watch emails / Search / Get attachments / Send email
Google Drive: Upload / Create folder / Search files / Move files
Steps:
Create a scenario
Add Gmail module → “Connect” your Google account
Add Drive module → “Connect” your Google account
Run once to authorize
Turn on scheduling
When to consider custom Google App OAuth
Only if you need:
strict control of scopes
you’re migrating off a shared connection
you want separation of tokens by environment
Privacy Policy
App name: AvbgCloud
Last updated: 22 February 2026
Contact email: arynetgroup@gmail.com
1. Introduction
This Privacy Policy explains how AvbgCloud („the App“, „we“, „our“) accesses, uses, and protects information when you connect your Google account to enable automation of Gmail and Google Drive via third-party automation platforms such as n8n or Make.com.
The App is intended primarily for personal use and is not offered as a commercial service to the general public.
By using the App, you agree to this Privacy Policy.
2. What data the App accesses
When you authorize AvbgCloud using Google OAuth, the App may access the following Google data only within the scopes you explicitly approve.
Gmail data (scope-dependent)
Email metadata such as sender, subject, and date
Email content, only if required by the configured automation
Email attachments
Labels and message state (read, archived, labeled)
Ability to send emails, only if explicitly enabled by the user
Google Drive data (scope-dependent)
Files and folders created, uploaded, or accessed by the App
File metadata such as name, size, and creation date
Files uploaded from Gmail automations
File sharing permissions or links, only if configured by the workflow
The App does not access any Google data beyond the scopes granted by the user.
3. How the data is used
Google data is used solely to execute automation workflows explicitly configured by the user, including but not limited to:
saving Gmail attachments to Google Drive
organizing emails using labels or archiving rules
sending notification or reply emails
monitoring Google Drive folders and triggering automated actions
The App does not use Google data for:
advertising or marketing
profiling or behavioral analysis
resale or sharing with third parties
analytics unrelated to automation functionality
4. Data storage and processing
AvbgCloud does not permanently store email or file content unless explicitly configured by the user within their automation platform.
OAuth access tokens and refresh tokens are stored securely by the selected automation platform (for example n8n or Make.com).
Email and file data is processed temporarily and only for the duration necessary to execute the automation workflow.
If the automation platform is self-hosted, the user remains fully responsible for data storage and security.
5. Data sharing
AvbgCloud does not share Google user data with third parties, except:
Google APIs, as required to perform authorized actions
the automation platform used by the user (n8n or Make.com), acting solely as a technical processor
No Google user data is sold, rented, or transferred for commercial purposes.
6. User control and consent
Users retain full control over their data at all times.
You may:
review granted permissions during the Google OAuth consent process
revoke access at any time via Google Account security settings
disable or delete automation workflows at any time
Revoking access immediately stops all data processing by the App.
7. Data retention
AvbgCloud does not enforce fixed data retention periods.
Any retained data depends on the configuration of the automation platform.
Logs, if enabled, should contain only minimal technical information such as message IDs, file IDs, or timestamps.
Users are responsible for configuring retention and deletion policies when using self-hosted automation platforms.
8. Security measures
Reasonable technical and organizational measures are used to protect data, including:
OAuth 2.0 authentication
encrypted credential and token storage (platform-dependent)
least-privilege API scope usage
Despite these measures, no system can be guaranteed to be completely secure.
9. Children’s privacy
AvbgCloud is not intended for use by children under the age of 16 and does not knowingly collect personal data from children.
10. Changes to this Privacy Policy
This Privacy Policy may be updated from time to time.
Any changes will be reflected on this page with an updated revision date.
Continued use of the App after changes constitutes acceptance of the updated Privacy Policy.
11. Contact information
If you have any questions about this Privacy Policy or the App, please contact:
Email: arynetgroup@gmail.com
Google API Services Limited Use Disclosure
AvbgCloud’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.
Application Terms of Service
Application name: AvbgCloud
Last updated: 22 February 2026
Contact email: arynetgroup@gmail.com
1. Acceptance of Terms
These Terms of Service („Terms“) govern your access to and use of the AvbgCloud application („the App“, „we“, „our“).
By accessing or using the App, including authorizing it via Google OAuth, you agree to be bound by these Terms.
If you do not agree to these Terms, you must not use the App.
2. Description of the Service
AvbgCloud enables users to automate actions related to Gmail and Google Drive using third-party automation platforms such as n8n or Make.com.
Typical use cases include:
organizing and labeling emails
saving email attachments to Google Drive
sending automated emails
monitoring Drive folders and triggering actions
The App is intended primarily for personal or internal use and is not provided as a commercial SaaS offering.
3. User Eligibility
You must:
have a valid Google account
have legal capacity to enter into these Terms
be at least 16 years old
By using the App, you represent that you meet these requirements.
4. User Responsibilities
You are solely responsible for:
configuring automation workflows correctly
reviewing and approving Google OAuth permissions
ensuring that automations comply with applicable laws and regulations
securing access to your Google account and automation platform
You acknowledge that automated actions may modify or delete emails or files, and you accept full responsibility for the outcomes of your configurations.
5. Permissions and Google Account Access
The App accesses Google services only through explicit user authorization using Google OAuth 2.0.
Access is limited to the scopes you approve during the consent process.
You may revoke access at any time via your Google Account security settings.
Revocation of access immediately disables all App functionality.
6. Data Usage and Privacy
The App’s handling of personal data is governed by the Privacy Policy, which forms an integral part of these Terms.
In summary:
data is used only to execute user-defined automations
no data is sold or shared for marketing purposes
no unnecessary data is retained by the App itself
7. Third-Party Services
AvbgCloud relies on third-party platforms and services, including:
Google APIs (Gmail API, Google Drive API)
automation platforms such as n8n or Make.com
We are not responsible for:
availability or functionality of third-party services
changes to third-party APIs
data handling practices of third-party platforms
Your use of those services is subject to their respective terms and policies.
8. Availability and Changes to the Service
The App is provided “as is” and “as available”.
We reserve the right to:
modify or discontinue the App at any time
change features, scopes, or functionality
suspend access for maintenance or security reasons
No guarantee is made regarding uptime, performance, or continued availability.
9. Prohibited Use
You agree not to use the App:
for unlawful purposes
to violate Google’s Terms of Service or API policies
to access data without proper authorization
to interfere with or disrupt Google services or automation platforms
to attempt to bypass security or permission controls
Violation of these rules may result in immediate termination of access.
10. Disclaimer of Warranties
The App is provided without warranties of any kind, whether express or implied, including but not limited to:
fitness for a particular purpose
accuracy or reliability
uninterrupted or error-free operation
Use of the App is at your own risk.
11. Limitation of Liability
To the maximum extent permitted by law, AvbgCloud shall not be liable for:
loss of data or emails
unintended automation actions
service interruptions
indirect, incidental, or consequential damages
In all cases, liability is limited to the extent required by applicable law.
12. Termination
You may stop using the App at any time by:
revoking Google OAuth access
disabling or deleting automation workflows
We may terminate or suspend access if these Terms are violated or if required by law or platform policies.
13. Changes to These Terms
These Terms may be updated from time to time.
Changes will be published with an updated revision date.
Continued use of the App after changes constitutes acceptance of the revised Terms.
14. Governing Law
These Terms are governed by the laws applicable in the European Union, without regard to conflict-of-law principles, unless otherwise required by mandatory local law.
15. Contact Information
If you have any questions regarding these Terms of Service, please contact:
Email: arynetgroup@gmail.com