Create and Activate the Human Approval Integration

Let's create the integration to request manager approval. The integration invokes the human workflow and passes the claimed amount to the workflow.

Prerequisites:
  1. Create and Activate the Human Approval Form
  2. Create and Activate the Human Approval Workflow
  3. Create the Trigger Connection for the Human Approval Integration

Before you create the human approval integration, keep in mind the following:

  • The integration must be asynchronous. The integration's endpoint does not receive a response.
  • The integration must always start with a REST trigger connection with the REST adapter.
  • The REST trigger connection must have with the following:
    • Trigger role
    • OAuth 2.0 Or Basic Authentication as the security policy
    • POST verb
    • JSON request
    • The trigger in the integration must be configured with the custom header x-agentic-callback-url. This is required for any integration that's calling human in the loop and must be stated with this name.
  1. Open your project.
    1. In the navigation pane, select Projects.
    2. Select your project name. For this tutorial: Simple Expense Approval Project.
  2. Create the integration.
    1. In the left toolbar, select Integration Integrations icon.
    2. In the Integrations section, click +.
      The Add integration panel is displayed.
    3. Click Create, then select Application.


      The Create integration panel shows selections for Application and Schedule.

      The integration canvas opens.

    4. In the Name field, enter Request Human Approval, leave all other fields as they are, then click Create.

      The Create connection page for the REST adapter. Fields are Name, Identifier, Role, Keywords, Description, Share with other projects. At the bottom, there's a Create button.

      The integration canvas opens.

  3. Select the connection that you previously created REST_TRIGGER_FOR_HUMAN_APPROVAL.

    Integration canvas for the “Request Human Approval” integration in the Simple Expense Approval Project. The screen shows a large, mostly empty canvas with a prompt box asking “What’s the purpose of this integration?” and an icon to send or confirm the response. On the right, a search panel is open, displaying a list of available trigger connections: REST_TRIGGER_FOR_HUMAN_APPROVAL, REST Connection, and REST_TRIGGER_FOR_AUTO_APPROVAL, under the heading “Triggers.”

  4. Configure the trigger connection.
    1. In Configure Basic Info, in the field What do you want to call this endpoint enter RequestHumanApproval and click Continue.

      Configure Basic Info screen for a REST trigger. The form includes fields to enter the endpoint name (“RequestHumanApproval”) and a description of what the endpoint does. At the bottom are Cancel and Continue buttons.

      The Configure Resource Configuration page is displayed.

    2. In Configure Resource Configuration, complete the fields as indicated:
      • What does this operation do?: Asks a human to approve the expense.
      • What is the endpoint relative resource URI?: /requesthumanapproval.
      • What action do you want to perform on this operation?: POST .

        Tip:

        An integration must have a REST trigger with a POST verb to be used as a tool in AI agents.
      • Configure a request payload for this endpoint: Make sure it has a checkmark.
      • Configure request header?: Make sure Custom has a checkmark.


      “Configure Resource Configuration” screen for a REST trigger. The form includes fields for operation name (“default”), description (“Asks a human to approve the expense”), endpoint’s relative URI (“/requesthumanapproval”), and HTTP action (POST). Below, the fields that are checked are: configure a request payload (checked) and configure request header - Custom (checked). At the bottom are Cancel, Go back, and Continue buttons.

    3. Click Continue

      The Configure Request panel is displayed.

    4. In Configure Request, complete the fields as indicated, then click Continue.

      The trigger connection must have JSON payload to be used as an agentic AI tool.

      • Select the request payload format: JSON Sample.
      • <<<inline>>>: Click and specify the following request format: 
        { "claimAmount" : "" }


      Configure Request screen for a REST trigger. Operation name is "default", resource URI is "/requesthumanapproval", HTTP method is POST. Multipart options are visible but not selected. Request payload format is set to "JSON Sample." "JSON" is selected as the media type. "Continue" button is highlighted.

      The Configure Request Header panel is displayed

    5. In Configure Request Headers, under Custom HTTP Headers, click Add and add the Custom Header Name: x-agentic-callback-url and the Description: callback URL for AI agent.

      Tip:

      The custom header x-agentic-callback-url must be specified exactly as indicated and is required for all integrations calling human in the loop. This parameter specifies the callback URL used by the AI agent to get the response after the human approval task completes.

      Configure Request Headers screen for a REST trigger displaying the operation name (“default”), resource URI (“/requesthumanapproval”), and HTTP method (POST). Below, a table lists specified custom request headers, with one parameter “x-agentic-callback-url” defined with description callback url for AI agent.” Buttons to add or remove custom request headers are on the right above the table. Cancel, Go back, and Continue buttons are at the bottom.

    6. Click Continue.
  5. In Summary, click Finish to complete the trigger connection configuration.

    Summary screen for a REST trigger. The page summarizes the REST endpoint configuration with endpoint name “RequestHumanApproval,” a field for description, and an endpoint summary section displaying REST service URI (/requesthumanapproval), HTTP method (POST), request media type (JSON), and custom request header (x-agentic-callback-url). At the bottom, there are Cancel, Go back, and Finish buttons.

  6. Add a Human in the loop action to the integration to call the workflow.
    1. Hover over the connection arrow, click the Plus icon sign that appears, type human in the search box, and select the Human in the loop action from the dialog box.

      Human in the loop action

      The Configure Basic Info panel is displayed.

    2. Configure the human in the loop action to call the workflow.
      1. On the Configure Basic Info page, provide a unique name and description in the following fields.
        • What do you want to call your endpoint?: Enter a unique name such as CallHumanApprovalWorklfow.
        • What does this endpoint do?: Provide the description Calls the workflow that requests human approval.

        Configure Basic Info” screen for invoking a human in the loop workflow. The left side shows a workflow diagram with a trigger labeled “RequestHumanApproval,” connected to a “Human in the loop” activity, which leads to an end event. The right side contains a form with fields for the endpoint name (“CallHumanApprovalWorkflow”) and a description (“Calls the workflow that requests human approval”). Cancel and Continue buttons are at the bottom.

      2. Click Continue.
      3. On the Configuration page, complete the following.
        From the Process drop-down, select the SimpleHumanApprovalWorkflow you created that the integration will call.

        Tip:

        The workflow must have been activated for it to be visible in the drop-down.

        Configuration screen for invoking a human in the loop workflow. The left side displays a workflow diagram with a trigger labeled “RequestHumanApproval,” leading to a “Human in the loop” activity, then to an end event. The right side shows configuration fields: project name (“Simple Expense Approval Project”), process (“SimpleHumanApprovalWorkflow”), version (“01.00.0000”), operation (“Create Instance”), and the URL for the POST request endpoint. Cancel, Go back, and Continue buttons are at the bottom.

      4. Click Continue.
      5. On the Summary page, review the data and click Finish.

        Your integration now looks like this:
        Integration canvas for the "Request Human Approval" integration in the Simple Expense Approval Project. The workflow diagram, displayed in the center of the screen, shows a vertical sequence: a trigger labeled "RequestHumanApproval," followed by a mapping step called "Map CallApprovalWorkflow," then a "Human in the loop" step labeled "CallApprovalWorkflow," and finally ending with an end event.

  7. Configure the mapper action to pass the Claim Amount that was received as input to the integration to the workflow as the Claimed Amount.
    1. In the map action, click Actions Actions icon, then select Edit Edit icon.
    2. Under Sources, Request Wrapper, drag Claimamount to Target, Request Wrapper, Claimed Amount.

      Mapping canvas for connecting data between sources and targets. The left panel (Sources) lists elements from the RequestHumanApproval REST request, including HTTP Headers, Request Wrapper, Claim Amount, Connectivity Properties, Security Properties, and integration metadata. The right panel (Target) displays elements from the CallHumanApprovalWorkflow HITL Process Automation request, specifically Message Start Args and Claimed Amount. A mapping line links Claim Amount in the source to Claimed Amount in the targe. The interface includes search and developer mode in the top menu.

  8. Click Validate.
  9. Click Back Back icon to return to the integration canvas.
  10. Assign a business identifier.
    1. Above the integration, click Business Identifier Business identifiers icon.
    2. Under request-wrapper, drag claimamount as the primary business identifier.

      The Sources section shows TemplateParameters expanded. The claimamount element has been dragged to the Primary business identifier name field.

  11. Click Save.

    You have completed creating the integration that calls a workflow to request human approval.

  12. Click Back Back icon to return to the Project page.
  13. Activate the integration. Only Active integrations can become agentic AI tools.
    1. In the Integrations section, next to the integration Request Human Approval, click Actions Actions icon, and select Activate.
Next step: Register the Human Approval Integration as an Agentic AI Tool.