Docs · Concepts
Ask Mosaic
Help that opens beside the page, explains a workflow run that failed and drafts a workflow from a sentence, with what it sends to a model and what it never does.
Ask Mosaic is help that opens beside whatever you are looking at. It does three things:
- explains a workflow run that failed, and says what to change
- answers a question about how Mosaic works, from this manual
- drafts a workflow from a sentence, for you to read and then create
It reads and it drafts. It never changes anything by itself.
#Opening it
| From | What it opens on |
|---|---|
| Ask Mosaic on a failed run, under a workflow's Executions | That run |
| Ask Mosaic on a node's error, in the node's window | That node in that run |
| The ? at the foot of the sidebar | Nothing in particular: ask anything |
| Build with Agent, under New workflow in the Workflows sidebar (admins) | A new workflow, with the sentence started |
It stays open beside the page, so the run or the canvas is still in front of you while you read. Close it with the ×.
#What you get without a model
Opened on a failed run, Ask Mosaic first shows what failed, what that error means and what to do about it, with a link to the part of this manual that covers the node.
This part needs no model. Nothing is sent anywhere, it is included on every plan, and it works with the model features switched off. When Mosaic does not recognise an error by itself, it says so.
#Asking a question
With a model connected, the box at the foot of the pane takes a question. On a failed run, Explain this run asks the obvious one for you.
Under each answer, Looked at lists what was read to produce it, such as a page of the manual or a run.
This part needs:
- a model connected under Integrations
- the model features switched on for the workspace by an owner (see Turning AI on)
- Pro or above
When one of these is missing, the pane says which.
#Drafting a workflow
Describe what the workflow should do, for example "Build a workflow that mails the team when a check finds differences". The answer comes with a card:
| On the card | |
|---|---|
| The nodes, in order | What starts it and what it does |
| Left for you to fill in | Fields that need a value only you have, such as who a mail goes to |
| A line in amber | Something to read before you run it, such as a node that runs a command or deletes a file |
Create workflow makes the workflow and opens it on the canvas. Until you press it, nothing is saved.
- A workflow made this way is always created switched off. Read it on the canvas, fill in what is left, run it by hand, and switch it on yourself.
- A draft never contains a password, a token or a key. Those fields are left empty for you, or point at an environment variable.
- Asked to change a workflow that already exists, it drafts a new one beside the original. The original is not touched.
- Drafting is offered to admins, because creating a workflow is an admin's right. See Who can do what.
#What is sent to the model, and what is not
Everything in this section applies to the model you connected. A model inside your own network keeps all of it there.
#Sent
- Your question, and the earlier questions and answers in the same conversation.
- For a failed run: the workflow's name; each node's name, kind and settings; how many items went in and out of each node; the error; the names of the fields the failed node was given; and the last thirty lines the failed node printed.
- When your question needs them: this workspace's workflows (their nodes and settings), a list of recent runs with their status and error, and the names of the workspace's checks, data sources, agents and monitors.
- Pages of this manual.
#Never sent
- The values in the items a workflow handled. Field names only.
- Rows from a check or from a data source.
- A data source's connection details: its address and its login.
- Passwords, tokens, keys and secrets held in a node's settings. The model is told only that one is set.
- The user and password inside an address written as
https://user:password@host. - A chat webhook's address beyond its host.
- A value a database put in quotes in its error message, when the node that failed runs a query or a check.
#Two things to know
Before the first question about a run, the pane states what the model is about to be shown.
#What is kept
- The conversation is not stored by Mosaic. It lasts until you close the pane or press Start again.
- What the model's provider keeps is governed by your agreement with that provider.
- A draft that is never created leaves nothing behind.
- Creating a drafted workflow is recorded in the audit trail like any other workflow: who created it, and when.
- Questions and answers are not recorded in the audit trail.
#Who can use it
| Viewer | Editor | Admin | |
|---|---|---|---|
| See what a failed run's error means | Yes | Yes | Yes |
| Ask a question | Yes | Yes | Yes |
| Have a workflow drafted, and create it | — | — | Yes |
Ask Mosaic reads only what the person asking can already read on screen, in the workspace they are in. It cannot run a check, a data source or a workflow.
#Connecting an assistant of your own
An assistant that speaks the Model Context Protocol (MCP) can read Mosaic's manual and the list of workflow nodes directly, to answer questions about Mosaic from inside the tool you already use.
| Address | https://<your Mosaic>/api/mcp |
| Sign-in | An API key sent as Authorization: Bearer <key>. Run and read is enough |
| What it can read | This manual, the kinds of workflow node and what each asks for, and the starting workflows |
| What it cannot read | Anything of your workspace: no checks, no data sources, no workflows, no runs, no rows |
| What it can change | Nothing |
Each use of the key updates the key's last used time, as any call through the API does.