A run is a case like any other. It inherits log, time limit, cancellation and approval from the flow system. It ends when the goal is reached, the step limit or the budget applies, or someone cancels it.
Agent platform
Set up an AI agent without coding
We set up the goal, tools, limits and trigger together with you, and you assemble the flow from building blocks. Checking, dry run and versions are built in.
In short
In ENGIVERITY an AI agent consists of a goal, permitted tools, fixed limits and a trigger, and you build the flow from blocks, without code. In Documents you set up flows from a trigger, conditions and actions per tenant.
Updated: November 2026
Overview
How we set up an agent
Five steps in ENGIVERITY, which the sections below explain in more detail.
Components
What makes up an agent
An agent in ENGIVERITY is a configuration. It consists of six details that you enter without code.
| Detail | What you define |
|---|---|
| Name | The agent appears under this name in lists and in the log. |
| Goal | One sentence in everyday language on what the agent should achieve. |
| Permitted tools | The list of what the agent may read or create. |
| Limits | Which projects and object types it covers and whether it only reads or also writes. |
| Writing without asking | Which writing steps it may carry out alone. All others are queued until a person approves. |
| Step limit and budget | How many steps and how much computing effort a run may use at most. |
The flow built from blocks
A flow in ENGIVERITY consists of steps, and each step is a building block with inputs and outputs. There are blocks for reading in and checking bills of materials, for branching, approving and rejecting, for notifications, reports and emails, for reading data sheets, and for agents themselves.
For each step you set how it behaves.
- A time limit caps how long a step takes.
- A repeat always has a cap.
- Branching goes forward. Depending on the result the flow continues on another path, and it cannot jump back.
- Every step can carry an approval point.
- After a restart the case picks up where it left off.
Triggers
Setting a trigger
A trigger says when a flow starts. Depending on the module, different ones are available.
| Trigger | How you set it | Module |
|---|---|---|
| Schedule | In plain words such as weekdays 07:30 or daily 06:00, in German time. | ENGIVERITY |
| Event | A new version, a finished check run, an uploaded data sheet, a granted approval or a new open point. | ENGIVERITY |
| Upload | An uploaded file starts the flow. | ENGIVERITY |
| By hand | A person starts the flow themselves. | ENGIVERITY |
| Document arrived | A document has arrived, is ready, checked, exported or rejected. | Documents |
| Deadline | Notice, contract end, discount, due date or the age of a clarification case. | Documents |
| Daily or weekly | Fixed times for reports and reminders. | Documents |
A missed time is counted, and a safeguard prevents a double start. Every trigger has its own log with the entries triggered, skipped with a reason, and error. You can switch it on and off at any time.
The flow workshop
In ENGIVERITY you put templates together without code. A check runs before saving. It looks at whether sources, types, mandatory details and approval roles are right, whether the structure fits and whether the flow runs in circles.
A dry run shows the result before anything takes effect. If the check finds defects, an assistant helps to fix them. Saving works only when the check has passed.
In Documents you set up flows per tenant. A flow there consists of a trigger, conditions and actions and can be switched on and off. Every execution is logged.
Versions and return to the standard
In ENGIVERITY every save creates a new version. A running case carries a copy of the definition it started with. If you change the template afterwards, that case stays as it was.
You can return to the standard that ships with the product at any time. That way you can try a change without losing the proven flow.
Interfaces
Connecting
Anyone who wants to control or observe agents and flows from other systems finds interfaces in both modules.
| Module | Interface | What for |
|---|---|---|
| ENGIVERITY | REST | Cases, templates, triggers and agents. |
| Documents | REST with API keys | Documents and flows. |
| Documents | Signed webhooks | Reporting events to your system. |
| Documents | Change feed | Fetch updates, always from the last position. |
Emails to third parties from the templates that ship with Documents start out as drafts. Users without administrator rights can change recipients only to addresses of the partner or its domains.
Questions and answers
Questions about building agents
Do I need programming skills?
No. You write the goal in everyday language and assemble the flow from building blocks in the flow workshop.
What can an agent actually call?
Only the tools on its list. In ENGIVERITY, agents read bills of materials, review results, data sheet values and drawings and research in the knowledge base. Tools that write wait in a queue until a person approves them.
How do I prevent endless runs?
In ENGIVERITY every agent has a step limit and a budget, every step a time limit, and repeats have a cap. A case can also be cancelled at any time.
Can I reset an agent to the standard?
Yes, in ENGIVERITY. Every save is a new version, and the standard that ships with it stays within reach.