Automation that starts where the work arrives
A flow starts on a schedule, an inbound mail or a changed file, then reads, decides, writes back and tells someone. Every run is recorded node by node.
Open a flow
The reminder nobody has to remember
Every Monday at 07:00 Copenhagen time it reads the entries that are past due, groups them by customer and leaves one reminder per customer as a draft in Outlook, firmer where the oldest entry is more than 30 days overdue. A person reads each one and presses send.
The order that arrives as an email
A flow can own an address. The mail's sender, subject and text become the run's input; attachments arrive as names and sizes only. A model reads the lines from the text, the sender's domain finds the customer, the flow creates the order header, then one sales line per pass of a loop, and replies on the same thread with the order number.
The check that tells the one person who needs to know
Every weekday at 08:00 it reads the sales orders whose shipment date has passed and that are not completely shipped. If there are any, the person picked on the Notify node gets the list, in the portal and by email. On a day with none, the run ends at the If and nobody is disturbed.
The run that stopped at the node that failed
A failed run reports a failure and stops exactly where it broke, with the error that node returned there to read. Uniconta is in early access: in the portal, and opened account by account.
Overdue reminder · weekly
- Schedule (Mon 07:00): Mon 07:00 · Europe/Copenhagen
- Read BC data (Cust. Ledger Entry (21)): Cust. Ledger Entry (21) · Open = true · Document Type = Invoice · Due Date < today
- For each (Customer No.): group by Customer No.
- Read BC data (Customer (18)): Customer (18) · E-Mail, Language Code
- If (branch): firmer tone where the oldest entry is more than 30 days overdue
- Ask a model (structured): subject + body · in the card's Language Code
- Draft in Outlook (outlook): to the E-Mail on Customer (18)
- Notify (Overdue reminder · weekly): workflow owner · drafts ready
Every run is recorded node by node.
What makes a flow safe to hand the ledger
- It starts on its own
A schedule, a mail, a file
A flow starts on a schedule, on mail to an address only it has, or when a file changes in SharePoint, OneDrive or a portal folder. Or someone runs it by hand. Business Central does not push events; a flow reads it when it runs.
- It is a real graph
Branches, loops, break and continue
The flow is drawn as a graph and checked before it is published. A missing trigger, a cycle, a step that reads an output no earlier node gives, or a setting a node cannot use stops the publish. A node nothing connects to is flagged as a warning.
- Every run is a recording
What each node returned, and how long it took
Every run keeps each node's status, its output or its error, and its time, so a failure can be read instead of reproduced. A dry run walks the whole graph: reads run for real, and every step that writes, sends or notifies is skipped.
Name the thing someone does every Monday
Most flows worth building are already written down somewhere as a procedure. Workflows needs its own licence, so ask us: book a demo, bring yours, and we will build it with you. Or start a trial to see the rest of the portal.
Or write to us at hello@uni4c.ai