Power Automate provides tools to automate workflows triggered by new emails. One crucial detail often required is the exact moment a message enters the inbox. This timestamp can be captured and utilized in subsequent steps of the automation.

To retrieve this information:

  • Use the "When a new email arrives (V3)" trigger from Outlook.
  • Access the dynamic content labeled "Received time" within the flow editor.
  • Store or transform this value using further actions like "Compose" or "Initialize variable".

Note: The time captured reflects the server-side reception timestamp, not when the email was read.

A structured approach helps ensure this timestamp is correctly captured and formatted:

  1. Create a flow with the email trigger.
  2. Add a "Compose" action and insert the received time token.
  3. Format the value using the formatDateTime() function if needed.

Action Description
Trigger Detects incoming messages
Compose Displays or modifies the timestamp
Store Saves the time to SharePoint, Excel, or another service

How to Retrieve the Time an Email Arrived in Power Automate

To capture the exact timestamp when a message lands in an Outlook inbox using Power Automate, start by configuring the flow with the trigger “When a new email arrives (V3)”. This trigger provides access to a wide range of metadata, including the delivery timestamp under the field named Received Time.

Once the email is detected, the flow can extract and manipulate this timestamp using built-in expressions or by directly referencing it in later steps. This enables automation based on arrival time, such as filtering by business hours or logging communication activity.

Step-by-step process

  1. Create a new flow using the Outlook trigger “When a new email arrives (V3)”.
  2. In the dynamic content panel, locate and select the field labeled DateTimeReceived.
  3. Use the formatDateTime() expression to format the timestamp as needed:
    • formatDateTime(triggerOutputs()?['headers']['x-ms-received'], 'yyyy-MM-dd HH:mm')
  4. Store or use the formatted time in subsequent steps like adding rows to Excel or posting to Teams.

Note: The received timestamp reflects the exact time the message was processed by the Outlook server, not when the user opened or read the message.

Field Description
DateTimeReceived The raw timestamp of when the email was received
formatDateTime() Expression to convert the timestamp into readable format

Extracting Timestamp from Email Trigger Metadata in Power Automate

When building automated workflows that react to incoming emails, it's crucial to capture the exact time an email arrives. This information is embedded within the system data of the trigger action and can be accessed using specific expressions. The timestamp can be used for logging, filtering messages, or triggering time-sensitive processes.

The trigger’s internal structure includes metadata fields such as the precise delivery time of the email. These values are not always directly visible in dynamic content but can be retrieved using expressions referencing the trigger output.

Steps to Retrieve Email Arrival Time

  • Start with a flow using the "When a new email arrives" connector (Outlook or Office 365).
  • Insert a Compose action to extract and display the internal timestamp.
  • Use the expression: triggerOutputs()?['headers']['x-ms-exchange-organization-originalarrivaltime']

This expression pulls the original server-side delivery time, which can differ from client-side timestamps.

  1. Test the flow by sending an email to the configured inbox.
  2. Check the flow run history and confirm the correct datetime is captured.
  3. Use this value in logging, delay calculations, or condition checks.
Field Description
x-ms-exchange-organization-originalarrivaltime UTC-based timestamp of when the email was received by Exchange
ReceivedTime Client-side interpreted receive time (less reliable for automation)

Adjusting Message Timestamps to Local Time in Power Automate

When working with automated email workflows in Power Automate, received timestamps are often returned in Coordinated Universal Time (UTC). This can cause confusion for end users expecting local time, especially when emails are part of task scheduling or approval chains.

To ensure clarity and consistency, it's essential to convert the UTC-based timestamp of incoming emails into the appropriate local timezone. This transformation allows downstream processes and users to interpret timing data accurately.

Steps to Convert UTC Time to a Specific Timezone

  1. Use the Convert time zone action in your flow.
  2. Set the base time as the received time of the email (e.g., triggerOutputs()?['headers']['x-ms-received'] or receivedTime field).
  3. Specify the source timezone as UTC.
  4. Select the target timezone (e.g., Eastern Standard Time or Central European Standard Time).

Use official Microsoft timezone identifiers to avoid mismatches. For example, use Pacific Standard Time instead of manually offsetting with hours.

Below is a reference table with sample conversions using the Convert time zone action:

Original (UTC) Target Timezone Converted Time
2025-04-21T14:00:00Z Central Europe Standard Time 2025-04-21 16:00
2025-04-21T08:30:00Z Pacific Standard Time 2025-04-21 01:30
  • Check daylight saving adjustments automatically applied by Power Automate.
  • Use dynamic timezone selection if flows serve users in multiple regions.

Capturing and Logging Email Arrival Timestamps in SharePoint or Excel

When automating email processing workflows, it's often critical to track the exact moment each message arrives. This information can be preserved by extracting the email's timestamp and saving it into structured storage like SharePoint lists or Excel spreadsheets. Doing so enhances audit trails, enables time-based analytics, and supports SLA monitoring.

Microsoft Power Automate enables this by retrieving the system-generated time metadata when an email is received. This value can then be parsed and added as a new item in a SharePoint list or a new row in an Excel table, depending on the storage system used.

Implementation Overview

Important: Ensure your Excel file is stored in OneDrive or SharePoint and formatted as a table to allow data insertion via Power Automate.

  • SharePoint: Create a custom list with a Date and Time column (e.g., "Email Received At").
  • Excel: Insert a column in your table specifically for storing timestamps, labeled appropriately (e.g., "Received On").
  1. Use the "When a new email arrives" trigger in Power Automate.
  2. Retrieve the internal property ReceivedTime using dynamic content.
  3. Pass this value into the "Create item" or "Add a row" action depending on your data target.
Field Target (SharePoint / Excel) Description
Email Subject Text The title or summary of the email
Received On DateTime The exact time the email was received
Sender Text Email address of the sender

Formatting Timestamps for Email Tracking in Power Automate

When capturing incoming mail metadata in Power Automate, precise formatting of the timestamp is essential for reliable notification tracking and log consistency. Instead of using the default UTC string, it’s often necessary to convert and format the time to match local business hours or user expectations.

Using the Convert time zone action helps align email timestamps with organizational time zones, which can then be formatted using the formatDateTime() expression. This approach ensures clarity in both logs and user-facing alerts.

Recommended Formatting Steps

  • Insert the Convert time zone action to adjust UTC to your local time.
  • Use formatDateTime(triggerOutputs()?['headers']['x-ms-received']), 'yyyy-MM-dd HH:mm') to structure the output.
  • Include the formatted time in subject lines or log entries.

Formatting timestamps enhances readability and prevents confusion caused by default time formats or mismatched time zones.

  1. Retrieve the original received header timestamp.
  2. Convert it to the correct time zone using "Convert time zone".
  3. Format the timestamp using formatDateTime().
Purpose Format Example Expression
Log timestamp 2025-04-21 14:33 formatDateTime(… , 'yyyy-MM-dd HH:mm')
Email subject time Mon 14:33 formatDateTime(… , 'ddd HH:mm')

Filtering Emails by Time of Arrival in Automated Workflows

When designing automated workflows in Microsoft Power Automate, it is often essential to narrow down incoming messages to those received within a specific time frame. This enables users to target only recent or time-critical emails, optimizing both performance and relevance of the automation.

Email arrival timestamps can be used as conditions in trigger filters or within conditional branches. By comparing the email’s internal timestamp against dynamic or fixed values, workflows can selectively process only the most relevant messages.

Techniques for Applying Time-Based Email Filters

  • Use the receivedDateTime property from the Outlook connector's email trigger.
  • Convert the timestamp to a specific format using the formatDateTime() expression if needed.
  • Compare it with the current time using expressions like addHours(utcNow(), -1) to target recent emails.
  1. Create a flow with a trigger: "When a new email arrives (V3)".
  2. Add a condition: receivedDateTime is greater than addHours(utcNow(), -2).
  3. If true, continue with processing; otherwise, terminate or skip.
Expression Description
utcNow() Returns the current timestamp in UTC.
addHours(utcNow(), -1) Gets the timestamp one hour before now.
formatDateTime(triggerOutputs()?['headers']['x-ms-exchange-organization-receivedtime'], 'yyyy-MM-ddTHH:mm:ss') Formats the received time for comparison.

Use expressions with caution: date and time comparisons are case-sensitive and require exact formatting to avoid errors in flow execution.

Comparing the Time of Email Reception with the Current Time for Conditional Logic

When automating workflows with Power Automate, comparing the time an email is received with the current system time is a common task. This comparison is crucial for setting conditions based on how recent an email is or determining whether certain actions should be taken depending on the time difference. In this scenario, the system time refers to the exact moment when a specific action or event occurs, while the received email time is when the email message was initially delivered to the inbox.

Utilizing these two time points enables the creation of intelligent and responsive workflows. By performing time-based comparisons, users can manage email-based tasks, such as responding to messages within a set time frame or flagging old emails. Power Automate allows you to define conditions that evaluate whether an email's reception time falls within a defined window, such as within the last 24 hours.

Steps to Compare Received Time with Current Time

  • Extract the time the email was received from the email metadata.
  • Retrieve the current system time using the "Current time" action in Power Automate.
  • Perform a comparison between the two time values using conditional logic.
  • Set up the workflow to trigger specific actions based on the result of the comparison.

Example of Time Comparison Logic

  1. If the difference between the received time and the current time is less than a specified duration (e.g., 24 hours), proceed with the action.
  2. If the email was received more than 24 hours ago, trigger a different action or alert.

It's essential to account for different time zones when performing time comparisons to avoid inaccuracies in global workflows.

Example Table of Time Conditions

Condition Action
Received within the last 24 hours Send automatic response
Received more than 24 hours ago Flag for manual review

Common Errors When Handling Email Timestamps and How to Fix Them

When working with email timestamps in Power Automate, there are several common mistakes that users often encounter. These errors can cause confusion, delays, and inaccurate automation workflows. It's important to understand these pitfalls and how to address them in order to ensure that email processing is done accurately and efficiently.

One of the most frequent issues is incorrect time zone handling. When emails are received from different time zones, it can lead to discrepancies in the timestamp. This can be especially problematic when scheduling or triggering actions based on the time of arrival. Another issue is misunderstanding the email's received time format, leading to parsing errors and incomplete data processing.

Common Issues and Solutions

  • Time Zone Misalignment: Emails may come from different time zones, causing discrepancies in timestamp data.
  • Incorrect Date Formatting: Some email services use non-standard formats, making it difficult to extract accurate timestamps.
  • Parsing Errors: The automation workflow might fail to correctly parse the timestamp if it's not standardized across the system.

How to Fix These Issues

  1. Adjust Time Zone: Ensure that all email timestamps are converted to a single, consistent time zone (e.g., UTC) before processing.
  2. Normalize Date Formats: Use Power Automate's built-in functions to parse and convert email timestamps to the correct format.
  3. Use Error Handling: Set up conditions to handle parsing failures and ensure the workflow proceeds correctly even if an error occurs.

Example of Timestamp Parsing Error

Email Subject Received Time Expected Format
Test Email 1 2025-04-21 14:00 MM/DD/YYYY HH:mm
Test Email 2 21-Apr-2025 14:00 MM/DD/YYYY HH:mm

Important: Always ensure that the timestamp format used in your email system is consistent and matches the expected format in Power Automate.