Opus Assistant
The Opus Assistant is your AI-powered builder and guide inside the OPUS editor. Describe what you want in plain language and it can generate a workflow or decision for you, explain what your graph does, and help you troubleshoot when something isn’t working.
Data classification: The Opus Assistant may only be used with information classified up to a maximum of RESTRICTED / SENSITIVE-NORMAL. AI-generated responses may be inaccurate — always review the graph and results the assistant produces before relying on them.
Where to Find It
The Opus Assistant is available inside the workflow editor and decision editor. When you have a graph open, click the Assistant button (bottom-right of the editor) to open the assistant panel alongside the canvas.
Prerequisites
The assistant runs on Platform AI using your own API key:
- The first time you open the assistant without a key configured, a Set up your AI Assistant prompt appears.
- Add your Platform AI API key under My Credentials (
Dashboard → Credentials). - Once your key is saved, open the assistant and start chatting.
Bedrock model access required: The Opus Assistant is powered by Bedrock–hosted Claude models on Platform AI. Your Platform AI API key must have access to all Bedrock models for the assistant to work.
You also need read access to the project you are working in. Assistant sessions are audited.
What It Can Do
The assistant understands the graph you currently have open and can act on it directly.
Build a Graph from a Description
Describe the automation you want (for example, “When a form is submitted, summarise the description and create a case in Ownself Gather”) and the assistant will:
- Generate the workflow or decision graph, adding and connecting the required nodes.
- Configure each node, using placeholder mock data for external integrations where needed.
- Run a simulation to check the graph works end-to-end.
Changes are applied live on the canvas as the assistant works, so you can watch the graph take shape.
Modify an Existing Graph
Ask the assistant to change the graph you have open — for example, add or remove a node, rewire connections, or update a node’s configuration.
Explain Your Graph
Ask the assistant to describe what the current graph does. It inspects your nodes (including logic in Function, Expression, Switch, and Decision nodes) and explains them, citing the actual configured values. The panel includes a quick “Explain this workflow” prompt to get started.
Troubleshoot and Simulate
The assistant can run simulations, generate mock responses for external nodes, and surface per-node execution traces to help you find and fix problems. It can also help you wire project environment variables (secrets) into sensitive fields — it only ever sees the names of your environment keys, never their values.
Decision Test Suites
When you are working on a decision, the assistant can additionally help create, update, and run decision test suites.
General Product Help
You can also ask the assistant how-to questions about using OPUS. It answers questions about the Management System and points you to relevant documentation. It will politely decline questions unrelated to OPUS.
How to Use It
- Open a workflow or decision in the editor.
- Click the Assistant button to open the panel.
- Type your request in the message box (for example, “Build a workflow that…” or “Explain this decision”) and press Enter to send. Use Shift + Enter for a new line.
- Review the assistant’s response and the changes it makes on the canvas. The assistant asks for confirmation before actions that need your permission.
- Use New chat (the + in the panel header) to start a fresh conversation. Note that starting a new chat clears the current conversation history and cannot be undone.
Sessions: A session belongs to the entity you have open. Switching to a different workflow or decision ends the current session and clears its history. Sessions also end automatically after a period of inactivity.
Good to Know
- Review everything. The assistant is a productivity aid, not a replacement for your judgement. Check generated graphs, node configurations, and simulation results before publishing.
- Very large or complex requests may hit a per-turn limit. If the assistant reports it reached its limit or that a response was too large, simplify or break the request into smaller steps.
- Decisions support a focused set of node types (such as Input, Output, Annotation, Function, Expression, Switch, Decision, and Decision Table); integration, trigger, and AI nodes are workflow-only, so the assistant will not add those to a decision.
