> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-hris.md). # HRIS Sync employee data from your HRIS into Siit.
:w: Connect WorkdayConnect Workday to Siit with a read-only Integration System User to sync employees, employment, groups and locations on a schedule, with optional field mapping and FAQConnect Workday
:h: Connect HiBobConnect HiBob to Siit by signing in with your HiBob admin credentials, no API token needed, to keep the People directory in sync and use HR dates in workflowsConnect HiBob
:r: Connect RipplingConnect Rippling to Siit from the Siit app in the Rippling App Shop to sync employee data and manage user accounts, and set up Rippling SAML SSO for SiitConnect Rippling
:a: Connect ADP Workforce NowConnect ADP Workforce Now to Siit by creating a Practitioner profile with access to reports and a service account in ADP, so Siit can sync your employee dataConnect ADP Workforce Now
:b: Connect BambooHRConnect BambooHR to Siit with your company subdomain and a BambooHR user with sufficient rights, so employee data from BambooHR enriches requester context in SiitConnect BambooHR
:l: Connect LuccaConnect Lucca to Siit with your company subdomain and a Lucca API key created by a user with sufficient rights, so Siit syncs your employee data from LuccaConnect Lucca
:d: Connect DeelConnect Deel to Siit by choosing a sandbox or production account and authorizing through Deel with a user who has sufficient rights, so Siit syncs your employee dataConnect Deel
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/integrations/integrations-hris.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.