Before you start
You need a Zapier account and a HollyHR System Admin to create the connection key. The public Beta app does not require an invitation. Triggers and searches work on every HollyHR plan; create actions need Standard and the relevant write permissions. Zapier's own plan and usage limits also apply.
Connect your workspace
- In HollyHR, open Integrations → Developer tools. Create a key named for this Zapier connection and select only the permissions your workflow needs. Complete verification if prompted.
- In Zapier, add a HollyHR step to your Zap. When asked for a connection, enter the workspace part of your HollyHR address: for acme.hollyhr.com, enter acme.
- Enter the dedicated API key in Zapier's connection form. Do not put it in a mapped field or Zap description.
- Choose the event and test with fictional records. Map only the fields needed by the next app, check the result and turn on the Zap.
Check the first result
- The six instant triggers cover new, updated and departing people, plus new, updated and cancelled time off. Departing Person runs when an employment end date is set or changed, not on the person's last day.
- For Create Person or Create Time Off, keep the Source record key stable for the same source record so retries do not create duplicates.
- Inspect Zap history if a run fails. Check the workspace, key permissions and plan before retrying; include the request ID when asking HollyHR for help, not employee records or the key.
Stop or replace the connection
Turn off Zaps that use the connection before removing it in Zapier. Revoke its dedicated key in HollyHR's Developer tools when it is no longer needed. If replacing a key, update and test every affected connection before revoking the old one. Revocation does not remove records already copied to another app.
Technical details
Use the developer guide for exact permissions, supported operations and detailed troubleshooting.