Adding a new attribute to the EntraID Spoke Lookup User Stream action
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
I have a need to add a new attribute from Entra ID into the output from the Lookup User Stream action. I am finding it difficult to find documentation on how to add this to the output. I copied the action and edited the pre-processing script to add my attribute. I get the data in the raw json response in the test for the action, but how exactly do I map this to the output for the action? The output is set to "create structure manually" and there are no fields here. I am unfamiliar with this and I am finding it difficult to find documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
This is the general Flow Designer custom-action output pattern, confirmed across multiple independent action-building walkthroughs worth flagging that I'm answering from the general REST/action-output mechanism, since I couldn't find EntraID-spoke-specific documentation on this exact action:
- On your copied action, go to the Outputs tab and manually add a new output variable (e.g., custom_attribute) with the right type (String, etc.) "create structure manually" means the platform won't auto-populate these from the response, you define them yourself.
- Go to the final step of the action (often a "Script" or "Set Output" step) and use the data pill picker to map your new attribute from the raw JSON response you'll dot-walk into the parsed response body (e.g., the pre-processing script's parsed output) to the specific field you added, and assign it into your new output variable.
- Save and re-test the new field should now appear as a usable data pill anywhere this action is referenced in a flow.
If your pre processing script alredy puts the attribute into a variable, the missing piece is almost always step 2 the output variable exists, but nothing is assigned to it yet, so it shows empty even though your test shows the raw JSON contains the value.