WaysayerWaysayer 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.
The plans below contain the building blocks: Paths connect to the systems, Ways do the work, and Gates receive what comes in from outside.
Not sure what you need?
Tell us what you want to connect- 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 Paths, Ways and Gates. The names recur in the plans below, in the portal and in the platform limits.
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.
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.
Prices
Plans and prices
All prices exclude VAT.
Start
For integrations between a few systems.
690NOK/month
- 2 active Ways and 6 Paths
- 2 Gates for webhooks and calls
- Start Ways from Gates or on a schedule, as often as every 30 min
Standard
For several integrations and higher volume.
1 290NOK/month
- 15 active Ways and 30 Paths
- 10 Gates for webhooks and calls
- Start Ways from Gates or on a schedule, as often as every 5 min
Pro
For many integrations and high volume.
2 990NOK/month
- 40 active Ways and 75 Paths
- 25 Gates for webhooks and calls
- Start Ways from Gates or on a schedule, as often as every minute
Enterprise
For large volumes and custom limits.
Price by agreement
- Volume as needed
- mTLS and own domain by agreement
- Custom limits by agreement
Swipe sideways to see all plans.
| Start | Standard | Pro | |
|---|---|---|---|
| Waypoints | |||
| Included per month | 5 000 | 25 000 | 100 000 |
| Integrations: Ways and Paths | |||
| Active Ways | 2 | 15 | 40 |
| Active Paths, test and production | 6 | 30 | 75 |
| Schedules, shortest interval | Every 30 min | Every 5 min | Every minute |
| Connect to a wide range of APIs | |||
| Test before publishing | |||
| Locked version on publishing | |||
| Gates (incoming webhooks and calls) | |||
| Gates | 2 | 10 | 25 |
| Authenticated endpoints: API key, Basic, Bearer, HMAC | |||
| Start a Way from a Gate | |||
| Advanced features | Contact us | Contact us | Contact us |
| Logging and run history | |||
| What runs store | Steps and status, content on failure | + selected fields | + extract of all steps |
| Omit and mask fields | |||
| Searchable references | |||
| Run history | 30 days | 60 days | 90 days |
| Email alert on failure | |||
| Lookup store | |||
| Tables | 2 | 25 | 100 |
| Rows | 5 000 | 200 000 | 500 000 |
| Writes per month | 10 000 | 200 000 | 500 000 |
| Access | |||
| Users | 1 | 10 | 25 |
| Data stored in the EU | |||
| Support | |||
| Target response time for enquiries | 24 working hours | 16 working hours | 8 working hours |
- Active Paths are the connections in use; test and production both count. Active Ways are Ways started from outside: by a Gate, a schedule or a button. Ways started only by another Way, drafts and Ways that are switched off do not count.
- The lookup store is simple tables for mappings and reference values. Rows are kept until they are deleted, independently of the run history. More advanced data features will come as separate add-ons.
- General limits, such as calls per second per Gate, are listed in the platform limits.
- The plans were last updated on 11 October 2026. The terms take precedence over this page.
- This page is a translation provided for convenience. Order Forms refer to the Norwegian version, which prevails if the two differ.
More Waypoints
Swipe sideways to see the whole table.
| Plan | Waypoints | Recurring add-on, per month | Top-up, this month only | When the next plan pays off |
|---|---|---|---|---|
| Start | 2 500 | 300 NOK | 360 NOK | From 2 recurring add-ons, Standard pays off. |
| Standard | 10 000 | 500 NOK | 600 NOK | From 4 recurring add-ons, Pro pays off. |
| Pro | 25 000 | 1 000 NOK | 1 200 NOK | With consistently higher use, we agree the volume. |
A recurring add-on gives more Waypoints every month for the rest of the agreement period and renews with the plan. On a monthly agreement it costs the same as a top-up. A top-up applies only to the month it is bought in, and is used after the included Waypoints.
Add-ons on Standard and Pro
- 5 more active Ways290 NOK/month
- Lookup store: 50 000 more rows49 NOK/month
- Lookup store: 100 000 more writes per month49 NOK/month
Add-ons follow the agreement period. If they are added mid-period, they apply for the rest of the period and renew with the plan.
Details
What the plans contain
What a Way can do, how Gates receive calls, what runs store and how usage is measured.
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.
Gates
Gates: let other systems start the integrations
A Gate receives webhooks and API calls from other systems. Each Gate has its own address, can check who is sending, and starts the right Way. Outgoing webhooks are sent with a Path. Runs started by a Gate are counted in Waypoints.
Authentication in every plan
- API key, in the standard field or a field with a name of your choice
- Basic
- Bearer token
- HMAC signature, the way many systems sign webhooks
Advanced features
These are not yet available as a standard setup. Get in touch and we will tell you what it costs and how we set it up.
mTLS
Client certificates for systems that require mutual TLS.
Own domain
Gates on your own domain instead of our address.
IP restriction
Accept calls only from specific addresses.
OAuth client credentials
Machine-to-machine access with dedicated clients and short-lived tokens.
One Gate for many senders
A separate address for each sender under the same Gate.
Delivery through a queue
Accept quickly and process at a steady pace through a dedicated queue.
Logging
Decide what the runs store
Every run is logged step by step. Choose how much of the content is kept, for the whole Way and for each step. The plan determines which levels are available.
How much is stored
Minimal
That the run happened, and how it ended.
Steps and status
Every step with its status and time. Content is stored only when a step fails.
Selected fields
Only selected fields from selected steps.
Extract of all steps
A limited extract of what each step received and passed on: long texts are shortened and large lists are summarised.
Runs are kept for 30, 60 or 90 days, depending on the plan.
Per field
Omit
Fields that must never be stored, for example a national identity number.
Mask
Fields shown without their value, so it is clear they were there.
Searchable reference
Fields stored as searchable references, to find a run again by order number or customer number.
- Data classification Coming
Mark fields as personal data or sensitive data, and let the mark control masking, how long they are stored and who can see them.
Waypoints
How we measure usage
Everything Waysayer runs is measured in Waypoints, including the time spent waiting for other systems to respond. Each operation uses at least 0.1 Waypoint, longer operations use 0.1 Waypoint per started second, and heavier operations count with a weight that is listed in the platform limits or stated when the component is configured. Waypoints are a measure of work, not a fixed unit of time.
How an integration is built affects usage: work done in several stages counts at each stage. We are happy to help choose a setup that uses little.
Included Waypoints apply to the month and do not carry over. More can be bought as a recurring add-on every month or as a top-up for the current month.
The definition and the limits are set out in the platform limits.
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.
The price is a fixed setup fee and a monthly price per Way based on volume. Changes after start-up are agreed and invoiced by time spent or at a fixed price.
Questions
Questions and answers
What happens if we use more than the plan includes?
Alerts are sent at 80% and 100%. Choose whether, and how many, top-ups can be added automatically, or whether new runs should stop when the quota is used up. Usage is recorded continuously but not in real time, so use just before a limit takes effect can go slightly over the quota. If stop is chosen, we do not invoice such usage, unless it puts an unreasonable load on the platform or breaches the agreement. If top-ups are chosen, they are used after the included quota, and only usage beyond the top-ups can be invoiced at the current price for additional volume, as section 7 of the Customer Terms sets out. The number of Paths, Ways and Gates follows the plan and is not increased automatically. If more are needed, the answer is a larger plan, or more active Ways as an add-on on Standard and Pro.
What is the difference between a recurring add-on and a top-up?
A recurring add-on gives more Waypoints every month, at the price for the chosen agreement period. If it is added mid-period, it applies for the rest of the period and renews with the plan. A top-up applies only to the month it is bought in, and costs the same as a recurring add-on on a monthly agreement. Included Waypoints are used first.
Can we change plan?
Yes. A larger plan applies from the same day, with a new monthly quota from that day. What has been paid for the rest of the period on the old plan is deducted. A change to a smaller plan takes effect at renewal.
How do we cancel?
An annual agreement renews for twelve new months unless it is terminated in writing no later than 30 days before it expires. A monthly agreement can be terminated in writing at any time, with effect from the end of the month.
Do test environments count?
A Path for test counts as an active Path, just like one for production, and the plans have room for both for each system. Test runs of drafts do not count as active Ways, but use Waypoints like other runs.
Where is the 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. See the sub-processors and what each of them does.
Contact
Get in touch
Tell us what you are working on and what you need help with. We reply within one business day.