Dyflexis REST API Webhooks Rota to payroll

Custom Dyflexis integration

Dyflexis is workforce scheduling software in which organisations build rotas, collect availability and record hours worked. Those hours need to reach the payroll system, till revenue belongs next to staffing levels, and new employees should come from the HR system. Appfront builds the integration with the Dyflexis API so that rota, hours, payroll and revenue line up.

What is a Dyflexis integration?

A Dyflexis integration connects the workforce scheduling in Dyflexis with the other systems in your organisation. Dyflexis offers a REST API with a public OpenAPI description, which its own documentation still describes as beta. Every organisation has its own environment, and the integration works with a key issued by Dyflexis. A Dyflexis administrator enables the scopes, meaning the parts the integration may use, for each integration. All dates and times are in the time zone of your own Dyflexis environment. With webhooks, Dyflexis sends a message itself when something changes, so the integration does not have to keep asking.

The integration is needed because a rota is only worth something when it connects to everything else. Hours worked, allowances and leave determine pay. New employees, contract hours and departments are held in the HR system. Till revenue or the number of bookings determines how many people are needed. Without an integration, hours are exported, checked in a spreadsheet and entered by hand in the payroll system, and every later correction goes the same way again.

We build it custom because every organisation has a different combination of systems around Dyflexis. The integration keeps employees and contracts in sync with the HR system, passes approved hours and allowances to your payroll software, pulls revenue from the till or booking system and sets it next to scheduled and worked hours. Changes arrive immediately via webhooks. Hours that don't add up, such as a shift without a clock-out or an allowance that doesn't fit the contract, end up in a list for the scheduler instead of in the payroll run. That way payroll administration only sees hours that have already been checked, and nobody has to correct anything afterwards.

Hours to payroll

No retyping.

Revenue next to staffing

Tills and bookings.

Instant

Changes via webhooks.

How we build your Dyflexis integration

We start with your scheduling and payroll: which systems are involved, how hours are approved, which allowances and collective agreement rules apply and which figures managers want to see side by side. Then, together with you, we request API access and the right scopes from Dyflexis. We build the step that takes the most time first, usually hours to payroll, and have your schedulers and payroll administrators check it alongside the current way of working for a period. HR, tills and reporting follow, and we maintain the integration when the API changes.

1
Mapping the process

Hours, allowances, systems.

2
Access and scopes

Key and permissions at Dyflexis.

3
First integration

Tested alongside the current process.

4
Go-live and maintenance

Go-live, monitoring and maintenance when things change.

What a Dyflexis integration actually does

The components below appear in almost every Dyflexis integration. Which ones you need depends on your payroll, HR and till systems.

Employees

Kept up to date from the HR system.

Hours and allowances

To the payroll software.

Revenue

Tills and bookings included.

Webhooks

Changes processed immediately.

Validation

Discrepancies for the scheduler.

Log

Every exchange logged.

Who we build a Dyflexis integration for

The integration is intended for organisations with many changing shifts, where hours, allowances and staffing have to add up again every week.

Hospitality

Shifts next to revenue.

Retail

Staffing per shop.

Events

Many flexible workers.

Leisure

Seasonal peaks.

Technology and integrations

This page is about integrating Dyflexis with your other systems. If you are considering custom scheduling instead of an off-the-shelf package, see replacing Dyflexis with a custom solution and building workforce scheduling software. For other scheduling packages there is the Bedrijfsrooster integration. On the payroll side, we integrate with Nmbrs, Loket and AFAS, among others.

Dyflexis REST API OpenAPI Webhooks Nmbrs Loket AFAS Point-of-sale system Reservation system Reporting Log

Why Appfront for your Dyflexis integration?

A payroll run with the wrong hours, a forgotten allowance or a new employee who cannot log in costs you trust with exactly the people who do the work. That is what we build on: approve hours once, pass them on automatically and see discrepancies before the payslip does.

Paid correctly

Approved hours, passed on straight away.

Less manual work

No exports or spreadsheets.

Control over costs

Staffing alongside revenue.

Security and privacy in a Dyflexis integration

Schedule and hours data is personal data, and leave or sickness can be sensitive. The integration requests only the scopes it needs, and passes on only the data the receiving system uses. The GDPR applies to every system in the chain.

The integration runs in a European data centre, with encrypted connections and storage. The Dyflexis API key is stored securely and is not visible to employees. Every exchange is logged with time and outcome, and we agree with you in advance who may manage the integration.

Frequently asked questions about a Dyflexis integration

Questions that schedulers and payroll administrators ask before integrating Dyflexis.

Yes. Dyflexis offers a REST API with an OpenAPI description and webhooks; the documentation still labels the API as beta. You arrange the key and the permitted components via Dyflexis.

The parts of the API that an integration is allowed to use. A Dyflexis administrator enables them per integration when the key is requested. We request only what the integration really needs.

Yes, that is usually the most important step. Approved hours and allowances go to your payroll software, and hours that do not add up first appear in a list for the scheduler.

Yes. The integration pulls revenue from your till or bookings from your reservation system, and places them alongside scheduled and worked hours, so you can see where staffing does and does not fit.

With webhooks, Dyflexis itself sends a message when something changes, for example an amended shift. The integration processes it immediately, instead of repeatedly asking whether there is anything new.

For organisations with many shifts and several systems around Dyflexis. If Dyflexis already offers a standard integration for your payroll system that does everything you need, we will recommend that first.

Integrating Dyflexis with payroll, HR and POS?

Tell us which systems around your scheduling are involved and where manual work currently sits. We will show you how an integration brings hours, payroll and revenue into line.

Edit content