Send-only Gmail access
Relay asks for gmail.send and basic identity scopes. It cannot read, search, modify, or delete anything in your mailbox.
Relay
Hackathon outreach, without the spreadsheet shuffle.
Relay lets an organizer import a participant list once and hand volunteers a clear queue of recipient sets. Each volunteer sends one BCC message per set from their own Gmail account, and Relay records exactly what went out.
Accounts are created through Neon Auth. Event access still comes only from an organizer’s invitation link.
How it works
- 1
Organizer sets up the event
Create an event, upload the participant list once as CSV or XLSX, and write the mail task: a fixed To address, subject, and body.
- 2
Volunteers join by invitation
Share an event invitation link. It grants access to that one event only — signing in on its own opens nothing.
- 3
One set, one Gmail message
A volunteer picks a set, previews every address, chooses one connected Gmail account, and sends. All recipients go in BCC.
What Relay guarantees
Duplicate-send protection
Idempotency keys, expiring send leases, and deterministic Message-IDs protect normal retries and concurrent clicks. Ambiguous provider failures stay visible for review.
Automatic record keeping
Every send writes an activity entry with the sender, set number, BCC count, and Gmail account used — no shared spreadsheet.
Sets sized for Gmail
Lists are split into sets of about 300 BCC recipients, staying under Gmail’s 500-recipient limit per message.
Your Google account data
Connecting Gmail is separate from signing in. When you connect an account, Relay requests only openid, email, profile, and gmail.send. Messages are sent only when you press send. Stored tokens are encrypted, and you can disconnect an account inside Relay or revoke access at myaccount.google.com/permissions at any time.
Relay’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.