Platform

Let the platform do the follow-up

Reminders, reports and order files go out on their own while your team gets on with something else.

Occurs when an order has been created.

Live
  1. When an order is created Event order.created Trigger
  2. Order total Continues when greater than €7,000.00 Filter
  3. Send email Subject Order {{order.id}} awaits your approval Email
A workflow that sends large orders on for approval when an order is created.

Today someone on your team sends reports and reminders by hand every Monday. If they’re on holiday, it doesn’t get done. Now it runs on its own.

  • Fennic A/SWeekly report, week 41 Mon 5 Oct
  • Fennic A/SReminder: 2 orders waiting for approval Mon 5 Oct
  • Fennic A/SWeekly report, week 42 Mon 12 Oct
  • Fennic A/SWeekly report, week 43 Not sent · holiday
Sent mail today: the same report and reminder sent by hand every Monday, and the holiday week missing.

Build the workflow once, and it runs

A workflow starts on an order, an expiry, a leaver or a set time. You build it in a visual editor and test it before it goes live.

    1. Event Order created
    2. Wait 1 day
    3. Condition Still awaiting approval
    4. Action Email the customer’s approver
    Workflow: when an order is created and still waits after a day, the customer’s approver gets an email.

    1Chases the approvalWhen an order has waited a day

    1. Schedule Every Monday at 08:00
    2. Action Generate report, new rows only
    3. Action Email Fennic A/S
    Workflow: every Monday at 08:00 the report is generated and emailed to the customer.

    2Sends the customer the reportEvery Monday at 08:00

    1. Event Order approved
    2. Action Put order file on SFTP
    3. Action Send webhook
    Workflow: when the customer has approved an order, the order file is put on the supplier’s SFTP.

    3Sends the order to the supplierWhen the customer has approved

It gets done, even when you’re on holiday. And you can see every run, step by step.

    • Mon 2 Nov 08:003 of 3 steps Completed
    • Mon 26 Oct 08:003 of 3 steps Completed
    • Mon 19 Oct 08:003 of 3 steps Failed · run again
    • Mon 12 Oct 08:003 of 3 steps Completed
    The run history of the weekly report to Fennic: four Mondays, one run failed on a step and was run again.

    You see every runThe history shows each step of each run, and if something fails, you can run it again.

  1. Customer Fennic A/S Supplier Workshop, Aarhus
    IDCustomerDelivery
    #4203Fennic A/SShip to workshop
    #4198Fennic A/SDrop-off
    Scheduled deliveryXLSX by email Every Monday, 08:00
    A repairs report filtered by customer and workshop, with scheduled delivery.

    The customer gets the report every weekYou build the report once, and a workflow sends it as XLSX or CSV by email or SFTP, with only the new rows.

Questions from resellers

What does it cost?

The price follows what you sell through the platform. Contact us for a quote.

Do I need to know how to code?

No. You build workflows in a visual editor in your back office.

Can I test a workflow before it goes live?

Yes. You do a test run, and the draft is kept apart from the version that is running.

Can a workflow apply to one customer?

Yes. It can apply to all your customers or to one.

Can it talk to my own systems?

Yes. A workflow can call a webhook or put a file on SFTP.

See one of your tasks as a workflow

Bring a task your team does by hand today, and we build it in the demo.