Glossary

An account contains the connection details of the application that you are connecting to, for example, the URL and credentials to access the application or data source.

Automated rules for your projects to send notifications to specific users when a workflow or flow service fails, timeouts, or completes execution.

A log that maintains a history of all actions that are completed within a tenant, including details such as the type of action completed, the user who completed the action, and the date or time when the action was completed.

Conditions are programming constructs in an integration. Based on the conditions defined, the integration does different computations or actions that depend on whether a specified condition evaluates to true or false.

Connectors are components that connect and integrate applications or data sources to send and receive data. Regardless of whether direct integration between the two applications is available, connectors use data that comes from one application to make it understandable and accessible in another.

Connector Builder is a utility that is designed for building custom actions or triggers for an API.

A flow service is used to encapsulate a sequence of services within a single service and manage the flow of data among them. You can create complex, advanced integration scenarios that involve multiple application endpoints.

Hybrid connectivity allows you to establish a secure connection between webMethods Integration and your server behind the firewall. You can consume data from your on-premises applications and use those applications in your workflows or flow services.

Listeners enable integration with streaming APIs and process streaming API events. You can subscribe to any supported streaming API event and specify the flow service that must be started when the subscribed event occurs.

Messaging is one of the integration patterns that are used by the enterprise applications to solve integration challenges. Messaging systems allow independent applications to work together to accomplish some common tasks by exchanging messages without requiring direct connections. Messaging is also known as message-oriented middleware (MOM), as it allows software components that are developed independently and run on different networks to interact with each other.

Parameters are key-value pairs that are defined for use within workflows. After a parameter is set, it can be referenced anywhere within the workflow.

A pipeline refers to the data structure in which the input and output values are maintained for each step of a flow service. It provides a graphical representation view for all your data. You can map the data between user input and connectors or services.

A project corresponds to a folder or container for organizing your integrations. For example, when you create or add a workflow inside a project, all the configurations that are related to that workflow are also stored inside the project.

Pre-built integration templates that you can readily use. The templates are created based on the most common integration needs and can significantly reduce the effort that is required to build a workflow or a flow service.

A trigger automatically starts a workflow when a defined event happens, which enables you to automate a complex business process without having to manually run the workflow every time. 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 webhook is a user-defined HTTP callback, triggered by an event. webMethods Integration supports incoming webhooks in workflows, which allows you to receive messages from an external application through HTTP posts. If a webhook is enabled for a workflow, webMethods Integration generates a unique webhook URL, which you need to provide to the external application. This external application then sends an HTTP request with a JSON payload, which can be used in your workflow.

A workflow connects two or more web applications or services. It defines the sequence of steps for automating a recurring task.