How do I send a calendar invite from a specific Gmail address?

The invite always sends from the Gmail address associated with the Google Calendar where the event was created. So the trick is routing bookings to the right calendar. Meetingpad handles this natively: each identity you connect (each Google account) has its own booking link, and events booked on that link are created on that identity's calendar and sent from that identity's Gmail.

Can Calendly send invites from different addresses depending on the event type?

Calendly Standard ($10/seat/month) has one primary send calendar per Calendly account. To have different event types send from different Gmail addresses, you need Calendly Teams ($16/seat/month) with a seat per identity, or multiple separate Calendly accounts. Meetingpad Pro handles multiple send identities in one app at $8/month flat.

Why does the sender identity matter?

Recipients recognize senders by email address. A prospect at Client A expects your email from you@clientA.com, not from your generic personal Gmail. Getting the sender wrong makes invites look like they're from an outsider, hurts open rates, and can confuse threading in Gmail. For fractional operators managing multiple client engagements, distinct per-link send identities are table stakes.

How to send calendar invites from different Gmail addresses

How Google Calendar decides the sender

The invite always sends from the Gmail address associated with the Google Calendar where the event is created. There's no "spoof sender" option — the calendar owner is the sender. So the trick is routing each booking to the correct calendar.

Approach 1: Log in and out of accounts manually

Free. Painful. If a prospect books via your generic scheduling link, you copy the details, log into the correct Google account, and recreate the event there manually. Works if you have low volume; doesn't scale.

Approach 2: Chrome profiles + Calendly per account

Each Google account gets its own Chrome profile and its own Calendly account (Free or Standard). You hand out N separate Calendly links. Each Calendly sends from its own connected calendar. Works, but the calendars don't see each other, so cross-account double-bookings remain a real risk.

Approach 3: Calendly Teams with one seat per identity

Calendly Teams ($16/seat/month) lets each seat have its own connected calendar and its own send identity. If you have 4 client identities: $64/month. Also gets you unified billing and admin, but you don't need those for a single-user fractional workflow.

Approach 4: Cal.com's per-event-type calendar routing

Cal.com's free individual plan lets you connect multiple calendars and set the "add to" calendar per event type. That effectively routes different event types to different send identities on a single account. Requires manual setup per event type; workable.

Approach 5: Meetingpad's per-identity model

Each Google account you connect to Meetingpad becomes a first-class identity. Each identity has its own booking links. When a guest books on an identity's link, the event is created on that identity's Google Calendar and the invite sends from that identity's Gmail — automatically. No per-event routing, no seat multipliers, no manual calendar switching.

Meetingpad Pro is $8/month for unlimited identities.

Setting it up in Meetingpad (5 minutes)

Download Meetingpad for Mac.
Menubar → Connect Google account → sign in to your first Google account → grant calendar + Gmail send permissions.
Repeat for each additional Google account you want to send invites from.
Create event types on each identity — 30-min intro, 60-min working session, etc. Each identity's event types get their own booking link.
Copy the correct booking link for each identity and share with the appropriate counterpart.

When a guest books on your Client A identity's 30-min link, the invite arrives from your Client A Gmail. Book on Client B's link, the invite comes from Client B's Gmail. Done.

Try it

Download Meetingpad for Mac See pricing