Use AI to Create an Integration

You can use AI to create an integration (within a project) based on natural language text. Using natural language, you can specify the purpose of the integration.

On the integration canvas, click Ask Oracle, specify what the integration needs to do, and click Send Send icon or press Enter. See Best Practices.

For example, you can specify to create an integration that receives customer information from Salesforce and updates NetSuite with that customer information if the customer is a VIP customer, sends a notification to the customer after updating NetSuite, and logs a message if the customer is not a VIP customer.

Note:

  • Creation of an integration using AI is only supported within a project.
  • AI features are available in select regions. See AI Feature Availability in Provisioning and Administering Oracle Integration 3.
Here’s what happens after you click Send Send icon.
  • The AI determines the nodes to be created for the request specified by the user and provides the list of nodes in a sequential order along with the type of adapter to be used for the trigger/invoke.
  • The connection needed for the integration is automatically selected from the available connections within the project and a trigger/invoke is created. If there is no connection available within the project, the AI will try to create a draft connection and then create a trigger/invoke using it.
  • The nodes are created too.
  • If multiple connections are available within the project, then the AI tries to identify the appropriate connection and then creates the trigger/invoke.
  • Make sure you have preconfigured the necessary connections correctly and specified their usage clearly in the natural language text you provided. The AI might automatically configure the trigger/invoke by selecting the operation and business object needed for the trigger/invoke based on the natural language text about what the trigger/invoke needs to do and the configured connections specified for use. The automatic configuration of trigger/invoke by AI is designed to deliver the best possible results. It is attempted automatically, however successful configuration cannot be guaranteed in every case.

    Note:

    The automatic configuration of trigger/invoke is supported only for the following adapters and under these conditions:
    • REST Adapter: Supported only when configured with the Swagger/OpenAPI catalog.
    • Oracle ERP Cloud Adapter, Oracle CX Sales and B2B Service Adapter, and Oracle HCM Cloud Adapter: Supported only for CRUD operations, generic/non-custom business objects, and generic/non-custom business events.
    • Oracle NetSuite Adapter: Only invoke is supported, and only for basic/search operations and single generic/non-custom business objects.
    • Salesforce Adapter:
      • Trigger is supported only on the available platform events for the configured salesforce application.
      • Invoke is supported only for create, update, or delete operations using generic/non-custom business objects.
    • SOAP Adapter: Supported only for WSDL URL or file upload use cases.
    • Oracle Autonomous AI Transaction Processing (ATP) Adapter: Only invoke is supported, and only for operations on tables (for connections without an agent) and stored procedures.
  • In the Ask Oracle pane, the AI might also provide best practices that might be helpful in improving the integration flow.
The AI creates a skeleton integration. You can perform one of the following steps:
  • Modify it further as needed by specifying updates using natural language in the Ask Oracle pane or configure the integration manually. To learn how you can edit an integration using AI, see Use AI to Edit an Integration.
  • Save the integration.
  • Click Remove all AI generated actions Remove all AI generated actions icon to remove the integration flow created by AI. The integration flow created by AI is removed. You can specify a new request indicating what the integration needs to do.
When you save the integration, in the Ask Oracle pane, the AI might list one or more best practices to improve the integration flow.
  • You can open or close the Ask Oracle pane, as needed. A number indicating the number of best practices available is shown when best practices are available.
  • When you modify the integration, you can click Recheck best practices Recheck best practices icon to verify if there are any new best practices for the updated integration flow.
  • Click Expand Expand icon to see the best practices or click Collapse Collapse icon to hide the best practices. You can also expand a best practice to see the detailed description or collapse it, as needed.

You can activate the integration after you’ve configured it.

Best Practices

  • Specify the exact system to be called (for example: Salesforce, NetSuite, or others) so that the trigger/invoke is created with the same adapter.
  • In order to create the trigger/invoke with correct connections, provide the connection name (for example: Call service A using connection {connection_name in system}).
  • To add a fault handler, specify conditional logic too (for example: Notify the user if any failures occur during the process or Handle failures/errors during the process).