Building workflows with AI from integration descriptions

The self-service, goal-oriented agentic integration authoring feature allows business technologists to describe their goals in natural language prompts. The Integration Agent interprets the input, creates a plan based on the goal, and then builds and deploys the workflow.

Before you begin

Make sure that you meet the following prerequisites before you start creating integrations.

  • Access to IBM® webMethods Hybrid Integration, webMethods Integration capability, and the necessary permissions to create projects, the associated assets, and integrations.
  • Create and configure the required connector accounts in the webMethods Integration capability in the target project where you want to create the integration.

About this task

Agentic integration authoring allows you to create workflows without needing specialized knowledge in integration tools, domain or cross-domain expertise, or familiarity with the webMethods Hybrid Integration capabilities. It reduces reliance on integration specialists, freeing them to focus on key strategic initiatives. By streamlining the workflow creation process, it supports greater business agility and enhances productivity across different roles.

You can do the following tasks by using the Integration Agent.

  • Create goal-driven integrations through the conversational chat interface.
  • Generate workflow definitions for specific use cases without requiring knowledge of integration authoring capabilities and the associated capability user interfaces.

Explore the following sample prompts by using the Integration Agent from the webMethods Hybrid Integration platform home page.

  • Launch an email marketing campaign for purchase of seasonal discounted products with double the reward points for existing customers for the next 30 days.

    Connectors - Salesforce CRM Rest and Gail. Triggers - Not applicable

  • As a support lead, I want to streamline incident tracking so that I can get notifications and create tickets for Engineering and Operations teams for resolution.

    Connectors - Atlassian Jira, Servicenow Enterprise, and Slack. Trigger - Atlassian Jira - New Issue

  • As a sales lead, the goal is to boost conversion rates such that when a lead or deal reaches a probability greater than 90%, automatically notify the sales team, enabling follow-up and chances of successful conversion.

    Connectors - Salesforce and Microsoft Dynamics 365. Trigger - Salesforce - Opportunity Updates

  • As a sales and marketing team leader, the objective is to align sales and marketing by extracting updated or new SalesPerson, Company, Lead, and Opportunity data from a sales system and syncing it to a marketing platform for consistent data and better collaboration.

    Connectors- Marketo and Salesforce CRM Rest. Trigger - Marketo - New Lead

Note: For an example of creating a workflow using the AI conversation interface, see Creating a workflow in webMethods Integration by using the AI conversation interface.
Prompt guidelines
  • Multi-node prompts are supported when the connector and action details are explicitly specified, for example, Get recent leads from Salesforce CRM – REST and add them to a new marketing campaign in Marketo. Unclear steps might cause failures, for example, Map the fields, Do the mappings from x to y, and Generate survey link are not supported.
  • Avoid technical jargon. For example, Notify on Slack or Inform on Slack might cause errors. Prompts that use clear language, such as Send message on Slack or Send notification on Slack are supported.
  • Prompts must include accurate connector names, trigger event names, operation names, and action names.
  • All conditions must be stated in the prompt. For example, instead of saying closed opportunity in Salesforce, say When an opportunity is updated in Salesforce and status is set to closed.
  • Prompts with simple, clear steps are supported, while complex phrasing or convoluted sentences might cause failures.
  • Prompts must follow the format of a trigger event followed by an action. For example, When an issue is created in Jira, create a new incident in ServiceNow is supported. However, Create a new incident in ServiceNow when an issue is created in Jira is not supported.
  • Prompts must use the exact event and action names as defined in webMethods Integration. For example, use Post a message to a channel in Slack instead of Send message in Slack.

Procedure

  1. With administrator permissions, access the webMethods Integration capability.
  2. Create a new project. If you prefer to use an existing project for asset creation, you do not need to create a new one. Help ensure that the user has the necessary access to the selected project. See how to create a project.
  3. Create the connector accounts required for the prompt in the project. See how to create a connector account.
  4. Go to the webMethods Hybrid Integration platform home page.
  5. Click the AI icon on the webMethods Hybrid Integration platform home page to open the Integration Agent conversation interface.
  6. Select a sample prompt or enter your own prompt. You are redirected to the webMethods Integration capability agent. The agent identifies the prerequisites that are required for your use case.
  7. Select the project where you want to create the integration and click Confirm. The agent pulls the assets from the asset explorer and creates a plan. The plan outlines the sequence of steps to create and run the integration. You can refine the workflow over multiple conversational turns, with the agent retaining context across prompts and gradually updating the authoring plan throughout the conversation.
  8. Click Edit to modify the plan and provide your input for the steps in the plan. Steps on the Edit Plan page detail the operations to be performed.
  9. After you have configured the parameters, click Save and analyze.
  10. Click Start. The agent creates the trigger first, and if the trigger is created successfully, it then proceeds to create the workflow. When the agent prompts you to run the workflow, click Yes. The agent creates the workflow in the webMethods Integration capability. If the workflow has errors, it does not run. In that case, resolve the errors in the workflow.