Workflow automation

Business process automation: what repeats, the system does

We set up rules like “when this happens, do that”. An invoice after payment, a reminder after the due date, a task for sales after a new enquiry.

Example rule
  1. Trigger: payment received
  2. Condition: order above CZK 5,000
  3. Action: issue and send the invoice
  4. Action: task for the warehouse

How process automation works

Every automation has three parts. The trigger is an event, such as a new order, a received payment or an upcoming booking. Conditions decide when the rule applies. Actions say what happens: send an e-mail, issue an invoice, change a status, create a task or pass data to another system.

The rules run in our system on the same data as orders, stock and invoices. Nothing has to be synced between tools, and every automated step is recorded in the history, so you know what the system did and why.

Where to start

The biggest savings come from processes that repeat every day, follow clear rules and are error-prone when done by hand.

Order confirmations and status e-mails.

Invoices and reminders.

Handing an enquiry to sales.

Bookings, payments and access.

Examples from practice

Invoice after payment

The customer pays, the system issues the invoice and sends it by e-mail.

Cancelling unpaid orders

If an order waits 24 hours for payment, it is cancelled and the goods return to stock.

Overdue reminder

An unpaid invoice past its due date is sent again with a payment QR code.

New enquiry

A website form creates a contact, a task for sales and a reminder in three days.

Smart lock code

30 minutes before a booking, an access code is activated and e-mailed to the guest.

Low stock

When an item drops below its limit, the buyer gets an e-mail.

How a rule is created

1

Trigger

We pick the event: new order, payment, status change, time or booking.

2

Conditions

We define when the rule applies: amount, customer tag, product type.

3

Actions

We decide what happens: e-mail, invoice, status change, task, call to another system.

4

Review

We switch the rule on, watch the first runs and fine-tune it.

Security and control

Automation follows the same rules as people. You see what it did and can switch it off at any time.

  • Field-level change history, including automated steps
  • Roles and permissions across the whole system
  • Scheduled jobs, for example daily or hourly
  • Webhooks and connections to other systems
  • E-mail notifications

What you can rely on

A system we know inside out

We have been developing and running it for 8 years. When you need a change, you do not have to chase a third-party vendor.

Your data stays yours

We hand your data over at any time in the format you need. Invoices can also be exported for Pohoda and as ISDOC.

You pay for what you use

A one-off implementation plus a monthly fee based on the features and volume you use. Parts you do not use cost nothing.

Every change is traceable

The system records who changed what and when, including automated steps. Each user only sees what their role allows.

What would you like to stop doing by hand?

Pick one process. We will show you how it could run on its own.

Book a consultation

Frequently asked questions

Do we need a programmer for automation?+

No. Common rules are set up in our system without programming, and we set up the first ones with you. More complex connections to other systems via API or webhooks are handled by us.

How do I know what the automation did?+

Every automated step is recorded in the history just like a human step: what happened, when and under which rule. If something looks wrong, you can trace it in moments.

Can we change the rules later?+

Yes. You can edit, switch off or add rules whenever your process changes. Before a bigger change we test it so it does not affect running orders.

Which process should we automate first?+

The one that repeats every day, follows clear rules and is error-prone. Most often that means invoices after payment, confirmation e-mails and reminders. We choose it together in the operations audit.