ActionMicrosoft OutlookUpdated September 2026

How do I fetch an Outlook email?

Short answer: You can get outlook message in Microsoft Outlook by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Microsoft Outlook Get Outlook Message action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Outlook Message in Microsoft Outlook — start free All 8 Microsoft Outlook actions

Get Outlook Message in Microsoft Outlook — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Message ID messageId	string	Required	Message ID

Sample request

{
  "messageId": "{{trigger.messageId}}"
}

Returns

{
  "id": "msg123",
  "from": {
    "emailAddress": {
      "name": "John",
      "address": "john@example.com"
    }
  },
  "subject": "Hello",
  "bodyPreview": "Hello...",
  "receivedDateTime": "2026-04-11T10:00:00Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Outlook Message.

Any of these apps can fire this action as part of a workflow.

Gmail → Microsoft Outlook

1 Gmail triggers

Slack → Microsoft Outlook

13 Slack triggers

Google Sheets → Microsoft Outlook

2 Google Sheets triggers

HubSpot → Microsoft Outlook

18 HubSpot triggers

FAQ

Questions about Get Outlook Message.

What does the Get Outlook Message action do in Microsoft Outlook?

Returns a specific email with full body, attachments, headers. The standard lookup for "fetch this email captured upstream and process" workflows.

What inputs does Get Outlook Message require?

Required: Message ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Microsoft Outlook returns an error?

The run history shows the failed step with its input and the error message Microsoft Outlook returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Outlook Message support batch operations?

Run Get Outlook Message inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Microsoft Outlook's rate limits.

More actions