New Outlook Email
Emit an event when Microsoft Graph reports outlook.message.created.
Workflow template
Create a separate OneDrive folder and a UTF-8 Email reference.txt file when a new email arrives in the connected Outlook inbox. The file records the full subject, received time, message ID and a link to open the original email. Folder names use the received time in UTC; OneDrive renames a folder if that name already exists, so simultaneous messages do not overwrite each other. Connect Microsoft 365 and Microsoft OneDrive, then optionally select a parent folder in the first Action; otherwise folders are created at the OneDrive root. Email bodies, previews, sender and recipient addresses, attachments and conversation history are not copied. People with access to the destination can read the subject and metadata; opening the original email still requires mailbox access. No public sharing is added. This creates reference files, not a full mailbox backup. Activate and wait for the Outlook subscription to be ready before sending a fictional test email. Older mail is not imported; later edits, moves and deletions are not synchronized. The workflow does not reply, forward, mark or delete mail. Replayed events or reruns create additional folders. If file creation fails, its folder may remain empty. Test in a folder you control.
How it works
Emit an event when Microsoft Graph reports outlook.message.created.
Create a folder under the root or another folder.
Create or replace a small text file in OneDrive.
Before activation
Open the template in FastHook to create an editable Workflow Draft.
Connect your accounts for Microsoft 365, Microsoft OneDrive.
Review the Steps, field mappings, routes, and provider settings.
Activate the Workflow when the Draft is ready, then verify a test run.
No. FastHook creates a disconnected Draft. Connect your own Microsoft 365, Microsoft OneDrive accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.