Others

How to Map Outlook Sender Names to Contact Fields in Power Automate

Maira Mehtab Sep 27, 2026 871 views

Question details

The user needs to separate a sender's full name into distinct Given Name and Surname fields when automatically creating Outlook contacts using Power Automate.

Product: Power Automate, Microsoft Outlook
Device & OS: not provided
Scenario: Creating automated workflows to extract sender information from emails and populate contact fields accurately.
Observed behavior: The automation flow combines the sender's first and last names into a single field instead of parsing them into separate Given Name and Surname fields.

Before you start

Ensure you have an active Microsoft Power Automate license and the necessary permissions to access and create Outlook contacts before modifying your workflow.

Solution 1Recommended

Use Split Expressions in Power Automate

Utilize Power Automate's built-in string functions to split the display name and extract the first and last names dynamically.

When Power Automate extracts a sender's name from an Outlook email, it usually retrieves a single string containing the full display name. By applying Data Operation expressions, you can divide this string based on spaces to assign values to specific Given Name and Surname fields.

Locate the Sender Data extraction step

Open your flow in Power Automate in Edit mode and locate the step where you extract the Outlook sender's display name or email address.

Apply the split() expression

Add an expression using the split() function to divide the display name into an array of strings based on the space character. For example: split(triggerOutputs()?['body/from'], ' ')

Map the Given Name field

Use the first() expression in the 'Given Name' mapping field to extract the first element of the split array. Example: first(split(triggerOutputs()?['body/from'], ' '))

Map the Surname field

Use the last() expression in the 'Surname' mapping field to extract the final element of the array. Example: last(split(triggerOutputs()?['body/from'], ' '))

Test the automation flow

Save your workflow and run a manual test. Review the newly created Outlook contact to ensure the first and last names populate the correct individual fields.

Handling Name Variations: Be aware that complex names (e.g., those with middle names or multiple surnames) might require more advanced parsing logic than simple first() and last() expressions. Account for single names by adding a condition to check the array length.

Free Microsoft Office alternative

Streamline Your Document Workflows with WPS Office

While Power Automate handles complex data mapping for Microsoft services, you might be looking for a lighter, cost-effective office suite for your daily document creation needs. WPS Office provides a robust, seamless alternative to Microsoft Office, helping you manage your files efficiently.

1. Download the software: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
3. Start working seamlessly: Open WPS Office and immediately begin opening, editing, and saving your Microsoft Office compatible documents.

Fully compatible with Microsoft Office formats, including Word, Excel, and PowerPoint files.Lightweight design that runs smoothly on almost all operating systems without heavy resource usage.Built-in PDF editing tools seamlessly combined with classic document management workflows.Free to download and use with a highly familiar user interface for an effortless transition.

microsoft office alternative - wps office

Frequently Asked Questions

Why is my Power Automate flow combining the first and last name?

By default, Outlook provides the sender's name as a single 'Display Name' string. Unless you explicitly split this string using Power Automate expressions, the flow will pass the entire string into whichever individual field you map it to.

What happens in my flow if a sender only has one name?

If you use the split() function on a single name without a space, both the first() and last() expressions will return the exact same value, populating both the Given Name and Surname identically. You should add a condition to check the length of the split array to handle this scenario.

Where can I get more help with advanced Power Automate expressions?

For complex automation logic, nested expressions, and custom script debugging, it is highly recommended to post your workflow details in the official Microsoft Power Platform Community forums where experts can provide tailored solutions.

Office Quick Solutions