Skip to the page
Eurus
Try it live
Menu

S · Systems

Your systems, read where they already are.

Your payments, shop, customer list, sign-ins and HR records stay where they are. Eurus reads them, checks what happens in them, and runs the work between them.

Try it live Book an audit

Compliance, kept on every record

Connected today

Each connection is built once and serves every organisation that uses it. The board says which have read a live business account, which are built against the vendor's API and ready to connect, and which wait on the vendor. Connecting yours takes a key or a sign-in.

What each system is checked for

5 proven on a live account

25 built against the vendor's API, ready to connect

3 built and tested, waiting on the vendor

and files, and your website

Payments · 6

Online shops · 8

Accounts · 4

Sign-in and devices · 3

Staff (HR) · 3

Cloud · 1

Code · 1

Tickets · 1

Customer lists · 4

Calendars · 2

Anything else · 1

Anything else

Files and spreadsheets

Ready to connect

For a system with no connection: upload its export, or link a Google Sheet. The file goes through the same reading and the same checks.

Up to 4 MB a file. The kind is told by the file's own first bytes.

  • CSV and tab-separated text
  • Excel workbooks (.xlsx)
  • Older Excel workbooks (.xls)
  • OpenDocument spreadsheets
  • JSON exports
  • XML exports
  • UBL e-invoices, as Peppol sends them
  • Word documents (.docx)
  • PDFs with a text layer
  • Google Sheets, by link

PDF and Word documents are read as text. Reading scans and photos is coming.

How a connection reads

  • The first read

    The first read brings in recent history without raising an alarm for every old record. After that, changes arrive as events.

  • Read twice, kept once

    Reading the same records again keeps each one once. A record that changed becomes a new event.

  • One read at a time

    Each system is read when it is due, one read at a time. A system that keeps failing is read less often until it answers.

  • Your website, signed

    An enquiry from your website arrives signed, becomes an event and starts its workflow. A resend is recognised as the same enquiry.

  • A spreadsheet, the same way

    A system with no connection can send an export. It goes through the same reading and the same checks.

  • Work starts when you say

    A change seen in one of your systems starts a workflow only once a person has turned that on.

Try this in a copy of your own, for two hours, with nothing to sign up for.

Open your own copy

Workflows

The follow-up work between systems: an approval, a notice that falls due, a payment and its receipt, a reminder before a deadline.

  • Versioned

    Each change to a workflow is a new version. A run keeps the version it started on.

  • Checked before saving

    The editor stops a save that has errors, and warns about the rest.

  • Tried first

    A dry run on test data shows what would pass and what would run, before anything runs for real.

  • Stops cleanly

    A step that fails is tried again. After its last try the run waits for a person, and resumes from that step once the cause is fixed, repeating nothing.

  • Waits for approval

    An approval step waits for a named person. One left waiting too long is raised.

  • Payment links

    An amount due becomes a Stripe payment link. Asking again gives the same link, and the payment settles once.

Sandbox first

  • Nothing sent

    Every organisation starts in sandbox. Its messages are written to an outbox with their recipients, and none is sent.

  • Live when ready

    Messages go live only when FourWinds switches the organisation to live.

  • Tried, then handed over

    Once live, a message that fails is tried again, and after three tries it stops with the reason kept.

Start here

See it on a business of your own.

Open your own copy in a few seconds and use it for two hours, with nothing to sign up for. When you want it on your own systems, we start with an audit.

Try it live Book an auditNext: Support