Answered

Power Automate "Text can't start with @" error on flow save in "Send Email V2" action

(0) Share

Report

Posted on by Alessio E

When I set up a "Send Email V2" action from Office365 OUtlook, using data from previous steps to set an email address in the "To" field, I get the "Text can't start with @" error on flow save. The flow tests successfully and works correctly; no visible error is shown. The error only appears when trying to save, and it does not allow me to save the flow. See this screenshot:
User's image

This is the code view:

For some reason, Power Automate does not like that @, but only when trying to save the flow. Otherwise, it works and tests with no errors.
What can I do to unlock this situation?

Categories:

Building flows

Using flows

General topics

I have the same question (0)

All responses (5)

Answers (1)

Sort by

Suggested answer

Fredrik_A 3,642 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hey,

try putting a compose step before the email step with the email. Then use the compose step in the "To" field and see if that solves it for you.

If my response solved your issue, please mark it as ✅ Accepted Answer and give it a like.

Was this reply helpful? Yes No
Alessio E 11 on at

Like (0)

Report
Copy link

Link copied!

Hi @Fredrik_A, thank you for your reply, Unfortunately, the same error persists.

Is this what you meant?

Here's the code view:

I think this is what triggers it, and I think it's a bug either in the "Send email V2" action or in the code checker of Power Flow, since the flow works and tests just fine, only saving triggers it:

Was this reply helpful? Yes No
Verified answer

Alessio E 11 on at

Like (0)

Report
Copy link

Link copied!

Huh... not sure what happened, but I had to restart the browser; Power Automate recovered the version I was working on when I made my original post, but this time it saved correctly.

Weird, I guess it was a temporary thing. Not sure why it happened, not sure why it disappeared. But now it's solved.

Was this reply helpful? Yes No
Suggested answer

TechFreak 58 on at

Like (0)

Report
Copy link

Link copied!
Hi,

The issue you’re encountering is due to how Power Automate validates expressions inside connector inputs, specifically in the “Send an email (V2)” action from Microsoft.

Recommended Fixes

Option 1: Use Expression Builder (Best Practice)

Click inside the To field

Go to the Expression tab

Paste:

outputs('Get_user_profile_(V2)')?['body/mail']

Save

This ensures Power Automate correctly recognizes it as an expression instead of raw text.

Option 2: Use Dynamic Content

Instead of writing the expression manually:

Select the Mail property from Get user profile (V2) dynamic content

This avoids validation issues entirely.

Option 3: Wrap with concat() (Workaround)

If the issue persists:

concat(outputs('Get_user_profile_(V2)')?['body/mail'])

This forces the designer to treat it as a valid expression.

Hope this helps!

Was this reply helpful? Yes No
Kalathiya 1,862 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hello @Alessio E,

Try to write in expression and try and use in email action, like this,

concat('',outputs('Get_user_profile_(V2)')?['body/mail'])

If this response resolves your issue, please mark it as the Verified Answer so it can help other community members as well.

---------------------------------------------------------------------------------

📩 Need more help? Just mention @Kalathiya and I’ll be happy to assist.

✔️ If this answer helped you, please tick “Does this answer your question?” so it can be marked as the Verified Answer.

💛 A Like always motivates me to keep contributing!

Was this reply helpful? Yes No