Send notification / Send email

What it does

This action communicates with people or looks up Microsoft 365 user data. Migration review should focus on recipients, dynamic identities, message content, and connector permissions.

How Flow Migrator maps it

Flow Migrator maps this to Send an email using Microsoft Exchange Online / Outlook. Preserves supported Exchange literal/value wrappers, direct recipient references, To/Cc/Bcc/ReplyTo, subject, body and importance. Claims/group identities require exact reviewed mailbox mappings; unknown collection item types require an explicit email-string contract and runtime validation. Unmapped message fields remain blocking. Validate attachments, sender permissions and delivery after import. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Validate expression syntax, data types, escaping, HTML output, and array/object handling in Power Automate.
• Confirm recipients, sender behavior, HTML body rendering, attachments, and tenant connector permissions.
• Run a test instance and compare outputs against the original Nintex workflow before production migration.

Validation checklist

1. Open the generated flow and confirm the action card imported correctly.
2. Validate connection references and required settings before running the flow.
3. Test with representative source data from the original workflow.