August 2026

Updates released in August 2026.

Every email an agent sends is clearly marked as AI-written

August 30, 2026 — Automatic AI identification on all agent email, in line with the EU AI Act

When an agent sends, replies to, or forwards an email on your behalf, it now always says so. Nothing to configure — identification applies to every agent, every mailbox, on both Microsoft 365 and Gmail.

• Clear disclosure for recipients — a short line at the top of the message states that it was generated by AI, and a footer carries a verification link.
• The sender is never presented as a person — emails come from an identity like "Anna — AI Assistant of Ivan Petrov", never plain Ivan Petrov. Acting for someone is never the same as being that person, and the platform now enforces the distinction.
• Replies still reach a human — replies are routed to the responsible person's address, so recipients always have someone to answer.
• Signed verification — every message has its own verification page where anyone can confirm it was AI-generated, which agent wrote it, and when — without exposing the message content or recipients.
• Machine-readable, too — messages carry standard markers so mail clients, filters and compliance tools can detect AI-generated mail automatically.

Learn more in AI Identification in Email.

Agents can start working on their own with Activation triggers

August 30, 2026 — The new Activation tab turns agents into proactive workers

Until now, every agent waited for you to start the conversation. The new Activation tab in the agent editor lets an agent wake up and act on its own — on a schedule, on an event, or on an incoming webhook.

• Scheduled runs — set an agent to work every morning, every Monday, or on any repeating schedule. It opens its task and reports back like any other conversation.
• Event-driven — when something happens in a connected system, the right agent is triggered automatically and takes care of it.
• Webhooks — external systems can trigger an agent with a simple call, so incoming requests get handled without anyone watching the inbox.
• One task at a time — triggers for the same agent are processed in order, so two runs never step on each other.
• Actions that need your approval wait for you — if a background run reaches a step such as sending an email, it pauses, notifies you, and shows the approval card in the conversation. Unanswered approvals are cancelled automatically after 24 hours so nothing stays pending forever.

You find Activation where Triggers used to be — renamed and, more importantly, now fully working.

August 25, 2026 — Agents can now summarize and group data

Until now, a question like "what did we sell per month, per customer, last year" meant pulling thousands of records. Agents now use the new summarization API in ERP.net 27 to ask the business platform for counts, sums and grouped totals directly, and receive only the result.

• Answers over big data sets — totals, counts, minimum and maximum values are calculated on the server, so a question spanning a whole year answers in one step.
• Grouping the way a report would — group by customer, product, warehouse, status or responsible person, and combine several groupings at once.
• Time series out of the box — group by year, year-month or exact date to get trends, comparisons and "this month versus last month" answers.
• Filter first, then summarize — the usual filters still apply, so you can narrow to a period, a company or a document type before the totals are calculated.
• Cheaper and faster — because only the summary travels back, answers arrive quicker and use far fewer AI credits than reading the underlying records.

Ask things like:

• "Sales per month for 2025, by product group."
• "Top 10 customers by total invoiced amount this quarter."
• "How many open orders per warehouse, and what is their total value?"
• "Largest order value per supplier over the last 6 months."

Agents choose automatically between a normal data query — when you need the actual records — and a summary, when you need numbers about many records.

BI-style apps in the App Builder

August 25, 2026 — Build dashboards and charts that stay fast on any data volume

The same summarizing power is available to apps, so the App Builder can now produce real analytical applications.

• Dashboards with live figures — KPI tiles, totals and counters read a single summarized result instead of downloading records.
• Charts and trends — monthly revenue lines, per-branch bar charts, share-of-total breakdowns and period comparisons.
• Drill-down — start from a summary, then let the user open the underlying documents for a single group.
• Built for scale — an app over hundreds of thousands of documents stays responsive because the heavy work happens on the business platform.

Just describe what you want to see — "a dashboard with sales per month and per salesperson, with a filter by branch" — and the App Builder will assemble it.

Requirement: summarizing works with ERP.net version 27 and above. Agents and the App Builder are aware of the version of the connected instance and will fall back to regular queries when it is older, so nothing breaks on earlier versions.

Meet Digital Entities — agents that keep working on their own

August 17, 2026 — A new kind of agent that remembers, watches, and acts even when you are not around

Digital Entities are the next step up from regular agents. A normal agent waits for your question; a Digital Entity keeps watching, remembers what matters, and steps in when something needs attention.

• They never forget the important stuff — facts, tasks, deadlines, and open issues stay alive across days and weeks, so nothing falls through the cracks.
• They notice what did not happen — a customer reply that never arrived, a delivery that missed its window, a deadline that is quietly approaching.
• They work on their own rhythm — set them to watch a process, a customer, or a list of obligations and they keep checking back.
• They take initiative — when they spot something that needs action, they can warn you, start a task, or record what happened.

Use a Digital Entity to:

• Track contractual deadlines and warn you before they slip.
• Follow up on customers who have not replied in a set number of days.
• Monitor stock levels, orders, or support tickets that need attention.
• Work through a long follow-up list and report progress each morning.

Digital Entities are available as an upgrade for any agent. While active, they use 2 AI credits per day.

Installable apps have a new address

August 15, 2026 — Apps you install now live at app.operator.net

Apps opened full-screen or installed on a phone or desktop now use a shorter, cleaner address at app.operator.net.

• Old links keep working — anything you bookmarked or shared previously is forwarded to the new address automatically.
• One-time reinstall for a clean icon — if you installed an app before this change, uninstall it once from your browser's app menu and install it again from the app's full-screen page. Everything else stays exactly as it was.

More room and better records for Pro apps

August 7, 2026 — Bigger file limits, retirable records, automatic history and a business date

The app backend got a round of upgrades that make it usable for real, growing data sets.

• More room for files — an app can now keep up to 500 stored files and 100 MB in total, instead of 50 files and 50 MB. The 5 MB limit per file stays the same.
• Retire records instead of deleting them — every record now has an Active switch. Lists show only the active ones, a direct lookup still finds a retired record, and retired records can be shown again at any time from the Backend tab.
• Who changed what, and when — every record keeps the moment it was created and last changed, together with the user behind each change. It is filled in automatically, so "added today" and "recently changed" lists are instant.
• A business date per table — a table can now carry one named date that matters to the business: document date, activity date, due date. Date ranges and newest-first lists on it stay fast however large the table grows.
• Steadier record addresses — apps now give each record a permanent address of their own instead of reusing a business code that may later change. Codes stay editable without creating duplicates, while genuinely permanent identifiers are still used as the address where that helps.

Pro apps can call external services safely

August 5, 2026 — Secrets and web requests are now part of the app backend

Pro apps can now talk to other systems — a courier API, a payment provider, a partner platform — without ever holding the credentials.

• Write-only secrets — store API keys, client ids and secrets in the app backend. They can be set and replaced, but never read back: not by you, not by the App Builder, not by the running app.
• One secret, many customers — every secret can have a global value plus a value for a specific ERP.net instance. When the app runs on that instance its own value is used automatically, with the global one as fallback.
• Requests defined once, called by name — the address, headers, body and credentials live in the backend. The app just says which request to run and passes a few parameters, so it can never be redirected elsewhere.
• Logins handled for you — bearer tokens, basic authentication and OAuth2 client credentials are supported, with access tokens fetched, reused and renewed behind the scenes.
• Test before you ship — run any request from the Backend tab and see the response with all credentials hidden.

Both sections live in the Backend tab of Pro apps, next to Files and Tables.

Pro apps can keep their own records

August 3, 2026 — Pro apps now have their own table storage

Apps on the Pro tier can now store structured records of their own — orders, settings, drafts, favourites, checklists — without pushing anything into ERP.net. Just tell the App Builder what the app should remember and it takes care of the rest.

• Records that belong to the app — anything that is not ERP.net business data and not an uploaded document now has a proper home.
• Ask in plain language — "keep a list of the daily requests", "remember my last selection", "save this form so I can finish it later".
• Grouped and searchable — rows can be grouped (by month, category, customer…) and searched by their display name, so lists and reports stay fast even when they grow.
• Per instance or shared — a table can keep separate records for each ERP.net instance, or one shared set for the whole app.
• Read-only tables — mark reference data such as price lists or statuses as read-only so the running app can read it but never change it.
• Browse and edit from the App Builder — the Backend → Tables section lists every table with its rows, a search box, and the full content of any row.
• Generous limits — up to 100 000 rows per table and 200 000 rows per app.

Table storage is available for Pro apps, next to stored files, in the Backend tab.