Hi everyone,
I'm working on a use case in Salesforce Marketing Cloud Engagement and I'm stuck on a specific requirement. Hoping someone has tackled this before.
The scenario:
A subscriber registers for an event (webinar, meeting, etc.) through a Cloud Page and opts in to receive communications. After registration, the client wants to send them a calendar invitation — not a regular marketing email with an .ics file attached or linked, but an actual calendar invite, like the kind you receive when someone schedules a meeting with you in Outlook or Google Calendar.
The key distinction:
The goal is that when the subscriber receives the email, it should show up as a proper calendar invitation with Accept / Decline / Maybe options, and the event should appear in their calendar in a "tentative" state (grayed out) even before they respond — just like a standard meeting invite from Outlook or Google Meet.
What we've tried / the problem:
We can generate an .ics file and include its URL in a button or link inside the email, but clicking that link downloads the file instead of opening it as an invitation directly in the calendar. That's not the experience the client wants.
The question:
Is there a way to send a real calendar invitation from SFMC — either through a specific email format, an SMTP header configuration, or any other mechanism — so that the email client recognizes it as an invite and renders the Accept/Decline UI natively?
Any pointers to documentation, workarounds, or third-party integrations that could help would be hugely appreciated. Thanks in advance!
Short answer: not with a standard SFMC email send, as far as I know. A real invite (Accept / Decline / Maybe, tentative entry in the calendar) needs the email itself to carry a text/calendar MIME part with METHOD:REQUEST, usually inside multipart/alternative. Marketing Cloud builds the MIME structure for you and doesn't let you add a custom part or content type through AMPscript or the template, so Outlook and Gmail see an ordinary marketing email with a link or attachment.
What we've seen work:
1. Send the invite from a mail service that lets you build the MIME yourself (Microsoft Graph, Gmail API, SendGrid or similar), triggered from the Cloud Page form post or from a Journey custom activity / webhook. SFMC keeps the registration, consent and the follow-up journey; the invite is the one message that goes out through the other channel. Make sure the organizer address can actually receive the replies.
2. If the event runs on a webinar platform (Zoom, Teams webinars, ON24 and so on), let that platform send its own calendar invite on registration and pass the registrant to it via API. Those platforms already send proper invites and handle reschedules and cancellations, which a one-off .ics never does.
3. If it has to stay inside SFMC, the best you can do is "Add to Google / Outlook / Apple" buttons with prefilled calendar links. Not a native invite, but one click and no file download.
One thing to check with the client: a true invite means updates and cancellations also have to be sent as calendar messages (METHOD:CANCEL with the same UID), so whoever sends the first one should own the whole lifecycle.
