The Agentforce HR Service template includes preconfigured subagents and actions designed to address employee requests. How you deploy these assets depends on whether you are using the Flow Connector model or the custom integration model.
Required Editions
| View supported editions. |
To give you maximum flexibility in how you connect to your external systems, we offer two distinct setup models. You can leverage our Flow Connector path for native, no-code connectivity or use the Standalone path for custom integrations. The Standalone path also extends to the new Agentforce Studio for a streamlined builder experience.
Before configuring assets, identify the implementation model that fits your HR ecosystem.
Flow Connector Model (No-Code)
The Flow Connector model uses MuleSoft for Flow to provide native, no-code connectivity to external systems. This streamlined path removes the need for custom middleware development. Because each external system stores data differently, connectivity behaves according to the specific triggers and actions available on the connector's reference page.
For out of the box SCI workflows and Agent Tools that use Flow connectors, configure employee ID mapping whenever a flow needs to match employee identifiers between Salesforce and an external system. For example, this applies to the BambooHR connector with the Create Goal, Update Goals, and Get Goals Agent Tools, and to any other SCI workflow or agent tool that depends on external ID mapping.
Salesforce can resolve Salesforce IDs within Salesforce. To map a Salesforce ID to an external employee ID, such as a BambooHR employee ID, configure ID mapping because each system uses different identifiers.
Choose one of these approaches:
- Store Salesforce and external employee ID pairs in the External Internal ID Mapping object.
- Implement a custom ID mapping solution in your integration.
- For standard flows, use Flow override to add connector and mapping logic. Keep the same Flow API name, and don't change flow input or output parameters. Changing flow input or output parameters can break the associated agent tool reference.
Standalone Integration Model (Custom)
The standalone model uses custom-built MuleSoft applications to bridge Salesforce with your external systems. This model currently supports two configuration environments:
- Agentforce Studio Builder: The new, unified workspace for the agent lifecycle. Most existing standalone subagents and Actions (like Direct Deposit and Expense Management) are now available here for a more streamlined configuration experience. See Access Agentforce Studio and the New Agentforce Builder.
- Legacy Standard Setup: The configuration path for standalone assets accessible through the legacy Agentforce Builder interface. These actions continue to utilize a custom Mule application for robust, third-party connectivity.
| Model | Setup Path | Available Subagents (Topics) | Subagents Associated with Individual Agent Templates | Available Actions | Associated SCIs (Service Catalog Items) |
|---|---|---|---|---|---|
| Flow Connector Model | Minimal configuration. | Employee Goal Management Subagent | Goal Management Agent |
Ready to use with BambooHR right away and flexible enough to connect with virtually any third-party system.
|
Note: SCI association is available for non-Get actions. |
| Compensation and Rewards Management Subagent | Employee Compensation Agent | View Salary And Total Rewards |
No SCI for this. |
||
| Employee Payroll Management Subagent | Employee Payroll Agent |
|
Payroll Discrepancy Note: SCI association is available for non-Get actions. |
||
| Paychex Direct Deposit Management Subagent | Employee Payroll Agent |
|
Change Direct Deposit Allocation Note: SCI association is available for non-Get actions. |
||
| Manage Employee Tasks Subagent | Employee Task Management Agent |
|
Mark Task As Complete Note: SCI association is available for non-Get actions. |
||
| Shift Swap Subagent | Time, Attendance & Scheduling Agent |
|
Swap Shifts Note: SCI association is available for non-Get actions. |
||
| Anomaly Correction (Missed Punches) Subagent | Time, Attendance & Scheduling Agent | Correct Missed Punch | Missed Punch | ||
| Subagents and Actions on new Agentforce Studio | Requires configuration. Some subagents and actions require a custom Mule application for third-party system integration. See the Available Subagents (Topics) and Available Actions columns for details. |
Requires Mule App Integration:
Standalone (No Mule App Required):
|
|
Requires Mule App Integration:
Standalone (No Mule App Required):
|
Note: SCI association is available for non-Get actions. |
| Subagents and Actions in native or legacy Agent Builder | Requires configuration. Some subagents and actions require a custom Mule application for third-party system integration. See the Available Subagents (Topics) and Available Actions columns for details. |
Requires Mule App Integration:
Standalone (No Mule App Required):
|
|
Requires Mule App Integration:
Standalone (No Mule App Required):
|
Note: SCI association is available for non-Get actions. |
- Agentforce HR Service Subagents
Get to know the subagents (previously referred to as topics) included in the Agentforce HR Service Agent template. To get started, identify whether your implementation uses the MuleSoft for Flow: Integration connectors model or a custom integration. - Agentforce HR Service Actions
Get to know the actions included in the Agentforce HR Service Agent template. To get started, identify whether your implementation uses the MuleSoft for Flow: Integration connectors model or a custom integration.