> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/ai-agents/employee-lifecycle/hris-workflow-blocks.md). # HRIS Workflow Blocks HRIS workflow blocks let you connect your agent workflows directly to your HR platform using purpose-built, provider-specific blocks. Instead of relying on generic HTTP calls or custom scripts, each supported provider has its own dedicated set of blocks that map cleanly to that platform's data model and API conventions. This gives you precise control over employee data operations at every stage of the employee lifecycle. The following providers are currently supported: * **HiBob** * **Workday** * **SAP SuccessFactors** * **Shapes HR** *** ### HiBob Use HiBob blocks to read and manage employee records and organizational structure within your Bob environment. | Block | Description | | ------------------------ | ------------------------------------------------- | | `hibob_get_employee` | Look up a single employee by ID or identifier | | `hibob_list_employees` | Retrieve a list of employees, optionally filtered | | `hibob_create_employee` | Create a new employee record in HiBob | | `hibob_update_employee` | Update fields on an existing employee record | | `hibob_list_departments` | Retrieve the list of departments defined in HiBob | #### Common uses * Automatically create a HiBob record when a new hire completes onboarding intake * Sync department changes triggered by a manager approval workflow * Look up an employee's profile to pre-fill downstream steps such as IT provisioning or payroll enrollment *** ### Workday Use Workday blocks to query and manage worker data stored in your Workday tenant. | Block | Description | | ------------------------ | ----------------------------------------------------------- | | `workday_get_employee` | Look up a single worker by employee ID or reference | | `workday_list_employees` | Retrieve a list of workers, with optional filter parameters | #### Common uses * Pull worker details at the start of an offboarding workflow to populate deprovisioning tasks * List employees in a given organization unit to trigger bulk lifecycle actions *** ### SAP SuccessFactors Use SAP SuccessFactors blocks to interact with employee central records in your SuccessFactors instance. | Block | Description | | -------------------------------- | -------------------------------------------------- | | `successfactors_get_employee` | Look up a single employee by person ID or user ID | | `successfactors_list_employees` | Retrieve a list of employees from Employee Central | | `successfactors_create_employee` | Create a new employee record in SuccessFactors | | `successfactors_update_employee` | Update an existing employee record | #### Common uses * Trigger a SuccessFactors record creation step as part of a coordinated new hire workflow * Read employee data to drive conditional logic, such as routing based on employment type or location *** ### Shapes HR Use Shapes HR blocks to manage people records within your Shapes HR workspace. | Block | Description | | -------------------------- | ------------------------------------------------------ | | `shapeshr_get_employee` | Look up a single employee record | | `shapeshr_list_employees` | List employees across your Shapes HR organization | | `shapeshr_create_employee` | Create a new employee in Shapes HR | | `shapeshr_update_employee` | Update fields on an existing Shapes HR employee record | #### Common uses * Keep Shapes HR records in sync when employee data changes in a connected system * Create new employee entries as a final step in an automated onboarding flow *** ### Connecting your HRIS provider Before you can use any HRIS block, you need to authenticate your agent workflow with the relevant provider. Each provider uses its own connection configuration: 1. Open your workflow in the agent editor and add an HRIS block from the block picker. 2. Select the target provider from the block's provider dropdown. 3. Click **Connect account** and follow the prompts to supply your API credentials or OAuth token for that provider. 4. Once connected, the credential is saved to your workspace and can be reused across other workflows and blocks for the same provider. Each provider connection is scoped to your workspace, so you only need to authenticate once per provider regardless of how many workflows use those blocks. *** ### Passing data between HRIS blocks and other steps HRIS blocks expose their output as structured data that subsequent steps can reference directly. For example, the employee object returned by `hibob_get_employee` can be passed into a notification block, a conditional branch, or a third-party integration step using the standard variable picker in the workflow editor. Use list blocks (`hibob_list_employees`, `workday_list_employees`, and equivalents) to feed a loop step when you need to perform an action for each employee in a result set. *** ### Supported operations summary | Provider | Get employee | List employees | Create employee | Update employee | List departments | | ------------------ | ------------ | -------------- | --------------- | --------------- | ---------------- | | HiBob | Yes | Yes | Yes | Yes | Yes | | Workday | Yes | Yes | - | - | - | | SAP SuccessFactors | Yes | Yes | Yes | Yes | - | | Shapes HR | Yes | Yes | Yes | Yes | - | --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.harmony.io/ai-agents/employee-lifecycle/hris-workflow-blocks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.