Skip to main content

Supported Integration Systems and Standard Fields

Which HR systems Appical supports as standard, the standard field set, and standard processing options.

Overview

Appical supports integrations with a number of HR systems. This article explains which systems are supported as standard, which fields are used, and how data is typically processed.


For admins

Appical has existing experience connecting to the following systems, which means an integration with any of them can typically be set up as standard:

  • AFAS

  • SuccessFactors

  • HR2Day

  • SmartRecruiters

  • YouForce

  • Connexys

  • Workday

  • NMBRS

  • Emply

  • Mulesoft

  • Tellent (Recruitee)

  • Daywize

  • ADP

If your organization uses one of these systems, or transfers data via a file (for example to an sFTP server, MS Blob storage, or an S3 bucket), your integration will most likely follow the standard process described in Standard vs Custom Integrations.

At a high level, a standard integration can be configured to:

  • Automatically invite new employees and update existing ones.

  • Give managers and buddies access to a new hire's profile (Manager Toolkit).

  • Assign employees to groups and tags in Appical, for example based on country, office, or department.

  • Convert a private email address to a business email address once someone starts.

  • Automatically archive access after a set period, and anonymize data after a further period.

Your Appical contact will confirm during scoping which of these options apply to your setup.


For IT and technical teams

This section lists the technical field set and processing options used in a standard integration.

Standard fields

Field

Description

Notes

Remote ID

Unique identifier for the employee

Last name

Surname

Last name prefix

Prefix of the surname

First name

Known first name

Can also be a nickname, if that is the known field

Email

Private email address of the employee

New email

Business email address of the employee

First day

Hire date of the employee

Deactivation date

Termination date, if the employee leaves before the default deactivation date

Manager remote ID

Unique identifier of the manager

Needed if Manager Toolkit is used

Manager last name

Surname of the manager

Needed if Manager Toolkit is used

Manager last name prefix

Prefix of the manager's surname

Needed if Manager Toolkit is used

Manager first name

Known first name of the manager

Needed if Manager Toolkit is used

Manager email

Email address of the manager

Needed if Manager Toolkit is used

Course ID

Determines which course a user receives, based on group, country, brand, etc.

Country tag

Used for tagging

Country or region

Office tag

Used for tagging

City or office location

Role tag

Used for tagging

Business unit, department, or job title

Technical notes:

  • All fields should ideally be available from a single endpoint. Using multiple endpoints is possible, but adds complexity and processing time.

  • Data shared with Appical should be limited to what is needed, for example only new employees after a specific date. Appical does not need access to the full dataset.

  • Any available field can be used for tagging.

  • Multiple manager types (for example, line manager, HR manager, buddy) can each be assigned a different preset, provided their ID, name, and email are available in separate fields.

Standard processing options

The following can be configured as part of a standard integration:

  • Number of days an employee (viewer) can access Appical before the account is archived (default: 365 days, configurable).

  • The integration runs once per day, at a configurable time.

  • New hire data is anonymized 1.5 years after archiving (configurable).

  • Number of days before an employee's first working day that they receive their invitation email (configurable).

  • Access to Appical can be filtered based on employment type, if required.

  • The private email address can be converted to the business email address on the employee's first working day. Note: if email is used as the unique identifier, this requires attention to duplicate handling.

  • Employee data updates (such as first day, location, department, or manager) can be synced to Appical automatically, with the exception of the unique identifier.

  • Employees can be assigned to one or more groups in Appical.

  • Employees can be assigned one or more tags in Appical.

  • Managers and buddies can be created in Appical and given access to their employee's profile (Manager Toolkit), with a defined preset per manager type.


Related articles

  • Standard vs Custom Integrations

  • Making a Request for an Integration

  • The Mapping Document Explained

  • The Integration Process, Step by Step


👉 Let us know if this article answered your question by using the buttons below. If not, get in touch with our Support Channel for more information.

Did this answer your question?