Skip to main content

Automation

Build a flow once — it runs automatically every time.

A visual flow builder that automates SMS, email, notifications and webhooks. 31 event types, dynamic variables, conditions and full run history — no code required.

  • Visual drag-and-drop flow editor
  • 31 event types across sales, payment, portal and time clock
  • Dynamic template variables: customer name, plate, amount and more
  • Full run history with per-step error tracing

Set the rules once — the system runs them every time

Whenever an event happens in the system — an order converts, an invoice falls due, a customer opens the portal — a flow can fire automatically. Design happens in a visual editor with blocks for actions, conditions and wait steps. The flow saves continuously and can be switched on or off in one click.

Variables are dynamic: the template "Hi {{customerName}}, your {{make}} {{model}} is ready" gets filled with real data every time. Run history shows exactly what happened at every step, so errors can be diagnosed without guessing.

No manual follow-up on orders or payments

If/else conditions based on event data

Wait steps pause flows before the next action

Webhooks integrate with external systems

Out-of-the-box flows for order confirmation and invoice sending

Multi-shop support with global or shop-specific flows

Visual flow editor

  • Drag and drop

    Drop events, actions and conditions onto a canvas and link them with lines.

  • Auto-save

    The flow saves continuously while you edit — no "Save" button to forget.

  • Enable / disable

    A flow can be switched on or off in one click without deleting the configuration.

31 event types in seven categories

Flows fire from concrete events in the system — sales, payments, portal and more.

  • Sales and documents

    Document created, quote-to-order, order-to-invoice, unpaid invoice (7 days), credit note, status change and delivery date.

  • Payments

    Payment link created, sent, received, failed or cancelled.

  • Worksheets and time clock

    First clock-in, every clock-in, and completion of all jobs on the order.

  • Rentals and reminders

    Rental start/end and automatic reminder 1 day before an appointment.

  • Customer portal

    Login, document open, PDF download, payment-page open and document link sent from admin.

  • Inbound messages

    SMS received from customer, email received from customer.

Actions

  • Send SMS

    Pick an SMS template and inject dynamic variables. Sent automatically via your SMS provider.

  • Send email

    Pick an email template, fill subject and body with variables, send automatically.

  • Notify staff

    Push a real-time notification to all signed-in staff in the shop.

  • Wait

    Pause the flow for any number of minutes or hours before the next step.

  • Send webhook

    Forward flow data as signed JSON to an external system (CRM, booking).

  • Stop

    Explicitly end the flow — useful to stop one branch in a conditional flow.

Conditions and branching

  • If/else logic

    Branch the flow based on event data — e.g. "if amount > 5,000 DKK".

  • Many operators

    Equals, not equals, greater/less than, contains, starts/ends with.

  • Different actions per branch

    Both branches can lead to entirely different sequences of actions.

Run history and error tracing

  • All runs per flow

    Status (completed, failed, running), duration and step count for every run.

  • Per-step detail

    Click a run to see exactly what happened at each step — including error messages.

  • Unified log

    All flow runs across the shop in one place with filtering and search.

Default flows and multi-shop

  • Order confirmation by email

    Sent automatically when a quote converts to an order. Ready from day one.

  • Invoice by email

    Sent automatically when an order converts to an invoice. Ready from day one.

  • Global or shop-specific

    Flows can target one shop or the whole business. The flow log filters automatically.

Frequently asked questions

What is an event in a flow?+
A specific occurrence in the system that triggers the flow — e.g. "quote converted to order", "payment received" or "customer opened payment page". There are 31 event types across seven categories.
Do I need to know how to code to build flows?+
No. The flow editor is visual — drag blocks onto the canvas, link them with lines, pick templates and fields from dropdowns. No code.
How do dynamic variables work?+
Each event provides relevant data (customer name, plate, invoice amount, etc.) that is injected directly into SMS and email templates with a simple syntax.
Can flows have conditions?+
Yes. If/else blocks branch the flow based on event data. You can send different SMS messages depending on amount, customer type or document status, for example.
What happens if a flow fails?+
Run history shows every run with status and duration. Click in to see exactly which step failed and the error message — so debugging takes seconds, not hours.

Let the system send the messages for you.

Start free and build your first flow in 5 minutes — without writing a single line of code.