piloton requestAPI / webhooksexport as foundation

ProSafetyMatch works alongside existing systems.

ProSafetyMatch does not need to replace existing planning or systems. Integrations are configured per organisation where they are needed.

Export remains the fixed foundation. Integrations are optional and aligned to scope, licence and technical feasibility.

Planning stays where it belongs; ProSafetyMatch keeps the assignment context together for the two involved parties per assignment.

Integrations are phased in and configured on request per organisation. This page describes scope and compatibility; it does not activate an integration in your environment.

Integrations V1 supports scoped connectors and dossierlinkback; runs are typically batch- or job-driven and not real-time by default. Enterprise integrations are on request and implementation-led (deeper/bidirectional configuration where configured). Availability also depends on tenant configuration and environment flags — not plug-and-play with every system.

Book an intro call How does it work?

Integrations Pack Add-on: V1 EUR 199/mo per organisation, Enterprise EUR 399/mo per organisation. Setup: typically EUR 750 per active integration.

core without integrationsIntegrations Pack required for integrations

System status

The system names below refer to compatibility levels in the platform. They do not imply partnership, certification or default activation for your organisation.

Beeple

Platform · Bridge

Secure-IT

Platform · Bridge

Dyflexis

Platform · Connector

Shiftbase

Platform · Bridge linkback

AFAS

Connector Lite · Pilot only

Nmbrs

Bridge/Export Lite · Pilot only

Nétive

Connector Lite · Pilot only

Bidirectional

Enterprise scope

Bridge-koppelingen · bridge compatible

Bridge compatible means limited status, export or dossier feedback without deep system mirroring.

Beeple: status via bridge connector. Beeple can be a Bridge target within a configured pilot or organisation context; this is not a partner, certification or default-activation claim.
Secure-IT: export package via connector.
Nmbrs: status/export via Bridge/Export Lite; no deep payroll sync in the current scope.
Dossier feedback: status + dossier/export links. Verification links require Trust Pack and are activated per integration configuration.

Connector-koppelingen · connector compatible

Connector compatible means assignment import plus agreed status/export feedback per tenant mapping.

Dyflexis V1: fetch assignments and import into ProSafetyMatch.
AFAS: Connector Lite foundation for assignment import and status/dossier/export feedback per tenant mapping.
Nétive: Connector Lite foundation for engagement records, dossier status and export links per tenant mapping.
Minimal feedback: status, times, dossier link.
Feedback via notes uses conflict-free block replacement, so notes do not get polluted.
No full WFM field mirroring in V1.

Bridge-koppelingen (Shiftbase)

Shiftbase V1: dossier/export feedback via connector batch.
Bridge-compatible: minimal feedback with dossier/export link without replacing your existing workflow.
No real-time direct connection and no guaranteed sync speed in V1.
Bidirectional requires Enterprise scoping per system (not a V1 default).

What is not in V1

No full bidirectional synchronisation.
Bidirectional can be assessed and scoped per Enterprise setup, but is not a default for all systems.
No extensive field mapping to all WFM/HR fields.
No certified AFAS, Nmbrs or Nétive partner claim; activation is per pilot/configuration.
No deep payroll sync or automatic payroll processing.
No real-time direct Shiftbase connection.
No guaranteed sync speed for Bridge connections.

Pricing information

View the current pricing structure for plans, add-ons and implementation on the "What does it cost" page.

View pricing →

Brands and trade names: All product and system names are the property of their respective owners and are used only to describe compatibility and possible connection levels. ProSafetyMatch is not affiliated with these providers and does not imply partnership, certification, approval, endorsement or an existing technical integration unless explicitly stated.

Compatibility: 'Compatible' means: functioning in accordance with the stated compatibility level (Bridge/Connector).