Automation in the neuland.ai HUB

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.

Talk to us

Ein Chat antwortet, wenn jemand fragt. Eine Automatisierung startet von selbst.

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.

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.

In chat

A good chat gets saved

You check the new supplier applications against the supplier policy once in the chat, and the result is right. One click turns this chat into an automation; a descriptive sentence works just as well.

Clarifying question

Every gap gets a rule

Which documents are mandatory? What happens if one is missing? Who gets the list? The neuland.ai HUB keeps asking until every case is covered.

Diagram

Every step is fixed

Read the inbox and the supplier database, check each application against the policy, draft a document request if something is missing. The diagram shows every condition and every tool; the AI only writes the text of the document request.

Test run

You see every step run

You start the first run manually and follow live which step is working. Changes happen in conversation: “Take the environmental certificate off the mandatory list.”

Schedule

From now on, it starts itself

On working days at 7 a.m. the automation starts without anyone stepping in. You see status and next run in one place, and you can pause at any time.

In chat

A good chat gets saved

You check the new supplier applications against the supplier policy once in the chat, and the result is right. One click turns this chat into an automation; a descriptive sentence works just as well.

Clarifying question

Every gap gets a rule

Which documents are mandatory? What happens if one is missing? Who gets the list? The neuland.ai HUB keeps asking until every case is covered.

Diagram

Every step is fixed

Test run

You see every step run

You start the first run manually and follow live which step is working. Changes happen in conversation: “Take the environmental certificate off the mandatory list.”

Schedule

From now on, it starts itself

On working days at 7 a.m. the automation starts without anyone stepping in. You see status and next run in one place, and you can pause at any time.

In chat

A good chat gets saved

You check the new supplier applications against the supplier policy once in the chat, and the result is right. One click turns this chat into an automation; a descriptive sentence works just as well.

Clarifying question

Every gap gets a rule

Which documents are mandatory? What happens if one is missing? Who gets the list? The neuland.ai HUB keeps asking until every case is covered.

Diagram

Every step is fixed

Test run

You see every step run

You start the first run manually and follow live which step is working. Changes happen in conversation: “Take the environmental certificate off the mandatory list.”

Schedule

From now on, it starts itself

On working days at 7 a.m. the automation starts without anyone stepping in. You see status and next run in one place, and you can pause at any time.

Example · In progress

Follow live which step is running.

Nothing goes out without approval.

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.

Kaltenberg Maschinenbau AG

German data center

Kaltenberg
Maschinenbau AG

ChatsProjectsAgentsAutomationsAppsKnowledge

Supplier Policy 2026New supplier backlogDocument request templateRisk analysis Q3

AgentAutomation supplier onboardingactive

Task: weekdays 7:00 AM · Supplier management inbox

Automation supplier onboarding

runningdone

Read 5 new supplier applications

Outlook · Supplier management inbox.

Checked against Supplier Policy 2026

Procurement knowledge · Mandatory documents per supplier.

Drafted 2 document requests

Hydraulik Sommer: supplier declaration · Feinguss Oberland: ISO 9001 certificate.

Send to suppliers

Two drafts in Outlook: Hydraulik Sommer and Feinguss Oberland.

ApproveApproved

Once Procurement gives the OK, both document requests go out.

The tools are fixed: Outlook, SQL database, Procurement knowledge, Teams.

Change it, for example: 21 days to submit

OutlookSQL databaseProcurement knowledgeMicrosoft Teams+ Context+3

Step 1 of 6

Built in Germany · German data center

Control

When a run starts and whom it reaches is set in advance.

What it did is in the history afterward.

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.

Start

Scheduled or manual

You set frequency and start time; you see the next run in advance, and you can pause at any time.

Recipients

Defined in advance

Which tools, data rooms and recipients a run reaches is set when you configure it, granular and versionable, within the approvals of your admins.

Log

Every run

Every tool call appears in the history, reproducible and auditable.

Documentation

ISO 27001, DPA

For audit and data protection, available documentation includes an ISMS per ISO 27001, a DPA under Art. 28 GDPR, technical and organizational measures, and the DORA addendum.

Best of Technology 2026 by WirtschaftsWoche, Process Management category.

Documentation in the Trust Center

Example · Result

The result is ready before your team starts.

Gaps flagged, document requests drafted.

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.

Supplier onboarding · Tue Sep 29 · 7 am run

3 of 5 complete

Next run Wed 7:00 AM

Supplier	Status	Document	Deadline
L‑2026‑0412 · Hydraulik SommerDue Oct 13	open	Supplier declaration missing · Draft in Outlook	Due Oct 13
L‑2026‑0415 · Feinguss OberlandDue Oct 13	open	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.

How long does setup take?

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.

How long does setup take?

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.

How does automation relate to the orchestrator?

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.

How does automation relate to the orchestrator?

What kind of work is a good fit?

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.

What kind of work is a good fit?

Can the automation reach ERP or DMS as well?

Yes, once they are connected; then every system is available to every run as a tool. What is already connected is listed under Integrations.

Can the automation reach ERP or DMS as well?

Yes, once they are connected; then every system is available to every run as a tool. What is already connected is listed under Integrations.

Does the neuland.ai HUB send emails without asking?

No. The run reads freely and creates drafts; nothing is sent, entered or changed until a human gives the OK.

Does the neuland.ai HUB send emails without asking?

No. The run reads freely and creates drafts; nothing is sent, entered or changed until a human gives the OK.

Can we change the steps without rebuilding?

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.

Can we change the steps without rebuilding?

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.

Can we trace what a run did?

Yes. Every tool call appears in the history with arguments, response, and duration: reproducible, exportable, and auditable.

Can we trace what a run did?

Yes. Every tool call appears in the history with arguments, response, and duration: reproducible, exportable, and auditable.

Can we pause an automation?

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.

Can we pause an automation?

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.

Where do the automations and their data run?

In the neuland.ai HUB, in your tenant, operated in the EU. Every step is logged and traceable. More under Security and compliance.

Where do the automations and their data run?

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.

Talk to us