Short answer: Drop the "Microsoft Outlook → List Outlook Messages" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Folder folder | options | Optional | Folder. Options: Inbox, Sent Items, Drafts, Deleted Items |
Filter (OData) filter | string | Optional | OData filter expression |
Limit top | string | Optional | Limit. e.g. "10" |
Search search | string | Optional | Search. Example: subject:quarterly report |
{"folder": "{{trigger.folder}}","filter": "e.g. isRead eq false","top": "10","search": "e.g. subject:quarterly report"}
{"value": [{"id": "msg123","from": {"emailAddress": {"address": "sender@example.com"}},"isRead": false,"subject": "Quarterly Report","bodyPreview": "Please find attached...","receivedDateTime": "2025-01-15T12:00:00Z"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.