Flows and rules
Almost any tool can send an email when a status changes. Many processes need more: a flow gathers data from several systems, processes a file line by line, calculates deadlines in business hours and continues differently depending on the result. In nexxcite, you set all of this up in the editor.
What carries a process
Two tools
A flow is a sequence of steps that someone or something triggers: a click, a schedule, an incoming email, a call from another system, a value crossing a threshold. It has a start, an end and a visible path in between.
A rule has no trigger in that sense. It simply applies. A required field is always required. A calculation always follows from its inputs. A visibility rule always applies.
Many tools only know flows. There, even the obvious has to be rebuilt as automation, and the configuration becomes hard to follow over time: many small automations that are really rules, and nobody knows any more which one fires when.
In nexxcite, you define rules on the data model. They apply everywhere: in the interface, through the API and in flows running in the background.
Low code in practice
A process almost every company knows: the purchase requisition with amount-based approval. Every step is set up in the editor without programming, and you can change it yourself later.
A form you design yourself: required fields, picklists from your master data, attachments. Which fields someone sees depends on their role.
From the description, AI suggests the commodity group and cost centre. The requester confirms or corrects. The entries become more accurate without anyone needing training.
Team leads approve up to €1,000, heads of department above that, and from €10,000 procurement as well. You can change these thresholds yourself later in the editor.
The approver gets a task and an email. If nothing happens, the platform sends reminders and escalates according to your rule. Deadlines are counted in working hours.
Once approved, the platform creates the order in the ERP system through its interface, using the values from the request. Nobody has to retype anything, and both systems show the same status.
Requesters see their case in the portal, procurement sees its analysis in the dashboard. Both are views of the same data, so nobody has to keep a separate list.
This is how a process like this takes shape in the editor.
You make later adjustments yourself in the editor.
What a flow can do
All building blocks are available without programming and without an add-on product.
The complaint must be acknowledged within 24 business hours, the change needs approval before the maintenance window, the safety briefing expires after twelve months. In nexxcite, you set this up without programming.
Create, update, delete, link and unlink, across relationships too, down to every related line item.
Conditional branches, loops over records, files and lines, variables, wait points and questions back to people.
Calls to other systems with sign-in, starting scripts and programs, sending and receiving email, connection to your user directory.
Attach, read, write, delete, process line by line. JSON, XML, Excel and CSV. Stored in the file system or in cloud storage such as Azure Blob Storage and S3.
Language models as an optional step in the flow: suggest field values, summarise and classify text, an assistant with access to tools. You use your own AI account for this.
Defined in one place
Rules apply wherever data is edited
They are defined on the data model and apply in the interface, through the API and in flows running in the background. You do not need separate automations for things that should be a given.
Triggers
A button, a menu entry, opening a form or an action from a list, including for several selected records at once.
A record is created, changed, saved or deleted. The flow can run before or after saving and cancel the operation if needed.
Run on a calendar or when a value crosses a limit, such as a deadline expiring in 24 business hours.
A monitored mailbox receives messages. Rules decide by sender, subject, content and attachments which process results, including matching it to an existing case.
A connected system triggers the same flow a click would. There is no second, different processing path for machine calls.
The flow is visible
Configurations often become hard to maintain because logic spreads across scripts, triggers and automations that someone set up at some point.
Steps, branches and loops are arranged graphically rather than programmed. The same view exists for all the business logic of a record type.
FAQ
Yes. Wait points and questions back to people are part of flow control, for example an approval that has to be given before the flow continues.
Business hours and public holidays are a definition of their own. Deadlines and escalations count in business hours, not calendar hours.
Yes. Flows can run before saving and cancel the operation. For simple checks, a validation rule with its own error message is often enough.
Yes. Tasks that run in the background are monitored. If nexxcite runs on several servers, it is defined which one handles the schedules, so nothing runs twice.
Yes, if you wish. You describe the logic, for example "up to €1,000 the team lead approves, above that the head of department", and the AI creates the rule and the flow in a draft. Neither takes effect until you approve it.
Live demo
Ideally one with exceptions, deadlines and another system in the middle. A flow like that shows you whether the platform fits your requirements.