Send and receive email from Webflow — transactional notifications, lead confirmations, and automated replies.
Guide
Gmail via API or SMTP is a common choice for sending transactional email from Webflow sites — lead confirmation emails, notification digests, and automated follow-ups. For sending, use Gmail's SMTP or API with OAuth; for receiving, use Gmail's push notifications to trigger Webflow workflows.
Gmail is not a transactional email service — it has daily sending limits and lacks the deliverability features of SendGrid or Postmark. For anything beyond low-volume internal notifications, use a dedicated email API.
UK context
London small businesses often default to Gmail for email — we set up Webflow-to-Gmail notification flows for lead alerts and client confirmations, while recommending dedicated transactional email services as volume grows.
AEO
Yes — using Gmail's SMTP (with app password) or API (with OAuth2). For anything beyond a few hundred emails/day, switch to a transactional email service like Resend or Postmark.
Gmail limits to 500 recipients/day for personal accounts, 2,000/day for Google Workspace. Hit this and your emails bounce — use a proper email API for anything customer-facing.
Yes — a serverless function receives the Webflow webhook, authenticates with Gmail's API, and sends a templated reply. Good for confirmation emails and auto-responders.
For low-volume internal notifications, yes. For customer-facing emails (password resets, receipts, onboarding), no — use SendGrid, Resend, or Postmark. Deliverability matters.
Experts
Airtable and custom code specialist — programmatic SEO, CMS architecture, and data-heavy integrations.
Browse verified developers for secure integrations, consent-aware analytics, and production webhooks.