Flow Editor

webMethods.io Flow Editor allows you to create complex integrations using a graphical drag and drop tool and use those integrations in your webMethods.io Integration workflows. The Flow Editor has rich data mapping, a familiar debugging mechanism, a large collection of built-in services, and dashboards to monitor integrations.

Let us create an integration — for example, CRMIntegration which will query and list Salesforce accounts using a predefined operation queryAccounts.

Overview of Steps

  • Step 1: Login to webMethods.io Integration instance
  • Step 2: Click App Switcher to launch the webMethods.io Flow Editor
  • Step 3: Create an Integration
  • Step 4: Use the Integration in your webMethods.io workflow

Detailed Steps

Step 1: Login to webMethods.io Integration Instance

Before you create an integration, connect to the webMethods.io instance with your webMethods.io Integration account where you want to execute the workflows. Read more about Understanding the GUI.


Step 2: Click App Switcher to Launch the Flow Editor

After you log in, click the App Switcher and select webMethods.io Flow Editor.


The Projects list page in webMethods.io Flow Editor appears. All projects created in webMethods.io Integration are listed on the Projects page.

Note: If you are granted permission to view only two specific projects in webMethods.io Integration, then in the Flow Editor you will be able to view only those two projects.

Step 3: Select a Project and Create an Account

In the Projects list page, click on Edit view. Now go to Applications > Salesforce CRM > Add New Account to create an Account. Read more about creating an Account from the Flow Editor context-sensitive Help.

For demo purposes, we have created the Salesforce_CS account.


Step 4: Create an Integration

To create an integration:

Click Integrations.


Click Add New Integration to create a new integration.

Name the new Integration as CRMIntegration. This integration will query accounts from Salesforce.


Click Applications, drag the Salesforce CRM Application to the workspace, and drop it at the anchor point.


Click the warning icon, select the Salesforce account Salesforce_CS and select the predefined operation queryAccounts.


Click the bars icon and select Map input and output.


The Pipeline Data window shows the input parameters.


Click Next and map the queryAccount Output to the pipeline Output.


Click Finish and then save your integration.

The new integration appears on the Integrations list page.


You have successfully created your integration.

Step 5: Use the Integration in your webMethods.io Workflow

The integrations you create in the Flow Editor are automatically made available to you as Actions in webMethods.io Integration. You can use these actions, that is, Flow Editor integrations in your workflows to automate tasks.

We will understand how to do this, by continuing with our Salesforce integration, CRMIntegration.

Click the App Switcher icon and navigate back to the webMethods.io Integration platform.


You will see the Projects list page. Select the project. The Workflows associated with that project appears. You can also create a new workflow. Read more about Creating First Workflow.

In the webMethods.io Integration workflow screen, click the Custom icon. Then click the down arrow beside webMethods.io Flows and select the integration, CRMIntegration.


Drag and drop CRMIntegration on the canvas and connect the action to the workflow.

Hover on the CRMIntegration icon and select Settings icon that appears. A pop-up window will appear where you will see the application supported on screen. 


Click Next, you will be redirected to the action configuration screen, where you can add relevant details to execute the action.


After this, click Next, now you can test the action.



And then click Done. This will take you back to the canvas. 

Once you have configured the rest of the workflow, connect the action to the Stop icon and save it.

Click the Debug panel at the low-left corner of your screen to view the execution details of the workflow. Read more on Debug Panel.