HR integrations and API
Connect Skailer to the tools your people use and the systems you run
01One account per integration
Service users connect to the API without taking an employee seat, and you revoke each one on its own.02Fields the role allows
An API response holds only the fields the service user's role may read.03Signed events you can replay
Every webhook is signed, and each delivery can be inspected and sent again.04Leave decisions in Slack
Approvers approve or decline time off from the Slack notification.The problem
HR data shouldn't travel by export and personal login
A new hire's start date is in the HR system, their Slack profile shows nothing, and IT learns about them from an email. Payroll and BI get a spreadsheet every month. The script that syncs employees signs in as someone from HR, sees everything that person sees, and stops the day they leave. When an event doesn't arrive, nobody knows what was sent or how to send it again. Skailer changes that by connecting the everyday tools natively and giving every other system its own scoped account, a documented API and signed events with a delivery history.
Work tools
Keep Slack profiles and Google accounts in step with the HR record
Connect Slack once and Skailer keeps profiles aligned: the photo comes from Slack, and the name, start date, work location, job title and division go to Slack. Each employee's Slack contact appears on their Skailer profile and opens a direct message. Approvers act on time off from the Slack notification, and news posts can go to a Slack channel. Google Workspace accounts are created and deleted as steps of onboarding and offboarding flows.
01Profile sync with Slack
Photo from Slack; name, start date, location, job title and division to Slack.02Slack contact on the profile
Name, handle and avatar, with a link to a direct message.03Time off from Slack
Approve or decline from the notification.04Notifications and news
Personal notifications in Slack, news posts in a Slack channel.05Google Workspace accounts
Create or delete a user as a flow step; the invitation carries the new login.
Email and calendar
Email candidates and book interviews from the tools you already use
Recruiters connect their own Gmail or Outlook account and send candidate emails from their own address. Replies land in the candidate's history in Skailer. Google Calendar connects company-wide through a service account: interviews and events are scheduled with availability checks and Google Meet links, and approved vacation can appear as Out of Office in the employee's calendar.
01Gmail and Outlook
Personal connections, several accounts per person, OAuth with no password stored.02Custom SMTP
Send through your own mail server.03Google Calendar
Interviews and events, availability, Google Meet links.04Out of Office from leave
Approved vacation blocks the calendar and declines new invitations.
Public API
Give each system its own scoped account instead of someone's login
The public REST API accepts only tokens that belong to a service user, a non-human account that doesn't take an employee seat. A browser session or an employee's token is refused. Each service user gets a role, and responses contain only the fields that role may read. Tokens have a lifetime you choose and are shown once.
01Employees
Search with up to 500 records per page, including employment, compensation lines, additional compensation, custom tables, time off and termination.02Custom data
The list of custom fields with their types, and custom table rows with full history on request.03Documents
Folders, search, upload, download, rename and delete, under folder rules.04Calendars and leave
Holiday calendars and dates, and who is on leave for up to 180 days per request.05Audit log
Search who changed what, with its own permission.
Webhooks
Tell your systems the moment something changes
A webhook sends a Skailer event to your endpoint when it happens: a hire, a termination, a position or compensation change, an approved leave request, a finished flow step, a candidate moving stage. Employee events arrive on the date the change takes effect. Every request is signed with HMAC-SHA256, and each delivery keeps its request and response, so a failed one can be fixed and sent again.
0126 event types
Employees and time off, flow results, candidates and jobs.02Signed requests
X-Webhook-Signature with a secret you can rotate.03Delivery history
Status, attempt, request and response for every delivery.04Redeliver and test
Resend a failed event, or send a test before going live.05Notifications to any messenger
Forward employees' Skailer notifications to Teams, Telegram or another messenger through your bot.Import and migration
Move your data in from files and from the system you're leaving
The import wizard takes CSV and XLSX files with example templates, matches your columns to Skailer fields and shows row-level errors in an import history. It covers people, employment, positions, compensation, custom tables and time off balances and history, and can create new records, update existing ones or both. Recruiters add candidates from LinkedIn and other sites with the browser extension.
01Eight data types
People, employment, position, compensation, additional compensation, custom tables, time off balances, time off history.02Three modes
Create and update, create only, update only.03Import history
Every run with row-level errors.04Browser extension
Import candidate profiles into the ATS.All integrations
Everything Skailer connects to today
| Integration | What it does | Who connects it |
|---|---|---|
| Slack | Profile sync, Slack contact on profiles, time off approvals, notifications, news to channels | Slack workspace owner and a Skailer admin |
| Google Workspace | Create and delete user accounts as flow steps | Admin |
| Google Calendar | Interviews and events, availability, Meet links, Out of Office for leave | Google Workspace super admin |
| Gmail | Candidate emails from your own address | Each user |
| Outlook | Candidate emails from your own address (email only) | Each user |
| Custom SMTP | Candidate emails through your mail server | Each user |
| Google sign-in | Sign in with Google, limited to your Workspace domains | Admin |
| Microsoft Entra ID | Sign in with a Microsoft work account from allowed tenants | Admin |
| MCP | Skailer data in Claude, ChatGPT, Cursor and VS Code | Each user |
| Browser extension | Import candidate profiles from LinkedIn and other sites | Recruiters |
| Public REST API | Employees, custom data, documents, calendars, leave, audit log | Admin, through service users |
| Webhooks | Events to your endpoint, signed, with delivery history | Admin |
| Flows HTTP request | Send flow data to any public endpoint, signed | Admin or flow owner |
One HR platform
Integrations run on the same roles and flows as the rest of Skailer
Service users get their access from roles built the same way as employee roles. Flows decide when something should reach another system, and webhooks and HTTP requests carry it there. People who work in AI clients connect through MCP with their own permissions.
What integrations and API does Skailer have?
Tokens and signatures
Know what every integration can reach, and prove where each event came from
Each API integration has its own service user and role, so you can see and change its access in one place and delete it without touching an employee. Tokens are shown once and expire when you decide. Service user tokens work only with the public API; the Skailer web app refuses them. Webhook requests carry an HMAC-SHA256 signature, endpoints must be public addresses, and a secret can be rotated at once. Email integrations use OAuth, and Skailer doesn't store the mailbox password.
Skailer vs. the alternativesHR suites with a marketplace offer the most prebuilt connectors, including payroll and benefits, and suit companies that want to click integrations together. General automation platforms connect almost anything, with their own logs and pricing. Skailer covers the everyday tools natively and gives your team an API and events built for HR data.
Three ways to connect an HR system to the rest of your stack
| Capability | HR suite with a marketplace | General automation platform | Skailer |
|---|---|---|---|
| Prebuilt connectors | Many, including payroll and benefits | Thousands of apps | Slack, Google Workspace, Google Calendar, Gmail, Outlook, Entra ID, MCP |
| How integrations sign in | Varies by vendor | A connected user account | Service users with their own roles |
| Field-level API access | Varies by vendor | Whatever the account sees | Only fields the role allows |
| Events | Varies by vendor | Polling or app triggers | 26 signed webhook events with delivery history |
| Best fit | Teams that want ready-made payroll and benefits links | Many small, non-HR automations | Teams with an IT or ops owner who want scoped, auditable connections |
How it works
How to connect Skailer to your stack
01Connect the work tools
In Settings → Integrations, connect Slack, Google Calendar and Google Workspace. People connect Gmail or Outlook in their account settings.02Create a service user
In Settings → Service users, add one per integration and give it a role with only the fields and features it needs.03Issue a token or add a webhook
Create a token with a lifetime for API calls, or point a webhook at your endpoint and store its signing secret.04Watch it run
Check webhook delivery history, redeliver failed events, and revoke a token or service user when an integration retires.Questions about Skailer integrations and API
Which integrations does Skailer have?
Slack, Google Workspace, Google Calendar, Gmail, Outlook email, Google and Microsoft Entra ID sign-in, MCP for AI clients and a browser extension for recruiting. Other systems connect through the public API, webhooks and the HTTP request action in Flows.