Gmail automations
Email · 7 integrations · 35 workflow guides
Automating Gmail is one of the most common starting points for workflow automation — routing incoming emails to CRMs, triggering notifications in Slack, logging messages to spreadsheets, or sending templated replies based on labels or senders. Most teams automate Gmail to eliminate manual triage and ensure nothing falls through the cracks across tools like Salesforce, HubSpot, or Pipedrive. Choosing the right platform matters because Gmail's underlying API has hard per-user quotas, a non-standard webhook architecture, and OAuth token behaviors that catch many automations off guard.
What it costs to automate Gmail
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Gmail integrations
Each page compares all five platforms for that pair.
Popular Gmail workflow guides
Step-by-step setup instructions for specific automations.
How to Forward Meeting Emails from Gmail to Slack with Zapier
Automatically detects meeting-related emails in Gmail and posts the subject, sender, and body to the appropriate Slack channel so your team sees external commitments in real time.
How to Forward Gmail Meeting Notes to Slack with Make
Watches Gmail for emails containing meeting notes, action items, or external meeting confirmations, then routes the content to the appropriate Slack channel automatically.
How to Forward Gmail Meeting Emails to Slack with n8n
Polls Gmail for emails containing meeting notes or action items, classifies them by type, and routes them to the correct Slack channel automatically.
How to Forward Gmail Meeting Notes to Slack with Power Automate
Monitors Gmail for emails containing meeting notes or action items and forwards them to the appropriate Slack channel so your team stays informed without being CC'd.
How to Forward Gmail Meeting Notes to Slack with Pipedream
Watches Gmail for emails containing meeting notes or action items and forwards a formatted summary to the appropriate Slack channel in real time.
How to Broadcast Gmail Project Updates to Slack with Zapier
When a labeled Gmail message arrives from a vendor or stakeholder, Zapier automatically posts the sender, subject, and a trimmed body excerpt to the matching Slack project channel.
How to Broadcast Gmail Project Updates to Slack with Make
Watches a Gmail label for incoming project update emails and posts their sender, subject, and body summary to a designated Slack channel automatically.
How to Broadcast Gmail Project Updates to Slack with n8n
Polls Gmail for labeled project emails and posts the sender, subject, and a trimmed body excerpt to the matching Slack channel automatically.
How to Broadcast Gmail Project Updates to Slack with Power Automate
Automatically posts Gmail messages matching project-related labels or subject filters into the correct Slack channel, keeping distributed teams informed without anyone forwarding emails manually.
How to Broadcast Gmail Project Updates to Slack with Pipedream
Watches Gmail for labeled project-related emails and instantly forwards their sender, subject, and body snippet to the matching Slack channel.
Gmail triggers & actions by platform
Which capabilities each platform supports for Gmail.
| Capability | Zapier | Make | n8n | Power Automate | Pipedream |
|---|---|---|---|---|---|
| Triggers | |||||
| New Email | ✓ | ✓ | — | ✓ | ✓ |
| HTTP Webhook | — | — | ✓ | — | ✓ |
| New Email (Gmail) | — | ✓ | — | — | ✓ |
| New Labeled Email | ✓ | — | — | — | ✓ |
| Schedule | — | — | ✓ | — | ✓ |
| Webhook | — | — | ✓ | — | ✓ |
| App Event Source | — | — | — | — | ✓ |
| App-specific trigger | — | — | — | — | ✓ |
| Email Flagged | — | — | — | ✓ | — |
| Email Labeled | ✓ | — | — | — | — |
| Actions | |||||
| Send Email | ✓ | ✓ | — | ✓ | ✓ |
| Create Deal | ✓ | — | ✓ | — | ✓ |
| Create Person | ✓ | — | ✓ | — | ✓ |
| Create Record | — | ✓ | — | ✓ | ✓ |
| HTTP Request | — | ✓ | ✓ | — | ✓ |
| Send Email (Gmail) | — | ✓ | ✓ | — | ✓ |
| Send Message | — | ✓ | ✓ | — | ✓ |
| Update Deal | ✓ | — | ✓ | — | — |
| Add a Row | — | ✓ | — | — | — |
| Add Label to Email | ✓ | — | — | — | — |
Things to know about automating Gmail
No Native Webhooks
Gmail does not support traditional webhooks. Instead it uses Google Cloud Pub/Sub for push notifications — a setup that requires creating a Pub/Sub topic, configuring permissions for [email protected], and calling the watch method at least once every 7 days or notifications silently stop arriving with no error message.
Sending Limits By Account Type
Free Gmail accounts are capped at 500 outbound emails per day; Google Workspace accounts can send up to 2,000 per day. Each outbound email is also limited to 500 recipients, and exceeding daily limits can block sending for multiple hours before the API recovers.
OAuth Scopes Affect Setup Time
Gmail API scopes are tiered: non-sensitive, sensitive, and restricted. Apps requesting restricted scopes (such as full mailbox read access) must pass an annual third-party security audit, and brand verification alone takes 2–3 business days. For internal Google Workspace automations, Workspace admins can exempt apps from this process entirely.
Polling vs. Push Efficiency
Polling Gmail every 5 seconds consumes approximately 17,280 API calls per day against your quota; push notifications via Pub/Sub reduce that to only calls triggered by actual changes. n8n's Gmail Trigger node uses polling by default, while platforms like Zapier and Make abstract the push setup but still operate within the same underlying quota constraints.
Refresh Token Expiry Trap
Google enforces a hard limit of 100 refresh tokens per Gmail account per OAuth client ID — when the 101st token is issued, the oldest is silently invalidated. Apps in 'Testing' mode (common when first building automations in n8n or Pipedream) receive tokens that expire in 7 days, which is a frequent cause of broken workflows that were working fine during development.
Bulk Sender Enforcement (Nov 2025)
As of November 2025, Gmail actively delays or rejects non-compliant messages from senders exceeding 5,000 emails per day to Gmail addresses — not just spam-filters them. Compliance now requires SPF, DKIM, and DMARC authentication, a spam complaint rate below 0.3%, and one-click unsubscribe headers processed within 2 days.
What breaks at scale
Hitting the daily sending limit does not produce an immediate hard stop — there is a lag of several minutes before Gmail's API starts returning 429 errors, meaning your automation platform may log successful 200 responses for emails that were never actually delivered. After the limit is reached, the block can persist for multiple hours. If you are sending transactional or CRM-triggered emails through Zapier, Make, n8n, Power Automate, or Pipedream and approaching these thresholds, you have no reliable in-band signal that messages failed until you audit delivery separately.
If you are relying on Gmail push notifications via the Pub/Sub watch method — which underpins real-time triggers in most platforms — and your renewal process fails or was never set up, notifications stop arriving with zero error output. Workflows appear healthy in Zapier, Make, or Pipedream because no failure event is logged; emails simply stop triggering downstream actions. Google recommends calling watch once per day, but many default integrations do not handle this renewal automatically, making this a silent failure mode that can go undetected for days.
The 250 quota units per user per second limit is shared across every application connected to the same Gmail account — meaning if you have Zapier, n8n, and a custom integration all polling or pushing via the same account simultaneously, they compete for the same quota bucket. Under combined load, all three will start receiving 429 throttling errors, and concurrent parallel requests against a single mailbox can trigger a separate 'too many concurrent requests' error. There is no per-app quota isolation; the only fix is reducing polling frequency, consolidating integrations, or using a dedicated Workspace account for automation traffic.
Frequently asked questions
Which automation platform is best for Gmail workflows — Zapier, Make, n8n, Power Automate, or Pipedream?
The best choice depends on your volume and technical comfort. Zapier is the fastest to set up and works well for simple trigger-action flows, but costs scale quickly with task volume. Make offers more complex branching at a lower per-operation cost. n8n gives the most granular control over Gmail operations including label management, but connecting it requires roughly 31 manual steps and a Google Cloud Platform account. Power Automate integrates well if your organization is already in Microsoft 365. Pipedream suits developers who want code-level control and event-driven pipelines without managing infrastructure.
Why did my Gmail automation stop receiving new emails or triggers?
The most likely cause is a Gmail API watch expiration — Gmail's push notification system requires the watch method to be renewed at least every 7 days, and when it lapses, notifications stop silently with no error returned. OAuth refresh token invalidation is another common culprit: tokens expire after 7 days in apps still in 'Testing' mode, and Google also invalidates the oldest token when a user exceeds 100 active tokens per OAuth client. All five major platforms (Zapier, Make, n8n, Power Automate, Pipedream) are subject to these underlying API behaviors.
What are Gmail API rate limits and how do they affect automation workflows?
The Gmail API enforces 1,000,000,000 quota units per day at the project level and 250 quota units per user per second — and these limits are shared across all applications connected to the same Gmail account simultaneously. When limits are exceeded, Google returns HTTP 429 errors, but there is a delay of several minutes before 429s appear even after the quota is already exhausted, meaning a 200 OK response does not guarantee the email was actually sent. This affects every platform including Zapier, Make, n8n, Power Automate, and Pipedream, since they all call the same underlying Gmail API.
Can I automate Gmail to log emails into Google Sheets, HubSpot, or Salesforce automatically?
Yes — logging incoming or outgoing Gmail messages to Google Sheets, Salesforce, HubSpot, Pipedrive, or Attio is one of the most common Gmail automation use cases across all five major platforms. Zapier and Make offer pre-built templates for most of these pairs. In n8n and Pipedream you have more control over filtering by label, sender, or subject before writing to your CRM. The main constraint to plan for is Gmail's 250 quota units per user per second, which can become a bottleneck if you are processing high volumes of incoming messages in real time.