WFD Integration Engine · by Workflow Doctor
Integrate once.
Connect everything.
Create reusable connections between applications, WFD Engines and business systems — moving data and documents in either direction without rebuilding the same integration every time.
Engine Reusable plugin layer
The problem
Stop integrating every application with every other application.
Point-to-point integration looks simple when there are two systems. Add another application, another ERP, another document repository — and every connection becomes another thing to build, test, support and change.
A different shape
Build the connector once. Reuse it everywhere.
Integration Engine gives different applications and WFD Engines a common integration layer. Connect a target system once, then reuse that capability wherever it is needed.
The integration becomes a reusable asset — not code trapped inside one process.
Data and documents
Each system can speak its own language.
Integration Engine can receive, reshape and pass on information in the form each side expects. That can mean structured data, files and documents — moving into a process, out to a target system, or both.
Plugin architecture
Connectors that belong to Integration Engine — not one project.
Plugins isolate the details of each target system behind a consistent integration layer. Standard connectors can be reused, and bespoke plugins can be developed where a customer-specific system needs one.
For ABBYY-centric solutions
Make ABBYY easier to connect.
ABBYY Vantage and ABBYY FlexiCapture are often only one part of a complete business process. Integration Engine provides the reusable layer between capture and the finance, ERP, document or line-of-business systems around it.
For ABBYY partners, that means less repeated point-to-point integration work across customer projects — and connectors that can become reusable assets rather than one-off implementation code.
Customer-facing control
Know what the integration is doing.
Integration Engine includes a customer-facing administration interface for configuration and runtime visibility. Combined with logging, events, failure handling and telemetry, it gives support teams a clearer route from “something failed” to “this is what happened”.
Meet systems where they are
APIs aren't the only way businesses integrate.
Integration patterns can include REST APIs, databases, files and folders, queues, SFTP and document exchange. The plugin boundary lets the transport fit the system instead of forcing every system into the same shape.
The WFD Engine ecosystem
One integration layer.
Many focused Engines.
Integration Engine works independently, but becomes especially valuable when several WFD Engines need access to the same external systems.
Focused Engines. Better together.
See Integration Engine at the system boundary.
In this invoice-processing example, other Engines perform focused process capabilities. Integration Engine owns the final exchange with the external finance system — while Routing Engine remains responsible for workflow orchestration.
Practical questions
Integration Engine, in plain English.
Can Integration Engine be used without other WFD Engines?
Yes. It is a standalone integration capability. The reuse story becomes even stronger when several WFD Engines or applications need to connect to the same external systems.
Is it a no-code integration designer?
No. Connectors and integration logic are developed. The customer-facing administration interface is for configuration and operational control rather than replacing development with a drag-and-drop designer.
Can it move documents as well as data?
Yes. Integration Engine can participate in integrations that exchange documents and files alongside structured business data.
What is the difference between Integration Engine and Routing Engine?
Integration Engine owns connectivity, transformation and reliable exchange with systems. Routing Engine owns the wider workflow — decisions, sequencing and orchestration across process capabilities.
What if the target system does not already have a connector?
The plugin architecture is designed to support bespoke connectors where a customer-specific or specialist system needs one.
Start a conversation
Your next integration shouldn't start from zero.
Tell us what needs to connect. We’ll show you how Integration Engine can turn that connection into something reusable across your wider solution.