Xurrent (4me) integrations

Xurrent (4me) integrations

→X4

AFAS Profit → Xurrent (4me)

AFAS to Xurrent integration: employees, employers and onboarding requests from AFAS Profit in Xurrent (4me)

→X4

Nmbrs → Xurrent (4me)

Nmbrs to Xurrent integration: people per entity and requests from a template in Xurrent (4me)

→X4

Workday → Xurrent (4me)

Workday to Xurrent integration: people, organisations and onboarding requests in Xurrent (4me)

→X4

Visma Raet YouForce → Xurrent (4me)

YouForce to Xurrent integration: people, departments with their manager and requests from a template

→X4

HiBob → Xurrent (4me)

HiBob to Xurrent integration: people per site and requests for joiners and leavers

→X4

Personio → Xurrent (4me)

Personio to Xurrent integration: people per legal entity and requests for joiners and leavers

Systems you can connect Xurrent (4me) with

How KoppelHet connects to Xurrent (4me)

Xurrent REST API with the /people endpoint for people, with references to organization, site and manager.

Authentication: Personal access token of OAuth 2.0 (client credentials voor machine-to-machine), plus de header X-Xurrent-Account

Objects we connect

• People with employeeID, job_title and primary_email
• Organisations and sites
• Manager relationship and disabled status
• Requests with requested_for, template and desired_completion_at

What a Xurrent (4me) integration does

• AFAS Profit, Visma Raet YouForce → to Xurrent (4me)

  People with employee number from HR

  New employees from AFAS or YouForce become a Xurrent person with employeeID, job title, organisation and site.

  AFAS Profit → Xurrent (4me) integrationVisma Raet YouForce → Xurrent (4me) integrationHR to ITSM

• AFAS Profit, HiBob → to Xurrent (4me)

  Manager relationship for approvals

  The supervisor from HR becomes the person's manager, so approvals for access and hardware reach the right person.

  AFAS Profit → Xurrent (4me) integrationHiBob → Xurrent (4me) integrationHR to ITSM

• AFAS Profit, Visma Raet YouForce → to Xurrent (4me)

  Onboarding request from a request template

  A hire creates a request through POST /requests from the onboarding template, with the new employee as requested_for and the start date as desired_completion_at. The template decides team and follow-up tasks.

  AFAS Profit → Xurrent (4me) integrationVisma Raet YouForce → Xurrent (4me) integrationHR to ITSM

• AFAS Profit, Visma Raet YouForce → to Xurrent (4me)

  Disable on leaving

  After the last working day the integration sets disabled to true. The request history is kept.

  AFAS Profit → Xurrent (4me) integrationVisma Raet YouForce → Xurrent (4me) integrationHR to ITSM

What to watch for

• A token never gets more rights than the roles of the person who created it. Use a separate integration account with only the needed roles.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• HR to ITSM

Topics that involve Xurrent (4me)

• People and departments
• Onboarding and offboarding tickets
• Multiple employers and locations