Familiarize yourself with the webMethods.io Integration terminology before you start creating Workflows. Understand how various concepts such as triggers, actions, webhooks, conditions, connectors, accounts, FlowServices, and containers together make up a workflow.
Creating and using a workflow get easier while knowing the terminologies used in it. This section gives you a quick overview of the components used to create a Workflow or a FlowService in webMethods.io Integration so that you can automate your daily tasks easily.
A project corresponds to a folder or container for organizing your workflows. When you create or add workflow inside a project, all the configurations related to that workflow are also stored inside the project. Every tenant, by default, has a default project. The user can choose to create additional projects as per their requirements.
A workflow is a connection between two or more web apps or services. Creating a workflow means defining the steps of a recurring task that you want to automate. For example, whenever a New Lead is created in Salesforce, create a New Task in Wunderlist. Go to Creating First Workflow to learn more about workflows and refer to our step-by-step instructions.
See this video to know about some of the common utilities used to build workflows.
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. Earlier you could do this by switching to the Flow Editor using the App Switcher, create the required integrations in the Flow Editor, and then use them in your webMethods.io Integration workflows.
We have simplified this process by providing you with FlowServices directly in your webMethods.io Integration project, thus eliminating the need to access the Flow Editor through the App Switcher. 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 can include the FlowService in a workflow.
Read more about FlowServices and know how to create a FlowService.
A trigger is an event that starts a workflow. For example, if your workflow is Whenever a New Lead is created in Salesforce, create a New Card in Trello, the first part, that is, New lead in Salesforce is the trigger. A workflow can have only one trigger.
Read more about Triggers and learn how to set up a trigger in your workflow.
An action specifies the tasks you want the workflow to perform. For example, if your workflow is Whenever a New Lead is created in Salesforce, create a New Card in Trello, the latter part, that is, create a New Card in Trello is an action. A workflow can have several actions.
Each connector has several actions that you can use. For example, Trello has actions like Create Board, Create List, Add Card, Add Board Member to Card, Add Comment, Delete Card, Get All Boards, etc.
Read more about Actions and learn how to set up in a workflow.
An account is a process of granting permission to webMethods.io Integration to perform certain tasks in third-party apps or services. So, for instance, if you use an action related to Gmail in your workflow, you will have to first login to your Gmail account, and then authorize webMethods.io Integration to perform certain tasks on your behalf.
Connectivity in webMethods.io Integration is provided through connectors. Connectors are grouped in the following categories:
Predefined Connectors: Predefined and configurable connectors. These connectors allow you to connect to the SaaS providers.
REST Connectors: You can define REST Resources and Methods and create custom REST connectors. You can invoke a REST API in a FlowService by using a REST Connector.
SOAP Connectors: Custom SOAP connectors enable you to access third party web services hosted in the cloud or on-premises environment. You can also invoke a SOAP API in a FlowService by using a SOAP Connector.
On-Premises Connectors: On-Premises applications uploaded from on-premises systems are listed in the On-Premises Connectors page.
Flat File Connectors: Flat file connectors created in webMethods.io Integration.
All connectors have a connection (Account) and an operation (Action). A predefined connector uses an Account to connect to the provider’s back end, performs operations, and comes with a predefined set of operations. Each connector has a different set of supported operations. You can also create your own custom operations.
You need to configure your Account by defining the URL and specifying the required credentials to connect to the SaaS provider.
Parameters let you set key-value pairs for your workflows. Once you set a parameter, you can use it anywhere in your workflows in a single click. Get started with using Parameters.
webMethods.io Integration supports incoming webhooks. An incoming webhook is an easy way to receive messages from an external application.
If webhook is enabled for a workflow, webMethods.io Integration generates a unique webhook URL, which you need to provide to the desired external application. This external application then sends an HTTP request with JSON payload, which can be used in your workflow.
To understand how it works, refer to our Webhooks section.
A container is an isolated run-time environment. It contains all the dependencies (configuration files, binaries, system libraries, code, etc.) that it needs to run your workflows smoothly.