Before
An operator or agent would need to review the request, search the available workflow list, decide which workflow matched, and manually initiate it. For requests requiring multiple actions, each workflow would also need to be identified and launched separately.
How it works
- Receive the action request and the configured catalog of available workflows.
- Analyze the request, select the relevant workflows, and generate instructions for each match.
- Trigger every selected workflow with its corresponding instructions, or take no action when no suitable workflow exists.
Workflow details
- Request intake: The workflow receives a request describing an action and combines it with a configured list of available workflows, such as locking a device or warning a user about a phishing attack.
- Intelligent selection: An AI agent analyzes the request against the available workflow names and descriptions, determines which workflows are relevant, and returns the matching workflow destinations with instructions tailored to the request. If no workflow is suitable, it returns an empty selection.
- Workflow execution: The automation processes every selected match and sends a request to the corresponding workflow destination, passing along the instructions generated from the original request.
- Operational result: Relevant workflows are launched automatically from a single request, while unsupported requests stop without triggering an unrelated workflow.
What changed
Workflow selection and execution now happen from the same request. The AI agent performs the matching decision, and every selected workflow receives its instructions automatically without a separate manual routing handoff.
Work removed
Reviewing requests one by one, searching the workflow catalog, deciding which workflow applies, copying or composing execution instructions, and manually launching each selected workflow.
Expected outcome
The process can remove at least two recurring manual actions per request—workflow identification and workflow launch—while ensuring that unsupported requests do not trigger an unrelated workflow.
