Will RecordX read my Gmail inbox?

No. The planned scope uses the gmail.compose scope, which only creates drafts and cannot read the inbox. Optional inbox-read scopes (gmail.readonly or gmail.modify) would only be requested if a user opts into thread-context features later.

Will RecordX auto-send follow-up emails on my behalf?

No. Auto-drafts are drafts - nothing leaves the outbox without a human click. RecordX will not gain send-on-your-behalf permission without explicit opt-in.

Does the Gmail integration need Google Workspace admin approval?

Workspace admins can restrict which OAuth apps their users grant. RecordX will submit the Gmail scope for Google's verification review (already verified for Calendar) so admins can approve it at the tenant level.

Can I use Zapier or Make to bridge RecordX and Gmail while I wait?

Once RecordX exposes an outbound webhook (also on the roadmap), Zapier and Make will let you wire a "new recording -> create Gmail draft" recipe. Until then, copy-paste from the RecordX summary screen is the fastest path.

RecordX + Gmail

Q: Is the Gmail integration live in RecordX today?

Not yet. Gmail is on the roadmap. RecordX today reads Google Calendar (read-only, for auto-join and event matching) but does not touch Gmail. Email support@recordx.io and we'll notify you when it ships.

Category: notes - Status: planned

Start for free → No credit card required.

How it works

Gmail integration is on the roadmap - not live yet. Today, RecordX reads Google Calendar (read-only, calendar.readonly, for auto-join and event matching) but does not touch Gmail. When live, RecordX will offer one-click auto-drafted follow-up emails in Gmail with the meeting summary and action items pre-filled and pre-addressed to attendees.

Get started with RecordX today

Create your RecordX account at recordx.io/register.html.
Connect Google Calendar under Settings - Integrations. This is what's live today (calendar.readonly). Gmail is not yet part of the OAuth grant.
When Gmail ships, RecordX will extend the Google OAuth request to include gmail.compose (draft creation only, no inbox read). You'll re-consent explicitly on the OAuth screen.
Meanwhile, open RecordX, copy the summary + action items from any recording, and paste them into a Gmail reply by hand.

Get RecordX free

Planned use cases

Send meeting summaries as follow-up emails without leaving the RecordX app.
Format action items with owners and due dates for the recipient.
Keep the follow-up thread tied to the source transcript.

Planned scope

One-click follow-up drafts in Gmail. After a meeting wraps, RecordX will offer a "Draft follow-up" action that composes a Gmail draft with the summary and action items pre-filled, addressed to the meeting attendees (pulled from the calendar event), and ready for a human to review and send. Nothing sends automatically.

Planned OAuth scopes

https://www.googleapis.com/auth/gmail.compose - create and modify drafts only. This scope cannot read the inbox, cannot send, and cannot access any existing messages. Minimum required for the draft flow.
Optional, opt-in only: gmail.modify or gmail.readonly for thread-context features (attaching the draft into an existing thread, pulling prior emails for context). These are not part of the default install.
Nothing is granted today - no Gmail scopes are requested by the current OAuth screen.

Pricing and limits (planned)

Draft creation is expected to be free-tier and above at launch. Google's Gmail API is free to use within the standard per-user quota (1 billion units/day at the time of writing) - drafting a follow-up is a handful of units, so quota is a non-issue in practice.
Follow-up drafts do not count against RecordX recording minutes.

Common concerns

Google Workspace admins can restrict which OAuth apps their users grant. RecordX is already Google-verified for the Calendar scope; the Gmail scope will go through the same verification review when it's added, so admins can approve it at the tenant level.
Auto-drafts are drafts, not sends. RecordX never sends email on your behalf without explicit opt-in to a send scope you'd have to consent to separately.
The gmail.compose scope does not grant inbox access. RecordX cannot read your existing email under this scope, full stop.
The follow-up is addressed to attendees pulled from the connected calendar event, so attendee accuracy depends on the event invite list.

Alternatives while waiting

Zapier and Make (both on the RecordX roadmap) will let you wire a "when new recording, create Gmail draft" recipe once RecordX exposes an outbound webhook. Until either lands, copy-paste from the summary screen in the RecordX web app is the fastest path - one keyboard shortcut, no OAuth required.

Get notified

Email us at support@recordx.io and we'll let you know when Gmail ships.

Related integrations

Start for free