Autom Mate Team · Practical example
Natural language is useful for describing what you want. The selected Hyperflow’s input contract tells the assistant what it can actually send.
- Find the existing Hyperflow and ask the assistant to inspect its inputs without running it.
- Ask for a short list of input names, expected types and descriptions. Use the contract returned from your workspace.
- Supply any missing values and ask the assistant to repeat the proposed request in plain language.
- Resolve unclear values before execution. An array of users, for example, should remain an array rather than become a single text string.
- Once the intended flow, target and values are clear, explicitly authorize one execution and inspect its result.
Try this prompt: “Inspect the inputs for our test access-request Hyperflow. Tell me what information you still need. Do not execute it yet.”
A successfully returned empty input contract means no declared inputs. A missing contract with an explanatory note means the requirements are unknown; the assistant should not guess. Masked values should not be inferred or pasted into chat.
This pattern uses an existing API/webhook Hyperflow in Dublin 6.0.
Which input is hardest for your users to provide correctly: account, application, request type or something else?