By 7 am, the inbox is checked. On its own.
Describe a recurring task in the chat. The neuland.ai HUB turns it into an automation that runs on a schedule or at the push of a button and shows every step.
A chat answers when someone asks. An automation starts on its own.
Recurring work such as checking incoming requests, matching documents or preparing follow-up requests runs on a schedule or at the push of a button, in the same order every time. No one has to remember to kick it off.
Set up
Describe it in the chat, set it up as an automation. Test first, then it runs on schedule.
You describe what should happen every working day. The neuland.ai HUB asks follow-up questions and builds an automation from it that you test before it starts on its own.
Example · In progress
Follow live which step is running. Nothing goes out without approval.
Each step reports as soon as it finishes, along with the tool it used. The document requests wait as drafts in Outlook until Procurement approves them.
Maschinenbau AG
Task: weekdays 7:00 AM · Supplier management inbox
Read 5 new supplier applications
Checked against Supplier Policy 2026
Drafted 2 document requests
Send to suppliers
Once Procurement gives the OK, both document requests go out.
The tools are fixed: Outlook, SQL database, Procurement knowledge, Teams.
Control
When a run starts and whom it reaches is set in advance. What it did is in the history afterward.
Before the schedule takes effect, you review the diagram with every condition and every tool. After that, the history shows for every run what was read, drafted and approved.
Best of Technology 2026 by WirtschaftsWoche, Process Management category.
Example · Result
The result is ready before your team starts. Gaps flagged, document requests drafted.
An example: five suppliers have registered since yesterday, three with all documents. The automation has read the mailbox, policy and supplier database without asking back; the two requests for missing documents are ready in Outlook, and one click from purchasing sends them.
3 of 5 complete
| Supplier | Status | Document | Deadline |
|---|---|---|---|
| L‑2026‑0412 · Hydraulik SommerDue Oct 13 | open | Supplier declaration missing · Draft in Outlook | Due Oct 13A |
| L‑2026‑0415 · Feinguss OberlandDue Oct 13 | openB | ISO 9001 certificate expired · Draft in Outlook | Due Oct 13 |
| L‑2026‑0409 · Kabelwerk Nordheide | complete | all 6 documents present | |
| L‑2026‑0411 · Logistik Albers | complete | all 6 documents present | |
| L‑2026‑0414 · Systemhaus Weber | complete | all 6 documents, code of conduct signed |
- Deadline per Supplier Policy 2026: 14 days from sending.
- Still missing after 14 days: follow-up in Procurement.
How they differ
Chat, agent, agent chain or automation? What fits when, and what starts on its own.
All four use the same Orchestrator, the same tools, the same knowledge. The difference: who triggers it and how fixed the steps are.
Chat: the question right now
You type, the neuland.ai HUB picks the tools and answers with a citation. Right for anything that comes up once, such as a follow-up question about a single supplier.
Agent: the task with fixed rules
Instructions, knowledge, tools and model are fixed. Whoever starts it gets results by the same rules, for example your own supplier check agent for every new supplier.
Automation: fixed steps on a schedule
Saved steps, conditions and loops. It starts on a schedule or manually and goes through the same steps every time.
Agent chain: several agents in sequence
Type “/” to call one agent after another in the same chat, for example first your own supplier check agent, then the Corporate Mail Writer for the document request.
FAQ
What IT and business units want to know before getting started.
One conversation and one test run. You describe the work, answer the follow-up questions and watch the first run live, without any programming. Admins decide which roles use automations.
In the neuland.ai HUB, the Orchestrator directs every step of every request, in chat and in agents. An orchestration saves this control in visible form: as a diagram, with a schedule and tools you define in advance.
Anything that recurs on a fixed cycle and spans several systems, for example follow-up on meetings from Fireflies.ai, a weekly list of open Jira tickets per team, the Outlook calendar overview for management. One-off cases that need judgment belong with an agent.
Yes, once they are connected; then every system is available to every run as a tool. What is already connected is listed under Integrations.
No. The run reads freely and creates drafts; nothing is sent, entered or changed until a human gives the OK.
Yes, in conversation, for example: “21 days to submit instead of 14.” The neuland.ai HUB adapts the diagram; you start the changed run manually first, before the schedule takes over again.
Yes. Every tool call appears in the history with arguments, response, and duration: reproducible, exportable, and auditable.
Yes, at any time. You see status and next run in one place; if you change the steps in conversation, start the changed run manually first.
In the neuland.ai HUB, in your tenant, operated in the EU. Every step is logged and traceable. More under Security and compliance.
The same list every morning? Your first automation.
Bring a task that comes up the same way every day or week, and the systems it touches. Together we sketch the steps, follow-up questions and schedule.