webMethods.io Integration is a powerful integration platform as a service (iPaaS) that provides a combination of capabilities offered by ESBs, data integration systems, API Management tools, and B2B gateways.
Cloud applications are easy to adopt, but a challenge to integrate. With webMethods.io Integration, it’s never been easier to connect your SaaS applications and make your business processes more efficient.
webMethods.io Integration enables you to automate tasks by connecting apps and services, such as Marketo, Salesforce, Evernote, and Gmail. It lets your favorite apps exchange data and talk to each other seamlessly, and eliminates the need to hire expensive developers to build your favorite integrations.
webMethods.io Integration offers total visibility into all of your webMethods.io systems. Real-time alerts notify you when there is an error and allow you to take action, while Root Cause Analysis allows you to drill-down and determine where the issues are. Maintain the highest quality of service and performance with a dynamic view into how your service calls are operating.
Use webMethods.io Integration for faster business implementation of SaaS applications, to lower the TCO by eliminating maintenance and upgrade projects, and for self-service integration where expertise is not required.
See this video for a quick overview of webMethods.io Integration.
Get started with the Enablement Series Videos
The webMethods.io Integration Enablement Series are short, easy-to-understand videos, to help you get started quickly and learn more about the features in webMethods.io Integration. Click here to view the videos and get started quickly.
See this video to learn how to register for a free webMethods.io Integration account.
A project corresponds to a folder or a container for organizing your assets. They hold all the assets created by the user, along with the configurations associated with the Workflows and FlowServices inside a tenant. It comes second (after the tenant) in the hierarchy of entities in webMethods.io Integration.
Once you log in to your tenant or webMethods.io Integration account, click on the icon to create a new project.
Click here to learn more about projects.
To get started with webMethods.io Integration, you first need to create a workflow. Workflow is a connection between two or more web apps or services. It’s like a set of steps required to perform a task. You define these steps once and webMethods.io Integration automates the execution for you, every time.
In simple words, creating a workflow is like defining your conditions: When an event occurs in ‘Service A’, do something in ‘Service B’, and (optionally) pass on the data to ‘Service C’, ‘Service D’, and ‘Service E.
webMethods.io Integration offers hundreds of web services for workflows. With the help of these, you can create custom workflows by defining triggers and actions, and automate almost every aspect of your work life.
Let’s look at an example to understand it a little better.
When a new note is created in my Evernote account, translate the note in Spanish (using Google Translate Text), and send the translated text to my Gmail account.
When a new bug is created in Zoho Projects, create a new card in Trello, and send me a text message on my mobile phone.
Once you define this, webMethods.io Integration will take care of the rest.
For the first scenario, webMethods.io Integration will keep checking your Evernote account regularly. As soon as a new note is created, it will extract the body text and convert it to Spanish using Google Translate Text. The translated text will then be sent to your Gmail account. All this will be done automatically, within seconds.
If 10 notes are created in your Evernote account, webMethods.io Integration will repeat the same process 10 times, while you sit and watch the magic happen.
This is an example of a simple workflow. You can create more complex workflows by using many operations in a single workflow.
Now that you know what webMethods.io Integration is, let’s learn how to create your first workflow.
webMethods.io Integration offers various features that enables you to automate tasks based on specific requirements. However, there are some scenarios where you want to create complex integrations that require advanced data transformation and custom logic implementation.
With FlowServices, you can encapsulate a sequence of services within a single service and manage the flow of data among them, create complex, advanced integration scenarios involving multiple application endpoints, and finally include the FlowService in a workflow.
Click here to learn more about FlowServices and how to create one.
Comparing Workflows and FlowServices
Workflows and FlowServices enable you to automate and optimize monotonous tasks based on a set of predefined rules and business logic. These features give you the power to connect apps, devices, and on-premises systems with only clicks and zero code. Although Workflows and FlowServices help you to accomplish the same goal, there are significant differences between both the features.
The following table showcases the differences between Workflows and FlowServices.
|Designed for Citizen developers.||Designed for Integration specialists.|
|Offers a visual, drag and drop interface to create business use cases.||Offers steps and constructs from within the steps to create business use cases.|
|Offers in-built triggers to automatically trigger workflows when relevant events occur and actions to perform specific tasks.||Offers in-built applications and services to perform specific tasks.|
|Supports executing other FlowServices and workflows from within a workflow.||Supports executing other FlowServices from within a FlowService.|
|Ideal for scenarios where basic data transformation on application data is required. This means you can execute simple business use cases with Workflows.||Ideal for scenarios where complex integrations and advanced data transformation are required. This means you can execute simple as well as complex business use cases with FlowServices.|
Asset Support Matrix
All assets that can be used with Workflows and FlowServices can be cloned, exported, imported, published, and deployed. These functions are helpful when migrating, promoting, or copying the existing flows.
Clone - Allows you to create a new Workflow or FlowService that is identical but separate from the original Workflow or FlowService. You can clone the Workflow or FlowService to the same or different project but within a tenant.
Export and Import - Allows you to export or import a Workflow or FlowService so that can be used in multiple projects. When you export a Workflow or FlowService a zip file is created containing all assets along with its dependencies used in that Workflow or FlowService. The zip file is saved to your local drive’s default download path and this zip file can be used to import those assets either in the same tenant or a different tenant. It can be in the different region as well.
Publish and Deploy - Allows you to promote assets from one environment to another. It is possible to select multiple assets and publish them all at the same time. The project and assets are named the same. In case of redeploying, it updates the existing assets with the new data.
The following table lists the functions that are supported in the current product version:
|Feature||Clone||Export and Import||Publish and Deploy|
|Workflow with Node.js backend connector||Yes||Yes||Yes|
|Workflow with CLI app which is global||Yes||Yes||Yes|
|Workflow with CLI app which is not global||Yes||No||No|
|Workflow with CloudStream connector||Yes||Yes||Yes|
|Workflow with Custom CloudStream connector||Yes||Yes||Yes|
|Workflow with Run workflow connector||Yes||Yes||Yes|
|Workflow with MarketPlace connector||No||No||No|
|Workflow with REST connector||Yes||Yes||Yes|
|Workflow with SOAP connector||Yes||Yes||Yes|
|Workflow with Flat File connector||No||No||No|
|Workflow with B2B connector||No||No||No|
|Workflow with OnPremise connector||No||Yes||Yes|
| Workflow with Adapters
Note: SAP Adapter is yet to be supported by Workflow.
|Workflow with FlowService||Yes||Yes||Yes|
|Workflow with Messaging||Yes||Yes||Yes|
Note: If a Workflow contains a FlowService that uses either a B2B connector or a FlatFile connector then all operations work and dependencies are retrieved, created, and deployed.