Nintex Automation Cloud - Get user in tenant

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 HTTP/API handoff scope using HTTP / Custom connector. Calls the NAC tenant user endpoint with the detected user ID and shapes the result into the original Nintex user output object. Replace placeholder authentication and validate tenant region and user identifier mapping before production activation. Flow Migrator has a direct or proven best-effort conversion path for this mapping.

Common migration issues

• Review HTTP method, URI, headers, authentication, retry behavior, premium licensing, and response parsing.
• 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.