Skip to main content

Flows from the field: Watson; Child flows; Experimental features; Listing users

by Eamon McCarthy Earls
Assistant Editor,
April 18 2020

Professionals put Microsoft Power Automate to work with IBM Watson, managing child flows, discovering experimental features, and pulling lists of active users out of Dynamics 365.

Want to see your flow featured in a future edition of this series? Contact me with your example.

Leveraging IBM Watson

According to Microsoft MVP Joe Gill the beauty of low code platforms is integrating with other platforms easily, without a need for substantial technical skill. In a recent experiment, he opted to call a Power Automate flow from Watson instead of from a Power Virtual Agents bot (in a previous blog post, he used PVA).

In the Watson designer, Gill used key phrases to generate an intent to trigger the action—in this case, #orderquery. From there, he inputted the details of the flow HTTP endpoint into the dropdown of webhook options. The flow accepts values from JSON messages, returning order details in JSON format from the CDS order entity. Additionally, he added a node to the handle the intent, customized it with slots and webhooks, and explained how to tie it all together.

Comparing child flows and child workflows

FREE Membership Required to View Full Content:

Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

About Eamon McCarthy Earls

As the assistant editor at and, Eamon helps to oversee editorial content on the site and supports site management and strategy. He can be reached at

Before joining, Eamon was editor for at TechTarget, where he covered networking technology, IoT, and cybersecurity. He is also the author of multiple books and previously contributed to publications such as the Boston Globe, Milford Daily News, and DefenceWeb.