Integration · Payroll & HR

Connect Claude & ChatGPT to Emply

Ask your AI how many vacation days an employee has left, to register sick leave, or which applications came in this week in Emply. It can create, change, approve and reject absence, and read employees, departments, forms, documents, candidates, applications and job postings. HR questions get answered without searching through profiles.

Connect Emply free

Free plan, no credit card. Takes about a minute.

Try asking

“How many vacation days does Peter Holm have left?”
The AI finds Peter's employee ID and reads his absence allowance balances.
“Register sick leave for Jonas today.”
It looks up the leave type for sickness and creates an absence for Jonas for today.
“Does Anna have any absence requests waiting? Approve them.”
It lists Anna's pending absence requests and approves them. Anna may be notified.

What your AI can do

Employees and absence

Search employees, read balances and absences, and create, update, approve, reject or delete absence.

Recruiting

Search candidates and applications, list new applications, read application form answers and see job postings.

Organisation

Read departments, users, roles, holidays, forms, onboardings and documents on employee profiles.

“Which applications came in this week?”
It lists job applications created since the start of the week, optionally for one vacancy.
“Show Mette Larsen's answers on her application form.”
It finds the application and the form, then reads the answers she gave.
“Which jobs are posted on our career site right now?”
It lists the job postings on your default career site.

89 tools for Emply

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

approve_absenceVisible to othersApprove a pending absence request by `employee_absence_id`, with an optional `comment`. The employee may be notified.
create_absenceChanges dataRegister an absence for an employee with `employee_id`, `leave_type_id`, `from_date`, `to_date` and an optional `comment`. Use `from_date_part`/`to_date_part` (1 morning, 2 lunch, 3 evening) for half days.
create_addressChanges dataCreate a new address. API summary: Creates single location for department.
create_createChanges dataCreate a new create. API summary: Creates onboarding using form data.
create_departmentChanges dataCreate a new department. API summary: Creates single department.
create_department_addressChanges dataCreate a new address for a department. API summary: Creates single location for department.
create_employeeChanges dataCreate a new employee for a employee. Search employees first to avoid duplicates. API summary: Creates folder for an employee.
create_employee_documentChanges dataCreate a new document for a employee. API summary: Creates document for an employee.
create_job_createChanges dataCreate a new job create. API summary: Creates vacancy.
create_userChanges dataCreate a new user. Search users first to avoid duplicates. API summary: Creates single user.
delete_absenceDeletesPermanently delete an absence by `absence_id`. This cannot be undone.
delete_addressDeletesPermanently delete a address by address id. Destructive action; may require approval. API summary: Removes single location from department.
delete_applicationDeletesPermanently delete a application by application id. Destructive action; may require approval. API summary: Removes single application.
delete_candidateDeletesPermanently delete a candidate by candidate id. Destructive action; may require approval. API summary: Removes single candidate.
delete_departmentDeletesPermanently delete a department by department id. Destructive action; may require approval. API summary: Removes single department.
delete_department_addressDeletesPermanently delete a address by address id. Destructive action; may require approval. API summary: Removes single location from department.
delete_employeeDeletesPermanently delete a employee by employee id. Destructive action; may require approval. API summary: Removes single employee.
delete_export_entityDeletesPermanently delete a entity by entity id. Destructive action; may require approval. API summary: Deletes single exported entity.
delete_onboardingDeletesPermanently delete a onboarding by onboarding id. Destructive action; may require approval. API summary: Removes single onboarding.
delete_userDeletesPermanently delete a user by user id. Destructive action; may require approval. API summary: Removes single user.
delete_usersMoves moneyPermanently delete a user by custom id. Financial or irreversible action; may require approval. API summary: Removes single department.
get_absence_balancesGet an employee's absence allowance balances (e.g. remaining vacation days) by `employee_id`.
get_addressGet one address by address id. API summary: Retrieves single location of department.
get_application_export_jsonGet one export json for a application by export template id. API summary: Retrieves export JSON for application.
get_application_form_dataRead the answers an applicant gave on one application form by `application_id` and `form_id`.
get_candidateGet one candidate by date. Results are paginated. API summary: Retrieves candidates.
get_countryGet one country by country code. API summary: Retrieves single country.
get_currencyGet one currency by currency code. API summary: Retrieves single currency.
get_departmentGet one department by `department_id`, including its name and parent.
get_department_addressGet one address for a department by address id. API summary: Retrieves single location of department.
get_employeeGet one employee by date. Results are paginated. API summary: Retrieves employees.
get_employee_documentGet one document from an employee's profile by `employee_id` and `document_id`.
get_employee_export_jsonGet one export json for a employee by export template id. API summary: Retrieves export JSON for employee.
get_employee_form_dataRead the fields an employee has filled in on one form (e.g. personal or employment details) by `employee_id` and `form_id`.
get_entity_documentGet one document for a entity by document id. API summary: Returns single exported file.
get_exportGet one export by export id. API summary: Returns references to exported entities.
get_export_entityGet one entity for a export by entity id. API summary: Returns single exported entity.
get_form_dataGet one form data by form id. API summary: Retrieves form data for profile.
get_form_getGet one form by form id. API summary: Retrieves form definition.
get_job_createGet one job create by template id. API summary: Prefills vacancy with template data.
get_job_templateGet one job template by type. Results are paginated. API summary: Retrieves job templates.
get_job_template_getGet one job template by template id. API summary: Retrieves template definition.
get_journal_entryGet one journal entry by media id. Results are paginated. API summary: Retrieves all published postings from a specific media.
get_journal_entry_getGet one journal entry by job id. API summary: Retrieves a posting for a job from specific media.
get_journal_entry_stageGet one stage for a journal entry by stage. Results are paginated. API summary: Retrieves all postings from a specific media by stage.
get_languageGet one language by language key. API summary: Retrieves single language.
get_onboarding_form_dataGet one form data for a onboarding by form id. API summary: Retrieves form data for onboarding.
get_roleGet one role by role id. API summary: Retrieves single role.
get_userGet one Emply user by `user_id`.
list_addressesList addresses. API summary: Retrieves locations of department.
list_applications_sinceList job applications created since `date` (MM-dd-yyyy), optionally limited to one vacancy (`vacancy_id` or `job_id`).
list_countriesList countries. API summary: Retrieves countries.
list_currenciesList currencies. API summary: Retrieves currencies.
list_department_addressesList addresses for a department. API summary: Retrieves locations of department.
list_departmentsList departments. Filter with `active` (true only active, false only inactive); paginate with `take` and `offset`.
list_employee_absencesList all absences registered for one employee by `employee_id`.
list_employee_documentsList the documents stored on an employee's profile by `employee_id`.
list_employeesList employees for a employee. API summary: Returns accessible folders of an employee from the root.
list_folder_documentsList documents for a folder. API summary: Returns accessible employee's documents from particular folder.
list_formsList the forms defined for an `area` (1 candidate, 2 onboarding, 4 employee). Use a form ID to read an employee's, candidate's or onboarding's form data.
list_holidaysList the public holidays configured in Emply.
list_job_postingsList the job postings on your default career site. Paginate with `take` and `offset`.
list_languagesList languages. API summary: Retrieves languages.
list_leave_typesList the leave types (vacation, sickness etc.) with their IDs. Use a leave type ID when creating an absence.
list_mediaList media. Optional filters: take. Results are paginated. API summary: Retrieves all medias available from a customer.
list_pending_absence_requestsList an employee's absence requests that are waiting for approval, by `employee_id`.
list_rolesList the user roles in Emply with their IDs, for filtering users by role.
list_time_zonesList time zones. Optional filters: take. Results are paginated. API summary: Retrieves time zones.
list_usersList users. API summary: Retrieves single department.
list_users_2List users. API summary: Retrieves single user.
list_users_getList users. API summary: Retrieves single user.
reject_absenceVisible to othersReject a pending absence request by `employee_absence_id`, with an optional `comment`. The employee may be notified.
search_applicationsSearch job applications by applicant `first_name`, `last_name` or `email`, optionally limited to one vacancy (`vacancy_id` or `job_id`).
search_candidatesSearch candidates by `first_name`, `last_name` or `email`.
search_employeesSearch employees by `first_name`, `last_name`, `email` or `custom_id`, or by `created`/`updated` date (dd-mm-yyyy). Use this to find an employee's ID. Paginate with `take` and `offset`.
search_onboardingsSearch onboardings (new hires being onboarded) by `first_name`, `last_name` or `email`.
search_onboardings_by_dateSearch onboardings by date, form id or take. Use this to find existing onboardings before creating a new onboarding. Results are paginated. API summary: Retrieves onboardings.
search_usersSearch Emply users (people who log in, e.g. managers and HR staff) by name, `email`, `username`, `role_id` or `department_id`, and filter by `active`.
update_absenceChanges dataChange an existing absence by `absence_id`: `from_date`, `to_date`, `leave_type_id` and `comment` are all required.
update_addressesVisible to othersUpdate an existing address identified by custom id. Has effects visible outside this system. API summary: Updates single location of department.
update_application_form_dataChanges dataUpdate an existing form data identified by form id. API summary: Saves form data for application.
update_createChanges dataUpdate an existing create identified by vacancy id. API summary: Creates application using form data.
update_create_postChanges dataUpdate an existing create identified by form id. API summary: Creates employee using form data.
update_department_addressesVisible to othersUpdate an existing address identified by department id. Has effects visible outside this system. API summary: Updates single location of department.
update_departmentsVisible to othersUpdate an existing department identified by customer. Has effects visible outside this system. API summary: Updates single department.
update_employee_form_dataChanges dataUpdate an existing form data identified by form id. API summary: Saves form data for employee.
update_form_dataChanges dataUpdate an existing form data identified by form id. API summary: Saves form data for profile.
update_onboarding_form_dataChanges dataUpdate an existing form data identified by form id. API summary: Saves form data for onboarding.
update_userChanges dataUpdate an existing user identified by user id. API summary: Updates single user.

Set up in three steps

1
Pick the app
Create a free HeyMyApps account and choose Emply from the app list.
2
Paste your key
Paste your Emply API key and your Emply platform name. As an Emply administrator go to Settings > Integrations > API and click 'New API key'. Enter a title, save, select the role or roles that may use the key, activate it and save again. Then copy the API key.
3
Add the link to your AI
You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:
1. Click your name, then Settings › Connectors › Add custom connector.
2. Paste your link as the Remote MCP server URL.
3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Emply?

The AI can search and read employees, absences, absence balances, pending absence requests, departments, users, roles, holidays, forms, form data and employee documents. On the recruiting side it can search candidates, applications and onboardings and list job postings. It can create and update absences, approve or reject absence requests and delete an absence.

Does the AI see my Emply credentials?

No. Your Emply credentials are encrypted at rest and never shown to the AI. After you save them, they are not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start read-only. Approving or rejecting absence may notify the employee, and deleting an absence is permanent. These can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT go to Settings › Apps & Connectors › Advanced and turn on Developer mode, then add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

HeyMyApps has a free plan with no credit card required. Paid plans bill per completed task. You also need your own Emply account.

Which Emply role should the API key have?

When you create the key in Emply, you select the role or roles that may use it. Pick a role with access only to the areas you want the AI to reach, such as employees and absence or recruiting. On top of that, you choose which tools are switched on in HeyMyApps.