Oracle Fusion HCM AI Orchestrator

Oracle Fusion HCM AI Orchestrator is the AI agent orchestration layer built into Oracle Fusion Cloud Human Capital Management. It enables external applications to programmatically invoke Oracle Fusion AI Agent teams — specialized, outcome-driven AI agents that are embedded directly into HCM business processes. These AI agents can reason across unified enterprise data, enforce approval hierarchies and policies, execute multi-step workflows, and return structured results asynchronously. Common use cases include automating HR processes such as onboarding, workforce planning, talent review, and employee query resolution by triggering and managing AI agent workflows from external systems through the invokeAsync REST API.

Power end-to-end data operations for your Oracle Fusion HCM AI Orchestrator API with Nexla. Our bi-directional Oracle Fusion HCM AI Orchestrator connector is purpose-built for Oracle Fusion HCM AI Orchestrator, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Oracle Fusion HCM AI Orchestrator or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Oracle Fusion HCM AI Orchestrator workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

To connect Nexla to the Oracle Fusion HCM AI Orchestrator API, you need an active Oracle Fusion Cloud HCM instance and appropriate access to register an OAuth 2.0 application in your Oracle Cloud Identity and Access Management (IAM) domain. The AI Orchestrator API uses OAuth 2.0 Bearer token authentication — access tokens are obtained from the OCI Identity domain linked to your Fusion Applications instance.

Oracle Fusion Cloud HCM Instance URL

Your Oracle Fusion Cloud HCM instance is accessible at a URL in the following format:

• https://{'{instance_name}'}.fa.oraclecloud.com

The exact base URL for your Fusion Applications instance can be confirmed by your Oracle Cloud administrator or found in the Oracle Cloud Infrastructure Console under your Fusion Applications environment details.

Register a Confidential Application for OAuth 2.0

The Oracle Fusion HCM AI Orchestrator API requires OAuth 2.0 authentication. To obtain client credentials (Client ID and Client Secret), an Oracle Cloud administrator must register a confidential application in the OCI Identity domain associated with your Fusion Applications instance. Complete the following steps:

1. Sign in to the Oracle Cloud Infrastructure Console as an administrator.

2. Navigate to Identity & Security > Identity > Domains, and select the identity domain associated with your Fusion Applications instance.

3. In the domain, navigate to Integrated Applications, and click Add Application.

4. Select Confidential Application as the application type, and click Launch Workflow.

5. On the Add Application Details screen, enter a descriptive Name (for example, Nexla HCM AI Orchestrator Integration) and an optional description, then click Next.

6. On the Configure OAuth screen, select Configure this application as a client now, and choose the appropriate Grant Type:

   • Client Credentials: Recommended for server-to-server integrations where no user interaction is required. The client acts on its own behalf using its own credentials.
   • Resource Owner: Allows authentication using a Fusion Applications username and password. This grant type is simpler to configure but is generally less preferred for production integrations.

7. Under Token issuance policy, leave the default settings or configure token scopes as required by your organization's security policies.

8. Click Next, review the configuration, and click Finish to create the application.

9. After the application is created, click Activate to enable it.

10. Navigate to the OAuth Configuration tab of the newly created application and copy the Client ID and Client Secret. Store these securely, as the Client Secret cannot be retrieved again after you navigate away.

    Important

    The Client Secret is sensitive and must be treated like a password. Store it in a secure location such as a secrets manager. If the Client Secret is compromised or lost, you must generate a new one in the OCI Identity domain application settings.

Configure the Client ID as a Fusion Applications User (Client Credentials Only)

If you are using the Client Credentials grant type, you must configure the OAuth client as a recognized user within Fusion Applications so that the API can enforce role-based access control:

1. In Oracle Fusion Applications, navigate to Tools > Security Console.

2. Select the Users tab, and click Add User Account.

3. In the User Name field, enter the Client ID of the confidential application you created above (the user name must exactly match the Client ID).

4. Complete the required fields and assign the appropriate HCM roles and privileges that the Nexla integration will need to invoke AI Agent teams. At minimum, the user must have the roles required to access the AI Orchestrator API and invoke the specific AI Agent teams you plan to use.

5. Click Save and Close to create the user.

The Fusion Applications user roles assigned in this step directly control which AI Agent teams and HCM data the integration can access. Assign only the roles necessary for your integration use case to follow the principle of least privilege. For more information about Oracle Fusion Applications security roles, refer to the Oracle Fusion Security documentation.

For detailed instructions on enabling external application access to Fusion AI Agents, refer to Oracle's official guide: Enable Applications to Access Fusion Applications Agents.

Authenticate

Credentials required

An OAuth authentication flow where users must authorize an application to access their data

Field	Required	Secret	Description
Idcs Url	Yes	No	Base URL variable: idcs_url
Client ID	Yes	Yes	A unique public identifier assigned to your application
Access Scope	No	No	A space-separated list of permissions your application requests
Client Secret	No	Yes	A private key used to authenticate your application when requesting tokens
Fusion Url	Yes	No	Shared variable: fusion_url
Hcm Base	Yes	No	Shared variable: hcm_base
Auth Test URL	Yes	No	URL used to verify authentication credentials
Auth Test Method	Yes	No	HTTP method used for the authentication test request
Auth Test Body	No	No	Request body sent when testing authentication

Create a credential in Nexla

1. To create a new Oracle Fusion HCM AI Orchestrator credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. The Oracle Fusion HCM AI Orchestrator API uses OAuth 2.0 for authentication. Enter the base URL of your Oracle Fusion Cloud HCM instance in the Instance Base URL field. This should be the root URL of your Fusion Applications environment, for example https://yourinstance.fa.oraclecloud.com. Do not include any path components after the domain.

4. Enter the Client ID from the confidential application you registered in your OCI Identity domain in the Client ID field. This is the unique identifier generated when you created the application.

5. Enter the Client Secret associated with your registered confidential application in the Client Secret field.

   Important

   The Client Secret authenticates your integration to Oracle's identity platform and should be kept strictly confidential. Do not embed it in code, share it in documentation, or check it into source control. Rotate it regularly in accordance with your organization's security policies.

6. Click the Save button at the bottom of the overlay to save the configured credential. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Oracle Fusion HCM AI Orchestrator connector tile, then select the credential that will be used to connect to the Oracle Fusion HCM AI Orchestrator instance, and click Next; or, create a new Oracle Fusion HCM AI Orchestrator credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Oracle Fusion HCM + AI Orchestrator endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Invoke Agent (Async)

Asynchronously invoke an Oracle Fusion AI Agent team by submitting a POST request to the invokeAsync endpoint, which returns a job ID for subsequent status polling.

• Issues a POST request to https://{fusion_url}/api/fusion-ai/orchestrator/agent/v2/{agent_name}/invokeAsync. The full response is returned at the root path ($).
• Configure the following parameters: Agent Name — the workflow code of the AI Agent team to invoke (required). Conversational — whether to invoke in conversational mode. Version — the agent version to target. Status — initial status value for the invocation. Message — the input message or payload to send to the agent.

The Agent Name (Workflow Code) is the unique identifier for the AI Agent team in Oracle Fusion AI Agent Studio. The response from this endpoint includes a job ID — use the Get Agent Job Status endpoint to poll for completion and retrieve the agent's output.

Get Agent Job Status

Retrieve the current status and output of a previously submitted Oracle Fusion AI Agent team invocation using the job ID returned by the invokeAsync endpoint.

• Issues a GET request to https://{fusion_url}/api/fusion-ai/orchestrator/agent/v2/{agent_name}/status/{job_id}. The full response is returned at the root path ($).
• Configure the following parameters: Agent Name — the workflow code of the AI Agent team (required). Job Id — the job ID returned by the Invoke Agent (Async) call (required).

Poll this endpoint after invoking an agent asynchronously. The job status will transition through states (e.g., SUBMITTED, IN_PROGRESS, COMPLETED) — retrieve results only when the status indicates completion.

Get All Workers

Retrieve all worker (employee) records from Oracle Fusion HCM with pagination support, including workforce details such as names, assignments, and employment information.

• Issues a GET request to https://{fusion_url}/{hcm_base}/workers with limit and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Limit — maximum number of records to return per page. Offset — number of records to skip for pagination.

Use Limit and Offset together to paginate through large employee datasets. For best performance, use the maximum supported limit value and increment the offset by the limit value on each successive call.

Get Worker by ID

Retrieve a single worker record from Oracle Fusion HCM by specifying the worker's unique identifier.

• Issues a GET request to https://{fusion_url}/{hcm_base}/workers/{worker_id}. The full response is returned at the root path ($).
• Configure the following parameters: Worker Id — the unique identifier of the worker to retrieve (required).

Use the Get All Workers endpoint to retrieve worker IDs, or reference worker IDs from another data source in your Nexla environment using lookup-based macros.

Get Worker — Describe Schema

Retrieve the metadata schema description for the Oracle Fusion HCM workers resource, which documents all available fields and their data types.

• Issues a GET request to https://{fusion_url}/{hcm_base}/workers/describe. No parameters are required. The full response is returned at the root path ($).
• No parameters need to be configured for this endpoint.

This endpoint is useful for understanding the full schema of the workers resource before building data transformations or mapping fields in a Nexla flow.

Get All Payslips (by PersonId)

Retrieve all payslips for a specific person from Oracle Fusion HCM, with support for filtering, ordering, and expanding related payroll data.

• Issues a GET request to https://{fusion_url}/{hcm_base}/payslips with q, orderBy, limit, expand, and onlyData query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Person Id — the person ID to filter payslips by (required). Orderby — sort order for results. Limit — maximum number of records to return. Expand — related resources to include in the response. Onlydata — whether to return only data without metadata links.

The Person Id parameter filters payslips to a specific employee. Use the Get All Workers endpoint to retrieve valid Person IDs for your workforce dataset.

Get Payslip by ID

Retrieve a single payslip record from Oracle Fusion HCM by specifying the payslip's unique identifier.

• Issues a GET request to https://{fusion_url}/{hcm_base}/payslips/{payslip_id}. The full response is returned at the root path ($).
• Configure the following parameters: Payslip Id — the unique identifier of the payslip to retrieve (required).

Use the Get All Payslips endpoint to retrieve payslip IDs, then use this endpoint to fetch detailed information for a specific payslip record.

Get All Payroll Relationships

Retrieve all payroll relationship records from Oracle Fusion HCM with pagination support, linking employees to their associated payroll definitions.

• Issues a GET request to https://{fusion_url}/{hcm_base}/payrollRelationships with limit and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Limit — maximum number of records to return per page. Offset — number of records to skip for pagination.

Use the payroll relationship IDs returned by this endpoint as input for the Get Payroll Relationship by ID or Get Payroll Assignments for Relationship endpoints.

Get Payroll Relationship by ID

Retrieve a single payroll relationship record from Oracle Fusion HCM by specifying the payroll relationship ID.

• Issues a GET request to https://{fusion_url}/{hcm_base}/payrollRelationships/{payroll_rel_id}. The full response is returned at the root path ($).
• Configure the following parameters: Payroll Rel Id — the unique identifier of the payroll relationship to retrieve (required).

Use the Get All Payroll Relationships endpoint to identify available payroll relationship IDs before using this endpoint for targeted record retrieval.

Get Payroll Assignments for Relationship

Retrieve all payroll assignment records associated with a specific payroll relationship, showing the employee's assignment details within that payroll.

• Issues a GET request to https://{fusion_url}/{hcm_base}/payrollRelationships/{payroll_rel_id}/child/payrollAssignments. The full response is returned at the root path ($).
• Configure the following parameters: Payroll Rel Id — the unique identifier of the payroll relationship whose assignments should be retrieved (required).

This endpoint retrieves child payroll assignment records nested under a parent payroll relationship. Use it in conjunction with Get All Payroll Relationships to build a complete payroll assignment dataset.

Get All Absences

Retrieve all absence records from Oracle Fusion HCM with pagination support, including leave requests, absence types, and duration details.

• Issues a GET request to https://{fusion_url}/{hcm_base}/absences with limit and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Limit — maximum number of records to return per page. Offset — number of records to skip for pagination.

This endpoint retrieves all absence records across all employees. For large organizations, use Limit and Offset to paginate through the full dataset efficiently.

Get Absence by ID

Retrieve a single absence record from Oracle Fusion HCM by specifying the absence's unique identifier.

• Issues a GET request to https://{fusion_url}/{hcm_base}/absences/{absence_id}. The full response is returned at the root path ($).
• Configure the following parameters: Absence Id — the unique identifier of the absence record to retrieve (required).

Use the Get All Absences endpoint to retrieve absence IDs, then use this endpoint for detailed retrieval of a specific absence record.

Get Benefit Enrollments

Retrieve benefit enrollment records from Oracle Fusion HCM, with optional filtering by person ID to focus on a specific employee's benefit elections.

• Issues a GET request to https://{fusion_url}/{hcm_base}/benefitEnrollments with q, limit, and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Person Id — filter benefit enrollments by a specific employee's person ID (optional). Limit — maximum number of records per page. Offset — number of records to skip for pagination.

Use the Person Id filter to retrieve benefit enrollments for a specific employee. Leave it blank to retrieve all benefit enrollment records across the organization.

Get Document Records

Retrieve HR document records from Oracle Fusion HCM, with optional filtering by person ID to return documents associated with a specific employee.

• Issues a GET request to https://{fusion_url}/{hcm_base}/documentRecords with q, limit, and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Person Id — filter document records by a specific employee's person ID (optional). Limit — maximum number of records per page. Offset — number of records to skip for pagination.

This endpoint retrieves HR documents such as employment contracts, identification documents, and certification records stored in Oracle Fusion HCM.

Get All Positions

Retrieve all position records from Oracle Fusion HCM with pagination support, including position names, grades, departments, and FTE allocations.

• Issues a GET request to https://{fusion_url}/{hcm_base}/positions with limit and offset query parameters. The full response is returned at the root path ($).
• Configure the following parameters: Limit — maximum number of records to return per page. Offset — number of records to skip for pagination.

Position data is useful for workforce planning, org structure analytics, and headcount reporting. Use Limit and Offset to paginate through large position catalogs.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Oracle Fusion HCM AI Orchestrator data sources can also be manually configured to ingest data from any Oracle Fusion HCM + AI Orchestrator endpoint not covered by the pre-built templates, such as GET requests for polling job status. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The API exposes two primary endpoints: Invoke AI Agent Team (Async) at https://{'{your-fusion-host}'}/api/fusion-ai/orchestrator/agent/v2/{'{AgentTeamCode}'}/invokeAsync for submitting an asynchronous agent invocation, and Check Agent Job Status at https://{'{your-fusion-host}'}/api/fusion-ai/orchestrator/agent/v2/{'{AgentTeamCode}'}/status/{'{jobId}'} for polling the resulting job.

The Agent Team Code (also referred to as the Workflow Code) is the unique identifier assigned to each AI Agent team in Oracle Fusion AI Agent Studio. You can find the Agent Team Code by navigating to AI Agent Studio within your Oracle Fusion HCM application and viewing the properties of the agent team you want to invoke. For complete details on available AI Agent teams and their codes, refer to the Oracle Fusion AI documentation.

The Oracle Fusion AI Orchestrator status endpoint typically returns a structured JSON response containing a results array alongside job status metadata — set the Path to Data in Response field (e.g. $.result or $.result[*]) to isolate the relevant output from surrounding job metadata.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Oracle Fusion HCM AI Orchestrator data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Oracle Fusion HCM AI Orchestrator destination, and select the Send to Destination option from the menu. Select the Oracle Fusion HCM AI Orchestrator connector from the list of available destination connectors, then select the credential that will be used to connect to the Oracle Fusion HCM AI Orchestrator instance, and click Next; or, create a new Oracle Fusion HCM AI Orchestrator credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Oracle Fusion HCM + AI Orchestrator endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Download Payslip Attachments

Trigger the download of attachments associated with a specific payslip in Oracle Fusion HCM by specifying the payslip ID in the request body.

• Issues a request to the Oracle Fusion HCM payslip attachments endpoint with the payslip ID supplied in the request body.
• Configure the following parameters: Payslip Id — the unique identifier of the payslip whose attachments should be downloaded (required).

Use the Get All Payslips or Get Payslip by ID source endpoints to retrieve valid payslip IDs before running this destination. The response may include binary attachment data that requires further processing.

Create Absence

Create a new absence record in Oracle Fusion HCM for a specific employee by sending the required absence details in the request body.

• Issues a POST request to the Oracle Fusion HCM absences endpoint. The request body should include the person ID and required absence fields such as absence type, start date, and end date.
• Configure the following parameters: Person Id — the unique identifier of the employee for whom the absence should be created (required).

The Person Id must correspond to a valid worker in Oracle Fusion HCM. Use the Get All Workers source endpoint to retrieve valid person IDs. Ensure the absence type and date values comply with your organization's Oracle Fusion HCM configuration.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to send a test payload to the Oracle Fusion HCM AI Orchestrator API. The result will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the destination is configured correctly before saving.

Manual configuration

Oracle Fusion HCM AI Orchestrator destinations can also be manually configured to send data to any valid Oracle Fusion HCM + AI Orchestrator endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The Oracle Fusion HCM AI Orchestrator API accepts JSON as the content format and uses POST to the invocation endpoint: https://{'{your-fusion-host}'}/api/fusion-ai/orchestrator/agent/v2/{'{AgentTeamCode}'}/invokeAsync, where {'{your-fusion-host}'} is your Oracle Fusion Cloud HCM instance hostname (for example, yourinstance.fa.oraclecloud.com) and {'{AgentTeamCode}'} is the workflow code of the AI Agent team to invoke.

The Agent Team Code (Workflow Code) uniquely identifies each AI Agent team in Oracle Fusion AI Agent Studio. Navigate to AI Agent Studio in your Oracle Fusion HCM application and open the properties of the desired agent team to find its code. For more information, refer to the Oracle Fusion AI Agents documentation.

The invokeAsync endpoint returns a job ID in the response that is required for subsequent status polling. Enable Would you like to process the API response as a Nexla Webhook source? to automatically capture this response in a new Nexla webhook source, so you can build a chained flow that polls the Get Agent Job Status endpoint for the agent's completion status.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Oracle Fusion HCM AI Orchestrator endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Oracle Fusion HCM AI Orchestrator API until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.