HollyHR maintains the route
The public Make app, Google sign-in, configured Microsoft sign-in, one-way calendars and organisation export.
INTEGRATIONS useful routes, named honestly
Start with the job, not the logo wall.
Sign in with Google, or a Microsoft work or school account where configured. Put approved time away in a calendar. Keep a Sheet or team digest current. Build one narrower connection when the job genuinely needs it.
Public Make app · every route names its operator and support boundary
Shipped connections separated from recipes Native apps never implied by a logo People-data scope stays part of the decision
THE DIRECT ANSWER
What does HollyHR actually connect to?
HollyHR has a public Make app, supported sign-in, a one-way away calendar, maintained recipes, governed developer access and reviewed payroll hand-offs. It has no directory sync or two-way payroll connection.
We document the build
You own the key, schedule, runtime, destination and support.
A person controls the transfer
HollyHR prepares a pack; an operator checks, adapts and transfers it.
No native app is implied
No marketplace install, provisioning or two-way sync unless stated.
BUILD THE SMALLEST USEFUL CONNECTION
A route for the job. A control for the risk.
REST reads and signed webhooks are on every plan. Standard and above includes governed writes with explicitly selected scopes.
- Organisation-scoped, expiring and revocable keys
- Documented event families, not every UI change
- MCP changes keep explicit scopes and confirmation
SIGN-IN + CALENDAR
Useful in Google and Microsoft. Still not a directory connector.
Google sign-in is available on HollyHR's supported app host. Microsoft work or school sign-in is available where the deployment is configured for it. The same one-way away-calendar subscription works with Google Calendar and Outlook.
HollyHR does not provision users, sync either directory, write events back or turn a calendar subscription into permission to read private absence reasons.
See the Who's Away privacy boundaryMAINTAINED RECIPES
A recipe can be useful without pretending it is a native app.
The Google Sheets example is a read-only Apps Script sync. The Slack example is a scheduled presence-only digest using a Slack incoming webhook. Both run outside HollyHR, under your API key, schedule and destination permissions.
Signed HollyHR webhooks cover documented read-event families on every plan, with ten active endpoints and durable recovery per organisation. Useupdated_since polling for independent reconciliation.
REVIEWED PAYROLL HAND-OFF
Prepare the pack. Keep the pay run with the payroll operator.
A System Admin can generate an audited Xero Payroll UK readiness pack and upload template. Sage uses HollyHR's generic payroll-readiness export. Neither route sends data to the provider.
The operator reconciles identifiers, checks warnings, completes payroll-only values and uploads the shaped Xero template. For Sage, they adapt or re-key the generic export to the workflow in use. There is no OAuth connection, pay-run push, payslip return or two-way sync.
Review the payroll export contractCURRENT CONNECTION DIRECTORY
Four routes. Four different ownership models.
Choose by the job and the support boundary, not by how recognisable the logo is.
SIGN-IN + CALENDAR
Use Google or configured Microsoft sign-in. Put time away where planning happens.
- GoogleSign-in on supported hosts + one-way iCalAVAILABLE
- MicrosoftConfigured work/school sign-in + one-way iCalAVAILABLE
Keep a useful digest or planning sheet current.
- Google SheetsRead-only Apps Script recipeRECIPE
- SlackCustomer-hosted presence-only digestRECIPE
Build one clear job with the access it needs.
- MakeSeven approved people, time-off and API modulesAVAILABLE
- REST APIApproved reads on every planBETA
- Signed webhooksBounded read-event families on every planAVAILABLE
- Hosted MCPScoped reads and governed writesAVAILABLE
Prepare a reviewed pack without pretending payroll is synced.
- Xero Payroll UKReadiness pack + upload templateHAND-OFF
- SageGeneric reviewed manual exportHAND-OFF
Guides:Slack,Google Workspace,Microsoft 365,Xero,Sage,Zapier,Make,Stripe
THE NATIVE-INTEGRATION TEST
A logo is not an authentication flow, failure path or support owner.
HollyHR calls something native only when it owns the connection, documents its behaviour and has a tested way to recover when it fails. A maintained recipe or reviewed export can still be the better small-team answer, provided everybody knows who operates it.
Not shipped today
- Google Workspace or Microsoft directory sync
- Native Slack or Zapier marketplace app
- Automated Xero or Sage payroll sync
- Customer Stripe payments connected to HR
Stripe powers HollyHR billing. It is infrastructure, not a customer integration.
STRAIGHT ANSWERS
Questions worth asking before any people data moves.
These answers describe what is available now, not a roadmap promise.
What integrations does HollyHR support today?
HollyHR has an approved public Make app with seven people, time-off and API modules. Other routes include supported sign-in, a one-way away calendar, exports, scoped API access, bounded signed webhooks on every plan and reviewed payroll hand-offs.
Does HollyHR sync Google Workspace or Microsoft 365 directories?
No. These are sign-in and one-way calendar routes, not directory connectors. HollyHR does not provision users, provide SCIM or Entra sync, or write to calendars.
Is there a native HollyHR Slack app?
No. The maintained Slack recipe is a customer-hosted scheduled job. It reads safe people and approved time-off data, then posts a presence-only digest through Slack's incoming webhook. HollyHR provides no app, bot or marketplace install.
Does HollyHR integrate directly with Xero or Sage payroll?
No API sync. A System Admin can generate an audited Xero Payroll UK pack and upload template. For Sage, the generic export is a reviewed source an operator adapts or re-keys. HollyHR neither pushes pay runs nor returns payslips.
Which plans include API access and webhooks?
REST and MCP reads plus signed webhooks are on every plan. Standard and above includes governed writes. System Admins select scopes on expiring keys after fresh MFA.
How are MCP changes controlled?
Existing credentials never gain write scopes automatically. A System Admin selects every scope, the host must support confirmation, and HollyHR keeps an independent emergency switch for MCP writes.
BRING US ONE USEFUL JOB
Tell us what needs to connect. We'll tell you the honest route.
Start free with the workflow in mind, or send the exact platform and data question. If the connection is missing, we will say so.