
HR & Notifications Integrations
Connect recruitment workflows and process notifications with the steps teams complete in AMODIT. Use candidate data from eRecruiter to prepare and sign documents, and send important SMS updates to selected recipients.
Configured connections with TETA, enova365 and SAP HR exchange employee records, reference data, approved HR data, documents and process statuses with AMODIT in the directions required by the workflow.
Continue the process beyond recruitment
Recruitment work often continues after candidate data enters eRecruiter. HR teams still need to prepare documents, collect signatures, and keep candidates or employees informed as the process moves forward.
AMODIT adds structured workflow steps around that work. Candidate data can support document preparation and electronic signing, while SMS messages deliver important process information to selected recipients.
HR and notification options
Connect the recruitment system or notification channel required by the workflow.
eRecruiter
Extend eRecruiter recruitment workflows with additional steps in AMODIT. Candidate data can support document preparation and electronic signing with candidates.
SMS API
Send SMS messages from within an AMODIT workflow to deliver important process information to selected recipients. When SMS authentication is configured, one-time codes can also protect temporary access to a selected case.
How HR data moves between systems
Connections with TETA, enova365, SAP HR, and other HR platforms are designed around a defined workflow. Each implementation identifies which source data feeds AMODIT and which approved results return to the HR system.
Employee records into AMODIT
Employee records and reference data can feed an electronic personnel file, employee portal, or HR form in AMODIT. Synchronization reduces repeated entry of core employee data.
Organization and manager assignments
Organization structures, groups, and manager assignments can come from the agreed source and support task routing and access rules in AMODIT.
Documents in both directions
A document and its metadata can enter AMODIT for processing or signature. Once the workflow is complete, a signed document, approved data, or process status can return to the HR platform.
Absence requests and return information
An approved leave request or other absence information can move from AMODIT to the HR system. Absence, schedule, or status data can also feed the AMODIT workflow when the integration is designed in that direction.
eRecruiter and SMS API connect candidate data, document steps, signatures, and notifications with the AMODIT workflow that coordinates the work. HR teams keep the operational context in the process while candidates and other recipients receive the information intended for them.
Tell us how recruitment data should move into the next workflow steps and when SMS messages should be sent. We will discuss the appropriate AMODIT setup.
HR & Notifications FAQ
1Which HR and notification services work with AMODIT?
AMODIT supports recruitment workflows connected with eRecruiter and SMS notifications sent through SMS API.
2How does AMODIT work with eRecruiter?
AMODIT extends eRecruiter recruitment workflows with additional process steps. Candidate data can support document preparation and electronic signing with candidates.
3Can candidate documents be prepared and signed in the workflow?
Candidate data from eRecruiter can support AMODIT steps for preparing and electronically signing documents with candidates.
4What can SMS API send from AMODIT?
AMODIT sends SMS messages from within a workflow to deliver important process information to selected recipients.
5Can SMS codes protect temporary access?
Yes. When SMS authentication is configured, a one-time code can protect temporary access to a selected AMODIT case. See the Temporary Access page for the full setup.