Path
A Path is the connection to one system, for example Salesforce or Tripletex. It holds the address, keys and settings. Keys are stored encrypted, and only your organisation’s own connections can access them.
Waysayer
Waysayer Integrations
Take control of the data flowing between your systems.
Orders, customers, hours, invoices or something else entirely: Waysayer fetches the data, checks it, adapts it and sends it where it needs to go. It can run on a schedule or when something happens. Every run is logged step by step, so it is easy to see where something stopped.
- Systems with an API
- Webhooks in through Gates
- Data stored in the EU
One run
Completed-
GATE
A system sends an event
The Gate checks who is sending and starts the right Way.
-
WAY
The Way does the work
Checks the content, looks up values in its own tables and transforms fields and values.
-
PATH
The system is updated
The Path delivers the data to the system that needs it.
-
LOG
Every step is logged
With status and time, so it is easy to see where something stopped.
How it is built
Paths, Ways and Gates
An integration in Waysayer consists of three building blocks. The names recur in the portal, in the plans and in the platform limits.
Way
A Way coordinates the work. It fetches and updates data through Paths, checks the content and chooses a route, looks up and stores values in its own tables, transforms fields and values, and much more.
Gate
A Gate is the way in for other systems. It has its own address that receives webhooks and API calls, can check who is sending, and starts the right Way.
Ways
What a Way does
Fetch and send
Read and write through each system’s API, with a ready-made template or set up to the system’s requirements.
Checks before updating
Check that the required information is there before anything is passed on, and stop with a clear reason if it is missing.
Transform fields, codes and values
When systems use different terms, for example different status codes or fields with other names.
Lookup store
Simple tables for mappings and reference values, for example which customer ID in one system belongs to which in another, or which orders have already been sent.
Choices and loops
Choose a route based on the content, and go through lists of records one by one.
Start on an event, a schedule or a button
A Way is started by a Gate, a schedule, a button in the portal or another Way. That is how large flows are split into smaller parts.
Test before publishing
Run the draft against the test environment, and publish a locked version when it is ready.
A log for every run
See every step of every run, and where something went wrong.
Insight and data
See what happens, and where the data is kept
Insight into every run
Every run is logged step by step with status and time. Choose how much of the content is kept, for the whole Way and for each step, and omit or mask fields that must not be stored.
Data stored in the EU
Waysayer uses AWS regions within the EU for data storage and regional services, and Cloudflare for file storage, which is also in the EU. Some services, such as DNS, are delivered through global networks. Keys to your systems are stored encrypted.
See the sub-processorsPlans
Choose the plan that fits
The plan determines how many active Ways, Paths and Gates are included, how many Waypoints are included per month, and how long runs are kept. Choose an annual or a monthly agreement.
- Start
- Standard
- Pro
- Enterprise
Managed
We can also build and run the integration
Running it means monitoring, alerts and fixing faults in our setup. Status and logs are in the portal.
Not sure what you need?