HRIS API and integrations
Connect Skailer to the tools you run
HR software integrations with Slack, Google Workspace, Google Calendar, Gmail, Outlook and Entra ID, plus an API and signed webhooks for your systems.
HR data shouldn't travel by export and login
Slack shows nothing about a new hire, payroll and BI get a monthly spreadsheet, and the sync script signs in as someone from HR. When they leave, it stops.
Keep Slack and Google accounts in step with HR data
Connect Slack once: the photo comes from Slack, and name, start date, location, job title and division go to it. Approvers act on time off from the notification. Google Workspace accounts are created and deleted by flows.
Email candidates and book interviews from your tools
Recruiters connect their own Gmail or Outlook and email candidates from their own address; replies land in the profile. Google Calendar connects once: interviews get availability and Meet links, and leave shows as Out of Office.
Give each system its own account, not someone's login
The public REST API works only through service users: non-human accounts that don't take an employee seat. Each gets a role, responses hold only the fields that role may read, and tokens expire when you decide.
Tell your systems the moment something changes
A webhook sends an event to your endpoint when it happens: a hire, a termination, a pay change, approved leave, a finished flow step, a candidate moving stage. Each request is signed, and each delivery can be resent.
Move your data in from CSV and XLSX files
The import wizard takes CSV and XLSX files, matches your columns to Skailer fields and logs row-level errors. It covers people, employment, compensation, custom tables and time off, and can create, update or both.
Everything Skailer connects to today
| Integration | What it does | Who connects it |
|---|---|---|
| Slack | Profile sync, leave approvals, notifications, news | Slack owner and a Skailer admin |
| Google Workspace | Create and delete accounts in flows | Admin |
| Google Calendar | Interviews, 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 address, email only | Each user |
| Custom SMTP | Candidate emails through your mail server | Each user |
| Google sign-in | Sign-in limited to your Workspace domains | Admin |
| Microsoft Entra ID | Sign-in with work accounts from your tenants | Admin |
| MCP | Skailer data in Claude, ChatGPT, Cursor, VS Code | Each user |
| Browser extension | Candidate profiles from LinkedIn and other sites | Recruiters |
| Public REST API | Employees, custom data, documents, leave, audit | Admin, through service users |
| Webhooks | Signed events with a delivery history | Admin |
| Flows HTTP request | Signed flow data to your endpoint | Admin or flow owner |
Integrations run on the same roles and flows
Native integrations for the tools your people use; API and webhooks for the systems you run. Service users get roles like employees, and flows decide when data leaves.
What HRIS API and integrations does Skailer have?
Skailer integrates natively with Slack, Google Workspace, Google Calendar, Gmail, Outlook email and Microsoft Entra ID sign-in, and connects AI clients through MCP. Other systems use a public REST API and webhooks. The API accepts only service user tokens, whose roles decide which fields they read. Webhooks send signed events with a delivery history. Payroll connectors and an app marketplace aren't part of Skailer.
Know what each integration can reach
Each API integration has its own service user and role, deleted without touching an employee. Tokens expire when you decide, webhook secrets rotate, mailbox passwords aren't stored.
What the model shows for a 500-person company
DATA RECONCILIATION
ATS AND HRM SYNC
INTERVIEW SCHEDULING
Three ways to connect HR to the rest of your stack
HR suites with a marketplace offer the most prebuilt connectors; automation platforms connect almost anything. Skailer covers everyday tools and gives you an HR API.
| Capability | HR suite with marketplace | Automation platform | Skailer |
|---|---|---|---|
| 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 |
| Failed deliveries | Varies by vendor | In the platform's own logs | Request, response and redeliver |
| Revoking access | Varies by vendor | Disconnect the user account | Delete one service user |
| Best fit | Ready-made payroll links | Many small non-HR automations | IT-owned, scoped HR connections |
How to connect Skailer to your stack
See how teams use Skailer
Skailer integrations and API: questions
Which HR software integrations does Skailer have?
Slack, Google Workspace, Google Calendar, Gmail, Outlook email, custom SMTP, 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.
Does Skailer have a public HRIS API?
How do integrations authenticate?
Which events can webhooks send?
Does Skailer have an HRIS payroll integration?
Does Skailer sync with Outlook Calendar?
See how Skailer fits into your stack
Book a 30-minute demo with your IT lead, and we'll walk through the API, webhooks and your tools.