Skip to main content
Version: 0.24.0

AI Actions

The AI group is new since 0.14.2. It covers two different jobs: generating parts of a scenario from a description, and extracting structured data from unstructured content.

note

These actions send content to the Aiviro AI service. Do not point them at data your organization is not allowed to process externally, and use Result is secret / Sensitive Data on the surrounding actions when handling personal data.

Prompt Actions

A container action that builds its own child actions from a plain-language description. Describe what should happen, and the AI generates the actions inside the block; you then review, edit and re-order them like any hand-built section.

Because the generated actions stay visible in the Commands tree, the AI is only a starting point — nothing runs that you have not seen.

The Prompt Actions dialog with a numbered prompt and the six actions generated from it listed below

Generated actions is a preview: the list shows what the AI produced, and pressing Save drops those actions into the Commands tree as the children of the block, where each one can be opened and edited on its own. Recent Prompts at the top recalls a prompt you have used before, and Regenerate Prompt asks for a fresh attempt at the same description.

ParameterDescription
TitleLabel shown on the block in the tree.
PromptDescription of what the generated actions should do.
tip

The block remembers the prompt the current children were generated from. Re-running generation after editing the prompt replaces the children, so keep hand-tuned actions outside the block — or copy them out before regenerating.

AI Read

Extracts structured fields from a document, a screen, the clipboard or a variable. Where Get reads one value from one place, AI Read takes a whole page of unstructured content and returns the fields you asked for.

The AI Read form with Source Type set to File, Instructions filled in and three rows in the Extract template table

Here Instructions and Extract template name the same three fields — the instructions say in words what to look for, the template fixes the name and type of each returned value.

ParameterDescription
Source TypeWhere the content comes from: Screen (what the robot currently sees), File (a path you supply), Clipboard, or Text (the contents of a variable). Choosing File adds a Document path field with a file picker.
InstructionsWhat to extract, in plain language. You can name the target fields here too, one per line — e.g. "Read the applicant's details from the document: name = person_name, surname = person_surname".
Extract templateCollapsible table of the fields to return — Field Name and Type per row, with Add to append another and a bin icon to drop one. This defines the shape of the result.
Save to variableVariable that receives the extracted data. Default processed_text.
Send image contextAlso sends the image to the model, which improves results on documents where layout carries meaning — tables, forms, invoices. Default off.
Custom JSON schemaAn explicit JSON schema for the result, for cases where Extract template is not expressive enough. Optional. (Advanced options)
tip

Name the fields in Extract template the way you want to use them later — the result is a structure keyed by those names, so invoice_total reads better in the rest of the scenario than field_2.

Process Invoice

Reads an invoice PDF and returns its parsed content — header data and line items — without you defining extraction rules.

📸 Screenshot needed — /img/editor/actions/ai/process_invoice.png

Capture: the Process Invoice form, and ideally the Variables panel showing the parsed structure it produced. Use an invented invoice: the supplied shot was rejected because the expanded invoice_insportline structure held a real supplier's invoice — company name, bank, invoice number and amounts were all readable. Run the action on a made-up invoice before capturing. Note: the old image is actions/files/pdf_reader.png — the action was renamed from Aiviro PDF Reader and moved from Files to AI, so the screenshot needs both a new name and a new capture.

ParameterDescription
PDF File PathInvoice PDF to read.
Save to variableVariable that receives the parsed result.

Which one should I use?

TaskAction
Read one known value from a known place on screenGet (Tools)
Read several fields from a document or a busy screenAI Read
Read a standard invoiceProcess Invoice
Pull fixed values out of a PDF with positional rulesExtract PDF custom (Files)
Draft a section of the scenario for youPrompt Actions