Automations: start workflows directly from the AI chat

Automations use company knowledge as context for recurring workflows and connect the platform to external software.

An automation here is an action that the platform carries out itself instead of leaving it to a person. It differs from an answer in that, at the end, an object is created or changed: a task, an appointment, a message, a transcribed text, an analysis.

The trigger is not a rule editor but one of three ways: a natural language instruction to Nex, an event in the platform such as uploading a file, or a conversation with a Chatbot.

Recurring work rarely fails at the individual step, but on the way between steps. A piece of information sits in a document, the resulting task is created in a second tool, the appointment in a third, the message to a colleague in a fourth. Every switch costs context, and every loss of context creates rework.

Traditional automation tools solve this with preconfigured if-then rules. That works for workflows that always look the same. For work with company knowledge, it falls short: there, the triggering sentence is worded differently every time and refers to content that the rule does not know.

Nex analyses the input and decides for itself whether a question to the knowledge base, internet research, a task or an appointment is meant. Names, deadlines and priorities are read from the same sentence. There is no command syntax to learn; the guide merely lists trigger words per tool for orientation.

Files uploaded to the knowledge base are processed without any further input: audio is transcribed, and scans and images are made accessible through text recognition. The result goes into the same index that Document search uses.

Connectors are available for chatbots and are set up on request.

We decide together in the project which systems you want to connect. Feel free to write to us about this in advance via the contact page.

• A Nexoria core product, Base or Pro plan. Automations are included; the terms are on the pricing page.
• A Workspace, whose shared content the workflow is allowed to use.
• Sufficient token allowance. Once the token allowance is used up, tokens can be topped up automatically or manually. Without a top-up, new AI requests are paused. Document search continues to work and does not consume any tokens.
• For email workflows, additionally the optional add-on Nexoria Mail.

An automation is not a second way in that bypasses the permission model. It accesses the same shared content as the person who triggers it.

Transcription, text recognition, embeddings and semantic search run locally on servers in Germany. Answer generation by Nex uses Mistral AI. The full classification can be found on Security and privacy.

• Tasks, appointments and messages from a natural language instruction.
• Recognition of people, deadlines and priorities in the same sentence.
• Processing on upload: transcription for audio, text recognition for scans and images.
• Analyses and aggregations of uploaded data, as a spreadsheet file on request.
• Appointment booking and handover to a member of staff from within the chatbot.
• Reuse of positively rated answers without additional token consumption.
• Integration of external systems via connectors, set up on request.