AI Analyze
Hands the run to a model and gets back a readable account of what happened.
Analyze/summarize logs and state
Reach for it when
- A nightly run whose report should say what went wrong, not just that something did.
- A log capture nobody is going to read in full.
- Putting a summary into the message the notify block sends.
Every setting this block has. A field marked only when appears once you have chosen the mode above it — those are alternatives to each other, not extra things to fill in.
- User promptstarts at —
Optional. Ask what you want to know — "did the install succeed?" — or drag in a field from the left. Blank gives a general summary.
Ask for what you want — or ask for nothing
The field is optional, and blank has one obvious meaning: summarise this run. Fill it in when you have a specific question.
the run attaches itselfevery step and its settingswhat each step returnedcaptured logsthe last screenshotDid the checkout complete, and if not, where did it stop?The run reached the cart and added two of the three items. The third tap landed on a “Sold out” overlay, so Assert / Verify found no confirmation screen. No crash in the log.
Put it before the block that tells someone
Its summary can be referenced by the message below it, so what arrives in Slack is the explanation rather than “a step failed”.
AI AnalyzeSend to SlackSend EmailIt runs where it sits, including with nobody watching
It executes on the worker in graph order, so the summary exists by the time the step below it sends anything — on a scheduled run as much as a hand-run. If the model cannot answer, the step is recorded as failed but the branch carries on: suppressing the message that says the nightly run broke would be the wrong trade.
AI AnalyzeSettings User promptOptionalDid the checkout complete?
- The model's answer, for a later step to put in a message, a ticket, or a condition.
- It reports; it does not route. To take a different path on what it concluded, use AI Decide, or put an If / Branch on something concrete.
- A failed Analyze does not stop the branch — the step goes red and everything after it still runs, with no summary to reference.
- It reads what the run captured. No Read Logs step means no logs to reason about, and the summary will be about screenshots and step results only.
- Inference is metered against your plan's monthly allowance.