Can Now Assist Flow Generation configure Group Approval actions directly from the prompt?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2026 10:18 PM
Hi Community,
I am testing Now Assist Flow Generation in Workflow Studio to create Flow Designer flows from natural language prompts.
One of my prompts contains instructions similar to the following:
Trigger when a record is created on the sc_request table.
Evaluate the request price.
If the price is greater than $1,000, add a Group Approval action.
Use a specific approval group (group sys_id provided in the prompt).
If approved, mark the request as approved.
If rejected, mark the request as rejected.
The flow structure is generated successfully, including the decision logic and approval step. However, the Group Approval action is not fully configured, and I still need to manually select/configure the approval group after generation.
My questions are:
Does Now Assist Flow Generation currently support configuring a Group Approval action directly from the prompt?
Can it reliably resolve and use a provided group sys_id when generating the flow?
Are there any recommended prompt patterns or best practices for populating approval groups automatically?
Is this a known limitation of the current capability, requiring manual configuration after generation?
Has anyone successfully generated a flow where the approval group was fully configured without post-generation edits?
Thanks in advance for any guidance.
- Labels:
-
Flow Designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi Prabhu, what you are seeing is the expected current behavior, not a prompt mistake on your part. Now Assist Flow Generation builds the flow structure from the prompt, but it does not reliably resolve a reference field like the Group Approval group from a sys_id in the prompt. A sys_id is not a name the model can look up and validate in the same way, so the generated action is left for you to finish. Do not rely on a sys_id in the prompt. Name the group in plain language, for example: Add a Group Approval action for the approval group named X, and then open the generated action in Workflow Studio and select that group, and check the approval outcome branches. If you need the group to be set deterministically every time, set it after generation with a data pill or a flow variable, or use a subflow where the approval group is an input you set once, rather than expecting the prompt to populate it. In short, treat Flow Generation as a draft of the structure, and always verify the approval group, the trigger table, and the decision condition before publishing. Regards, Karimuddin