Custom Nostradamus integration development
Nostradamus is software for workforce scheduling and time tracking, with rosters, clocking, absence, leave and forecasts, used in hospitality, retail, theatres, leisure and logistics, among others. It has integrations with payroll systems, HR systems and tills. Appfront builds the connection with the systems that are not on that list, so hours, schedules and staffing costs no longer have to be transferred by hand.
What is a Nostradamus integration?
Nostradamus is workforce scheduling software. Planners create rosters, employees see their shifts in an app and clock in and out, hours are approved, and absence and leave are tracked. Nostradamus forecasts busyness and revenue, so the roster matches what is expected. It has integrations with payroll systems, HR systems, tills and event planning software, among others.
Whatever isn't covered by those standard integrations is often handled by hand. A chain wants staff costs from all its locations alongside revenue in its own reporting, and exports them location by location. The HR system knows different contracts from Nostradamus. And data from your own systems, such as reservations or production orders, doesn't find its way into the forecast on its own.
We build custom integrations because businesses differ: which payroll system, which till, which in-house systems, and which figures need to go where. The integration runs through the API that Nostradamus provides. What data it contains and under what conditions, we look at in the first step, together with you and with Nostradamus.
Hours in one place
Approved hours in your own systems.
Costs alongside revenue
Per location and department.
Via the API
Agreed with Nostradamus.
How we build your Nostradamus integration
We start with your organisation: which systems you use alongside Nostradamus, which data is currently handled by hand, who needs to see what, and whether your system is perhaps already among the standard integrations. Then we look with Nostradamus at what the API offers for your situation. We often start with approved hours and staff costs per location going into reporting, because that saves manual work straight away. Employees and contracts from a single source, and data for the forecasts, follow once the first integration is running well. After that, we maintain the integration when Nostradamus or your own systems change, and after every change we check that hours and costs still match the payroll system.
Systems, data and who needs to see what.
What Nostradamus offers for your situation.
Hours, costs and employees.
Go-live, monitoring, and maintenance when things change.
What a Nostradamus integration actually does
The components below come up in almost every Nostradamus integration. Which ones you need depends on your organisation and systems.
Hours
Approved, per shift.
Rota
Shifts per location.
Staff costs
Alongside revenue.
Employees
From a single source.
Forecast data
From your own systems.
Log
Every message recorded.
Who we build a Nostradamus integration for
The integration is intended for organisations that schedule with Nostradamus alongside systems that aren't included as standard. The more locations and employees you have, the more time it saves.
Hospitality and retail chains
Many locations. Costs are compared side by side.
Theatres and venues
Varying staffing levels. Planning per performance matters.
Leisure businesses
Seasonal work. Forecasting matters.
Software suppliers
A product for planners.
Technology and integrations
This page is about integrations with Nostradamus. If you use a different scheduling app, see our page on the Eitje integration; for payroll, our page on the Nmbrs integration; and for your own scheduling system, our page on workforce scheduling software. You can read about our approach on building software.
Why Appfront for your Nostradamus integration?
Hours exported location by location, and staff costs that are only set against revenue after the month has ended, cost a chain time and control. That's what we build on: hours in one place, costs alongside revenue, and an integration through the Nostradamus API.
No exports
Hours arrive automatically.
Managing costs
Alongside revenue.
Official route
Via the API.
Security and privacy in a Nostradamus integration
The integration processes data about employees, such as names, contracts, hours, leave and sometimes sickness absence. That is personal data, and sickness absence is sensitive. We use only the data that is needed, API access credentials are stored encrypted, and every message is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about a Nostradamus integration
Questions organisations ask before they get started.
Nostradamus is software for workforce scheduling and time tracking. Planners create schedules, employees see their shifts and clock in and out in an app, and sickness absence and leave are tracked. Nostradamus also produces forecasts of busyness and revenue, so that the schedule matches expected demand.
Yes, including payroll systems, HR systems, tills and event planning software. If your system is on that list and the integration does what you need, custom work isn't necessary, and we'll tell you so. A custom integration is for systems and reports that aren't covered.
Through the API that Nostradamus provides. In the first step, together with you and Nostradamus, we look at which data is available, how access is arranged and under what conditions. Only then do we build, so you don't get stuck on a route that doesn't exist.
Yes. Approved hours and costs from Nostradamus are combined with revenue from your till or accounting system, per location, per department and per day. That shows you where staffing is too expensive for the level of trade, and where more people were needed.
Often, yes. Bookings, ticket sales or production orders say something about how busy it will be, and can be passed to Nostradamus if the API allows it. In the first step we look at which data that is and how Nostradamus uses it.
The integration reports it and records what went wrong. The message is retried or queued for review, so no hours are lost or arrive twice in payroll.
For multi-site chains, for theatres and leisure businesses with fluctuating staffing, for production and logistics with shifts, and for software vendors who want to connect their product to Nostradamus. If you work with the standard integrations and don't miss anything, a custom integration is often not needed.
Nostradamus connected to your own systems?
Tell us which systems you use alongside Nostradamus and which data is currently transferred by hand. We'll show you which route is available and what the integration looks like.