New Outlook Email
Receive new inbox-message events after the Microsoft Graph subscription connects. The recipe does not import older mail or synchronize later moves, edits or deletions.
Workflow template
Save new Outlook inbox messages as UTF-8 text references in Google Drive. Each file keeps the subject, received time, message ID and original-email link without copying bodies, previews, addresses or attachments.
How it works
Receive new inbox-message events after the Microsoft Graph subscription connects. The recipe does not import older mail or synchronize later moves, edits or deletions.
Create a text/plain UTF-8 file containing subject, receivedDateTime, message ID and webLink. The filename uses the trimmed subject or Untitled email; choose a parent folder or leave it empty for My Drive.
The result
Outlook — Köln review — Grüße 🚀.txt
Outlook email reference Subject: Köln review — Grüße 🚀 Received: 2026-11-15T12:00:00Z Message ID: AAMkFictionalOutlookDrive0001 Open in Outlook: https://outlook.office.com/mail/deeplink/read/AAMkFictionalOutlookDrive0001 Email body, preview, addresses and attachments remain in Outlook.
Fictional source email metadata and mapped text, not an exported mailbox or Google Docs document. The original email link still requires mailbox access. No public sharing is added.
Before activation
Connect Microsoft 365 for new inbox-message events. This recipe saves references to messages received after activation rather than importing existing mail.
Connect Google Drive and optionally select a Parent folder. Empty means My Drive. Files inherit folder access, so review who can see subjects and message metadata before activation.
Activate and wait for the subscription to connect, then send a fictional email. Compare the text filename, subject, received time, message ID and Outlook link in the saved file.
The filename has a subject fallback. A missing, non-text or blank subject becomes Untitled email in the filename. The text reference retains the mapped subject and metadata; a filename is not a unique message identifier.
This is a reference, not an email backup. Bodies, previews, sender/recipient addresses, attachments and conversation history are not copied. The workflow does not reply, forward, mark or delete mail, and creates plain text rather than a Google Docs document.
Drive access and mailbox access stay separate. Files inherit the destination folder’s access without adding public sharing. Recipients of the file still need mailbox access for the Outlook link. Provider redelivery or reruns may create duplicate files, including identical names.
No. It creates a UTF-8 text/plain file with subject, received time, message ID and an Outlook link. Bodies, previews, addresses, attachments and conversation history stay in Outlook.
It is saved in My Drive. Selecting a folder places it there with inherited access; the recipe does not create public sharing permissions.
The filename uses Untitled email when the subject is absent, non-text or blank. Otherwise it uses the trimmed subject. The message ID inside the file identifies the source email even when filenames repeat.
No. Only new inbox-message events after activation are processed. Later edits, moves and deletions are not synchronized, and redelivery or reruns can create another reference file.
Keep a dated text-file index of receipt emails for bookkeeping.
View template →