Top 30 Business Workflow Automation Platforms 2027

This report forms part of The Economy Rankings’ Software & Digital Platforms portfolio. This edition evaluates active named software platforms, with the operating provider identified separately from the product.

Business workflow automation platforms connect a recurring organizational need with the people, records and application actions required to complete it. Their role is broader than removing an individual manual step. A process must preserve responsibility as a request moves through review, authorization and execution, including the exceptions that prevent the normal sequence from continuing.

This ranking evaluates general-purpose enterprise workflow and business-process automation software. One-off bespoke automations sold only as consultancy and AI agents limited to a single use case are outside the series. The unit is the named maintained platform, with its operating provider identified separately. A visual modelling tool qualifies only where an identifiable operating environment supports substantive executable processes.

The market includes process and case platforms, application-centred workflow products and integration-led orchestration. Their architectures differ. A process engine may coordinate workers and services, while a record-based application organizes tasks around shared business information. An integration platform can connect external applications, but a connector catalogue alone does not establish a governed end-to-end process. The comparison follows the documented operating model.

The 2027 edition reflects information reviewed by 22 October 2026. Five leading platforms are ordered in Tier I; ten established offerings appear alphabetically in Tier II and fifteen focused or specialist offerings alphabetically in Tier III. The assessment is editorial and weighted. It does not claim an identical benchmark across different workflow runtimes or assume that automation produces a measured operational benefit in every deployment.

Market Overview

Process design is valuable when it corresponds to execution. A diagram can make the intended sequence understandable, but the operating software must also manage tasks, state changes and interactions with external systems. Buyers should identify how the model becomes an executable process and which application records the result. That distinction separates a maintained workflow platform from a useful but non-operating process illustration.

Human participation remains important even in highly automated environments. A request may need approval, a case may require judgement and an exception may need an accountable response. The product should provide a real place for that work, with the relevant information available to the person acting. A theoretical promise that a human can intervene later is less informative than documented routing, assignment and completion behaviour.

Integration-led platforms address workflows spanning applications that retain separate records and permissions. Their practical task includes mapping information and interpreting events, not simply connecting two logos. The implementation needs to identify which system owns the business record, what authority the integration account holds and how a failed or rejected action returns to the person responsible for the process.

Application-centred platforms combine records, forms and workflow in a shared environment. That can give participants a coherent account of the request they are handling, while introducing configuration responsibilities for the organization. A flexible builder is useful only if administrators can maintain the resulting application and understand the implications of changes. Customization depth and continuing governability therefore need to be considered together.

Current agent and AI features add new participants to this architecture. They can assist with intake, analysis or application actions, but they do not remove the need to define authority and exceptions. The ranking evaluates the substantive workflow around those features. It does not infer autonomous reliability, unrestricted cross-system access or a measured efficiency improvement from the presence of an AI interface.

Industry Trend — 2027

For 2027, the visible direction connects process orchestration with configurable applications, cross-system integrations and agent-assisted actions. The central operating questions remain stable: what starts the workflow, which record describes its state, who can make a decision and what happens when an action cannot be completed as designed?

2027 market development	Current evidence and direction	Implication for the sector
Executable process models	Platforms connect workflow design with tasks, data and runtime actions.	Buyers should examine how a model becomes an operating process.
Human participation in automation	Products document approvals, assignments and human-in-the-loop steps.	Review authority and the information available to the participant should remain explicit.
Cross-application orchestration	Integration-led platforms coordinate events and actions across business systems.	Record ownership, account permissions and error handling require configuration.
Record-centred workflow applications	Builders combine forms, shared records and process stages.	The application should remain understandable and maintainable as business rules change.
Deployment-specific governance	Engines and hosted services allocate administration duties differently.	Runtime, update and support responsibilities should be identified for the actual environment.
Agents inside governed processes	Providers add agents and assistants to enterprise intake and orchestration.	The action taken and its authorization matter more than the interface label.

These developments make a representative process walkthrough more useful than a connector count. A practical evaluation follows a request through submission, a decision, an external application action and completion, then repeats the sequence with missing information or a rejected task. That reveals whether the proposed environment preserves responsibility when work departs from the ideal path.

The appropriate shortlist depends on the organization’s application architecture and process ownership. A dedicated engine, an integration-led platform and a configurable business application can each be credible. The comparison recognizes their documented workflow contribution without assuming they include the same runtime, deployment model or surrounding enterprise applications.

Methodology — Core Eligibility Criteria

The ranking uses an evidence-based editorial assessment tailored to this technical market. Candidates were required to satisfy the following core conditions:

• General-purpose enterprise workflow/BPM automation products.
• A named active product with an identifiable operating provider and inspectable current technical or product documentation.
• Substantive organizational workflows rather than a demo, inactive brand, wrapper, reseller or implementation-only consultancy.
• The product is evaluated separately from a diversified parent company’s reputation and unrelated business lines.
• Related brands under one operator are grouped; acquisitions, rebrands and supported legacy product boundaries are reviewed.
• Headquarters or current business-location and founding facts identify the provider, steward or expressly labeled product lineage.
• International comparison without geographic quotas; regional availability and deployment dependencies are qualified.
• The review uses material available by 22 October 2026; the 2027 edition does not claim observed future results.

Methodology — Ranking Factors

• Product capability and functional depth — 30%: Explicit workflow design, state/approval routing, human tasks, triggers and process orchestration beyond a single autonomous-agent use case.
• Documented enterprise utility and deployments — 25%: Named implemented business processes and traceable production usage, separating workflow operation from marketing demonstrations.
• Reliability, security and integration — 20%: Credential isolation, permissions, error/retry handling, API integration and audit/governance controls.
• Implementation ecosystem and ongoing support — 15%: Connector/SDK resources, testing/versioning guidance, implementation support and maintained process development documentation.
• Transparency and operating governance — 10%: Clear operating entity, execution/deployment terms, lifecycle maintenance and disclosure of governance/plan constraints.

The five criteria carry weights of 30%, 25%, 20%, 15% and 10%, respectively. The private research record documents criterion-level editorial assessments and supporting sources. These are judgments about the documented offering, not scores from laboratory tests performed by The Economy Rankings. Missing material evidence is pursued before selection rather than silently treated as average performance. Licensing, sponsorship and likelihood of purchasing recognition do not influence eligibility, scores or tier placement.

Company Profiles and Further Reference

Names appearing in this ranking are linked to their corresponding organizational profiles in The Economy Wiki, where available. These profiles provide further background on principal activities, technology capabilities, product and service portfolios, market positioning and related rankings and analysis across The Economy Network.

Where an entry identifies a product or service line, its provider or operator is identified so that the scope of the organizational profile is clear. The Economy Wiki profiles are maintained as editorial reference pages and may be updated as new public information becomes available.

---

Tier I — Leading Business Workflow Automation Platforms

1. ServiceNow App Engine

• Provider / operator: ServiceNow
• Headquarters: Santa Clara, California, United States
• Provider founded: 2004

ServiceNow App Engine provides application and workflow development on the ServiceNow platform, connecting business records, user tasks and enterprise processes. The evaluated product is App Engine, with unrelated service applications and separately packaged automation components kept distinct. An enterprise workflow connects people, records and system actions across a continuing process. Its design must represent both the normal sequence and the decisions that interrupt it.

Teams can build a workflow around a business record and connect it with the assignments and approvals needed to complete the process. App Engine’s record-and-workflow scope gives reviewers a concrete application boundary before considering separately packaged platform automation components. ServiceNow maintains workflow-building, administration and integration documentation. The useful review follows a request through assignment, authorization and completion, including a returned or rejected task.

Its developed enterprise workflow model and governance resources support a leading position. The chosen applications, subscriptions and extensions determine the actual operating scope. Its standing reflects documented orchestration and governance rather than an assumed automation benefit.

2. Appian

• Provider / operator: Appian
• Headquarters: McLean, Virginia, United States
• Provider founded: 1999

Appian connects process modelling, application interfaces and business data within an enterprise process-automation platform. The product supports a continuing workflow rather than merely providing a diagram or a consultancy engagement. Process design and process execution address different responsibilities. A visual model is useful when it corresponds to the tasks, events and records actually managed by the operating application.

Organizations can model work involving people and systems, then organize the forms and task responsibilities needed to execute that process. Current automation guidance links the platform’s process functions with the application environment in which a configured enterprise workflow operates. Current automation documentation describes platform functions and implementation resources. Administrators need a route to inspect configuration and understand where a person must review or authorize a change.

Its coherent process-and-application architecture supports a leading position. The selected data model, integrations and process configuration remain central to the delivered application. Recognition concerns the documented application environment, not a claim that every process can run unattended.

3. Pega Platform

• Provider / operator: Pegasystems
• Headquarters: Waltham, Massachusetts, United States
• Provider founded: 1983 (Pegasystems)

Pega Platform organizes business workflows and case-oriented work through Pega’s enterprise platform. Its evaluated purpose connects rules, tasks and customer or operational records rather than relying on the reputation of a particular industry solution. Case-oriented work often requires a flexible sequence while preserving responsibility for the underlying business outcome. The platform must connect individual actions with that continuing context.

Teams can represent a continuing case and coordinate the people or system actions needed to move it toward completion, including review decisions. The case-oriented platform keeps the continuing business context visible while individual tasks and decisions move between participating users or systems. Pega maintains workflow-automation and platform documentation. A practical evaluation includes incomplete information, an exception and a change after a task has already been assigned.

Its substantial case-and-process architecture supports a leading position. Industry applications and additional components should be identified within their actual product boundaries. The assessment recognizes the named workflow proposition without inferring a measured reduction in handling time.

4. IBM Business Automation Workflow

• Provider / operator: IBM
• Headquarters: Armonk, New York, United States
• Provider founded: 1911 (IBM lineage)

IBM Business Automation Workflow provides workflow and case-management capabilities within IBM’s business-automation environment. The named BAW product is evaluated independently of unrelated IBM infrastructure, consulting and AI services. Human tasks and system integration can participate in the same process without becoming the same operating responsibility. Their handoff should remain visible to an administrator.

An organization can coordinate business tasks and process information while connecting the workflow with supported enterprise application interfaces. The BAW API reference identifies a product-specific integration boundary, avoiding assumptions drawn from IBM’s unrelated automation or infrastructure products. IBM publishes BAW-specific API references and current product documentation. Current technical guidance helps reviewers identify supported actions and the point at which another application becomes responsible.

Its detailed process runtime and inspectable integration resources support a leading place. The deployment model and related automation components require explicit confirmation. Its contribution is considered within that documented scope rather than through a provider’s unrelated software portfolio.

5. Microsoft Power Automate

• Provider / operator: Microsoft
• Headquarters: Redmond, Washington, United States
• Provider founded: 1975 (Microsoft)

Microsoft Power Automate connects triggers, actions, approvals and business applications through Microsoft’s automation environment. Its general-purpose workflow role is evaluated separately from Power Apps and from desktop automation used without a broader business process. Automation becomes operationally meaningful when a trigger leads to a defined action and the organization can understand who remains responsible for its result.

An organization can route a request for approval, exchange data through supported connectors and continue the process after an authorized response. The approval tutorial provides a specific workflow example in which a person’s response determines how the automated sequence continues. Microsoft publishes current flow, approval and administration guidance. Interfaces should preserve the identity and meaning of the record being changed across the participating applications.

Its documented integration and enterprise operating environment support a leading position. Connector licensing, environment policies and the authority of participating accounts require configuration. The product is evaluated for that maintained workflow capability, with deployment and subscription limits kept explicit.

---

Tier II — Established Business Workflow Automation Platforms

(Alphabetical order)

Bizagi

• Provider / operator: Bizagi
• Headquarters: Washington, District of Columbia, United States
• Provider founded: 1989

Bizagi connects process modelling with executable business applications and automation. Its eligible operating environment is distinguished from using the modeller alone to draw a process that is never deployed. Case-oriented work often requires a flexible sequence while preserving responsibility for the underlying business outcome. The platform must connect individual actions with that continuing context.

Organizations can configure the data and user interaction associated with a process and connect the result with the relevant enterprise applications. The platform guide distinguishes authoring and runtime responsibilities, keeping process modelling separate from the environment that executes the resulting application. Bizagi publishes platform, Studio and API guidance. A practical evaluation includes incomplete information, an exception and a change after a task has already been assigned.

Its developed process-to-application model supports an established place. The authoring environment, runtime and current deployment package should be evaluated as separate implementation responsibilities. The assessment recognizes the named workflow proposition without inferring a measured reduction in handling time.

Boomi Flow

• Provider / operator: Boomi
• Headquarters: Conshohocken, Pennsylvania, United States
• Provider founded: 2000 (Boomi)

Boomi Flow provides workflow and application-flow design within Boomi’s integration portfolio. Its eligible scope is the named Flow product, with broader integration-platform capabilities used only where their relationship to the workflow is documented. A configurable workflow should preserve clear ownership as organizational rules change. Forms, routing and decisions are useful when colleagues can understand why a task reached them.

A team can connect an interactive flow with external APIs and business systems, preserving the relationship between user steps and the action performed by an integration. The Flow API-tool documentation identifies the named product’s connection to external services without borrowing unrelated capabilities from the wider Boomi platform. Boomi publishes Flow-specific API-tool and developer guidance. The implementation must identify who can alter the process and how existing work is treated when a configuration changes.

Its documented workflow-and-integration model supports recognition. The selected Flow environment and additional Boomi services must be specified directly. The product is recognized for its documented operating model, with implementation quality assessed separately.

Camunda

• Provider / operator: Camunda
• Headquarters: Berlin, Germany
• Provider founded: 2008

Camunda provides process orchestration connecting modelled workflows with application services and participating workers. Its product proposition centres on executable process coordination rather than a static diagramming tool. AI and agent interfaces add another possible participant to an automated process. Their value depends on the action taken and the authority surrounding that action.

A business can connect the definition of a process with the software or person performing each step, preserving a context for its execution and review. Process and worker coordination connect the executable model with the applications performing individual steps, making runtime responsibilities a concrete implementation question. Camunda maintains developer guidance and process-orchestration resources. A human review or approval needs a real place in the workflow rather than an unverified assumption that the output will be checked later.

Its clear orchestration architecture supports an established position. The runtime, worker implementations and operating responsibilities should be specified for the chosen deployment. The assessment follows documented process functions and does not treat agent branding as proof of autonomy or reliability.

Creatio Studio

• Provider / operator: Creatio
• Headquarters: Boston, Massachusetts, United States
• Provider founded: 2014 (current provider origins)

Creatio Studio provides no-code application and process design within Creatio’s enterprise platform. Its workflow role is evaluated separately from the separately packaged sales CRM and other business applications. Process design and process execution address different responsibilities. A visual model is useful when it corresponds to the tasks, events and records actually managed by the operating application.

A team can configure records, interfaces and a process that coordinates the tasks needed to complete an organizational request. Academy resources describe the underlying platform rather than crediting Studio with every function of Creatio’s separately packaged business applications. Creatio Academy documents platform development, integrations and implementation. Administrators need a route to inspect configuration and understand where a person must review or authorize a change.

Its connected application-and-process proposition supports recognition. The selected runtime, business applications and supported customization boundaries need explicit review. Recognition concerns the documented application environment, not a claim that every process can run unattended.

Nintex

• Provider / operator: Nintex
• Headquarters: Bellevue, Washington, United States
• Provider founded: 2006

Nintex provides workflow automation and orchestration through its maintained platform. Its eligible role is the continuing coordination of forms, tasks and business actions rather than document generation or process diagrams alone. A specialist workflow engine can provide substantial depth without including every office or business application. Its intended runtime and integration model should be explicit.

Teams can configure a workflow that connects a submitted request with assigned work and the systems involved in carrying it out. Workflow API and orchestration resources make the maintained process product inspectable beyond a diagram or an isolated document-generation capability. Nintex publishes current workflow APIs and orchestration guidance. The relevant evaluation connects the process definition with the application or worker that performs each step and records the result.

Its documented workflow depth supports an established position. The current product edition and any additional document or process-intelligence components should remain explicit. Recognition therefore concerns inspectable workflow provision rather than an assumed universal enterprise-suite scope.

Oracle Integration

• Provider / operator: Oracle
• Headquarters: Austin, Texas, United States
• Provider founded: 1977 (Oracle)

Oracle Integration connects application integration with workflow and human-in-the-loop functions. Its eligible process role is established through current workflow guidance rather than assuming every integration service is automatically a business-process platform. Integration-led automation coordinates work across applications that retain their own records and access controls. A connector catalogue does not itself establish a complete business process.

A configured integration can include a workflow step that returns an action or decision to a person before the larger process continues. Current human-in-the-loop guidance gives the workflow an explicit intervention point within an integration rather than leaving review as an informal afterthought. Oracle documents workflow addition and current integration APIs. The meaningful comparison follows the configured trigger, data mapping and action, including how failures or approvals return to the responsible team.

Its integration-to-human-task architecture supports an established position. Buyers should confirm the service version, human-task functions and connected application responsibilities. Its placement reflects an identifiable maintained orchestration environment, not the number of possible connections alone.

ProcessMaker

• Provider / operator: ProcessMaker
• Headquarters: Durham, North Carolina, United States
• Provider business origins: 2000 (business origins)

ProcessMaker provides a process-automation environment for forms, routing and business workflows. Its current combined provider relationship with Decisions is recognized, so Decisions is not counted as a second independent platform in this series. Automation becomes operationally meaningful when a trigger leads to a defined action and the organization can understand who remains responsible for its result.

Organizations can organize recurring requests and the people or system tasks needed to complete them within the configured workflow. Platform documentation and REST resources describe the current operating application, while the combined-provider relationship remains distinct from individual product functions. ProcessMaker publishes current platform documentation and REST interfaces. Interfaces should preserve the identity and meaning of the record being changed across the participating applications.

Its maintained process application model supports recognition. The evaluated ProcessMaker product and any combined-provider components must remain clearly identified. The product is evaluated for that maintained workflow capability, with deployment and subscription limits kept explicit.

SAP Build Process Automation

• Provider / operator: SAP
• Headquarters: Walldorf, Germany
• Provider founded: 1972 (SAP)

SAP Build Process Automation supports workflow design, forms, decisions and process automation within SAP Build. The named process product is evaluated separately from the wider development suite and from deprecated standalone application-builder offerings. A configurable workflow should preserve clear ownership as organizational rules change. Forms, routing and decisions are useful when colleagues can understand why a task reached them.

An organization can define a process and route business tasks or approvals while connecting the workflow to the relevant enterprise applications. The workflow-design material gives the process application its own technical scope within the wider SAP Build development and automation portfolio. SAP publishes product-specific workflow design and technical information. The implementation must identify who can alter the process and how existing work is treated when a configuration changes.

Its defined process environment and enterprise integration context support recognition. The actual Build services and subscriptions need to be identified for the proposed implementation. The product is recognized for its documented operating model, with implementation quality assessed separately.

TIBCO BusinessWorks

• Provider / operator: TIBCO / Cloud Software Group
• Documented TIBCO business location: Palo Alto, California, United States (TIBCO business)
• Product-provider business origins: 1997 (TIBCO business origins)

TIBCO BusinessWorks provides model-driven enterprise integration and orchestration using supported activities and application connections. The named BusinessWorks component is evaluated separately from TIBCO BPM Enterprise and unrelated analytics products. Automation becomes operationally meaningful when a trigger leads to a defined action and the organization can understand who remains responsible for its result.

Teams can coordinate services and data exchanges across enterprise applications using the configured integration processes and runtime. The current BusinessWorks component documentation preserves the distinction between integration-process orchestration and the separately maintained TIBCO BPM Enterprise product. Current BusinessWorks documentation identifies supported runtime components and release resources. Interfaces should preserve the identity and meaning of the record being changed across the participating applications.

Its developed integration-orchestration architecture supports recognition. BusinessWorks, BPM and other Cloud Software Group products must not be treated as interchangeable sources of functionality. The product is evaluated for that maintained workflow capability, with deployment and subscription limits kept explicit.

Workato

• Provider / operator: Workato
• Headquarters: Palo Alto, California, United States
• Provider founded: 2013

Workato connects enterprise integrations with automation and workflow applications. The named platform supports cross-system processes rather than functioning only as a library of connector descriptions. Integration-led automation coordinates work across applications that retain their own records and access controls. A connector catalogue does not itself establish a complete business process.

Organizations can configure recipes and workflow interfaces that coordinate data and actions across participating enterprise applications, with a defined place for user interaction. Workflow Apps adds an explicit user-interaction context to an integration-led platform, helping reviewers examine where a person participates in the automation. Workato publishes platform APIs and Workflow Apps resources. The meaningful comparison follows the configured trigger, data mapping and action, including how failures or approvals return to the responsible team.

Its integration-led orchestration scope supports an established position. The implementation should identify connected account permissions, exception handling and the applications owning each business record. Its placement reflects an identifiable maintained orchestration environment, not the number of possible connections alone.

---

Tier III — Specialist Business Workflow Automation Platforms

(Alphabetical order)

AuraQuantic

• Provider / operator: AuraQuantic
• Published US provider office: Miami, Florida, United States
• Provider-stated commercial origins: 2002 (provider-stated commercialization origins)

AuraQuantic provides business process automation and workflow orchestration through a configurable enterprise platform. The evaluated product supports an ongoing process environment rather than a single-purpose AI assistant or a consultancy project without software. A configurable workflow should preserve clear ownership as organizational rules change. Forms, routing and decisions are useful when colleagues can understand why a task reached them.

A business can connect a request and its information with a defined sequence of people, decisions and application actions. The dedicated orchestration offering identifies the workflow as an enterprise process, with support resources available for the resulting application environment. AuraQuantic maintains workflow-orchestration and support resources. The implementation must identify who can alter the process and how existing work is treated when a configuration changes.

Its clearly identified process-automation role supports recognition. The selected functions and current operator arrangements should be established for the actual deployment. The product is recognized for its documented operating model, with implementation quality assessed separately.

Bonita

• Provider / operator: Bonitasoft
• Headquarters: Paris, France (Bonitasoft)
• Provider founded: 2009 (Bonitasoft)

Bonita combines process execution with application interfaces and business data through Bonitasoft’s automation environment. The maintained Bonita platform is distinguished from a process-modelling-only utility. An enterprise workflow connects people, records and system actions across a continuing process. Its design must represent both the normal sequence and the decisions that interrupt it.

Teams can connect a process definition with forms, tasks and external application actions, making the relationship between the workflow and its business records inspectable. The REST and engine references expose different interaction routes with the maintained process runtime, with version and edition boundaries retained. Bonita publishes REST and engine API documentation. The useful review follows a request through assignment, authorization and completion, including a returned or rejected task.

Its documented process runtime supports recognition. Community and commercial capabilities should be evaluated according to the edition and deployment actually proposed. Its standing reflects documented orchestration and governance rather than an assumed automation benefit.

Flowable

• Provider / operator: Flowable
• Headquarters: Zurich, Switzerland
• Platform project established: 2016 (platform project origins)

Flowable provides process, case and decision capabilities within a maintained automation environment. Its enterprise offering is distinguished from the open-source engines and the operating responsibilities of applications built around them. Human tasks and system integration can participate in the same process without becoming the same operating responsibility. Their handoff should remain visible to an administrator.

A configured process can connect human work and application actions while retaining the business context represented by the workflow or case model. Enterprise and open-source documentation are separately scoped, preventing the presence of an engine API from establishing every commercial administration control. Flowable maintains enterprise and open-source developer documentation. Current technical guidance helps reviewers identify supported actions and the point at which another application becomes responsible.

Its inspectable process-engine architecture supports recognition. Edition-specific controls should be established from the corresponding enterprise documentation rather than inferred from an open-source API alone. Its contribution is considered within that documented scope rather than through a provider’s unrelated software portfolio.

Integrify

• Provider / operator: Integrify
• Headquarters: Chicago, Illinois, United States
• Provider founded: 2001

Integrify provides workflow management around requests, forms, routing and organizational approval processes. Its current application is distinct from advisory work performed to design a buyer’s internal procedure. Process design and process execution address different responsibilities. A visual model is useful when it corresponds to the tasks, events and records actually managed by the operating application.

A team can organize a recurring request and the task sequence needed to review or complete it, then connect the workflow with supported external application interfaces. Administrator and task-type resources connect the API with the workflow objects used to organize a recurring request and its review sequence. Integrify publishes administrator and REST API resources. Administrators need a route to inspect configuration and understand where a person must review or authorize a change.

Its defined request-and-approval operating model supports recognition. Current product versions and deployment arrangements should be confirmed instead of inferring them from a historical API example. Recognition concerns the documented application environment, not a claim that every process can run unattended.

Joget

• Provider / operator: Joget
• Published provider office: Columbia, Maryland, United States (US provider office)
• Provider business origins: 2009 (Joget business origins)

Joget combines visual application development and process automation through its maintained platform. Its current AI-related presentation is assessed through the underlying forms, records and executable workflow rather than the branding alone. Integration-led automation coordinates work across applications that retain their own records and access controls. A connector catalogue does not itself establish a complete business process.

Teams can build an application around a recurring process and connect the steps that users or integrations perform as a request moves forward. The platform guide connects application development with executable process work and identifies the maintained product rather than a consulting-only delivery model. Joget publishes a platform guide and enterprise support resources. The meaningful comparison follows the configured trigger, data mapping and action, including how failures or approvals return to the responsible team.

Its defined application-and-workflow model supports recognition. The intended hosting, edition and organizational administration responsibilities should be specified directly. Its placement reflects an identifiable maintained orchestration environment, not the number of possible connections alone.

Kintone

• Provider / operator: Cybozu
• Provider headquarters: Tokyo, Japan (Cybozu)
• Provider founding and product launch: 1997 (Cybozu); Kintone product from 2011

Kintone connects configurable business records with team applications and workflow management. Its product role combines shared operational data with a process rather than presenting a database or an approval notification in isolation. A specialist workflow engine can provide substantial depth without including every office or business application. Its intended runtime and integration model should be explicit.

Teams can organize records, status changes and the user actions used to move a request through a configured business workflow. The record-based application model gives workflow status and user actions a shared context rather than treating approval as a disconnected notification. Kintone publishes workflow, developer and implementation resources. The relevant evaluation connects the process definition with the application or worker that performs each step and records the result.

Its coherent record-centred process model supports recognition. The provider’s other groupware products are not automatically included in the evaluated application. Recognition therefore concerns inspectable workflow provision rather than an assumed universal enterprise-suite scope.

Kissflow

• Provider / operator: Kissflow
• Provider operating office: Chennai, India
• Provider business origins: 2003 (OrangeScape business origins)

Kissflow provides configurable business applications and approval-oriented workflows. Its process platform is assessed independently from the provider’s named procurement application and from advisory services around implementation. Workflow applications organize recurring work around a shared record and a defined sequence of responsibilities. They remain different from a one-off custom automation sold only as consulting.

A team can organize a request, form data and the approval or task sequence used to complete a recurring business process. The API and developer environment provide a route to examine how configured business workflows exchange information with connected applications. Kissflow maintains API and developer documentation. Users and administrators should be able to relate a request, its current state and the next action within the configured environment.

Its coherent configurable-workflow proposition supports recognition. Process ownership and the functions remaining in connected transaction systems should be established for the actual application. Its standing reflects that substantive software contribution at the research cutoff.

Laserfiche

• Provider / operator: Laserfiche
• Headquarters: Long Beach, California, United States
• Provider founded: 1987

Laserfiche connects forms, records and process automation within a broader information-management environment. Its eligible workflow role is evaluated separately from storing documents without a substantive business process. Workflow applications organize recurring work around a shared record and a defined sequence of responsibilities. They remain different from a one-off custom automation sold only as consulting.

An organization can route a request and associated information through tasks and supported integrations, keeping the action connected to the material used in the decision. The process-automation API guidance establishes a specific connection between a workflow action and an external application rather than content storage alone. Laserfiche documents calling external APIs from process automation. Users and administrators should be able to relate a request, its current state and the next action within the configured environment.

Its defined information-to-workflow relationship supports recognition. Content-management and workflow modules should be identified within their actual package and deployment boundaries. Its standing reflects that substantive software contribution at the research cutoff.

Make

• Provider / operator: Make / Celonis
• Headquarters: Prague, Czech Republic
• Product-business and brand origins: 2012 (Integromat origins); Make brand from 2022

Make provides visual cross-application automation through configured scenarios. The maintained Make platform is evaluated within its Celonis ownership context, without treating the owner’s process-mining functions as native Make capability. Workflow applications organize recurring work around a shared record and a defined sequence of responsibilities. They remain different from a one-off custom automation sold only as consulting.

Teams can connect triggers and application actions and use the documented enterprise human-in-the-loop component where an authorized decision must interrupt the automated sequence. The enterprise human-in-the-loop application makes subscription scope relevant to the review of approvals and intervention within a configured scenario. Make publishes current API and application documentation. Users and administrators should be able to relate a request, its current state and the next action within the configured environment.

Its clear visual integration workflow supports recognition. Human-in-the-loop availability and the responsibilities of connected services depend on the selected edition. Its standing reflects that substantive software contribution at the research cutoff.

n8n

• Provider / operator: n8n
• Headquarters: Berlin, Germany
• Provider founded: 2019

n8n provides configurable workflow automation connecting applications, data operations and current AI-related components. Its eligible platform coordinates general business processes rather than offering only one narrowly defined agent use case. AI and agent interfaces add another possible participant to an automated process. Their value depends on the action taken and the authority surrounding that action.

A team can build a sequence of connected operations and examine how data and actions move through the workflow in its chosen deployment. The documentation separates workflow design and API interaction from the operational responsibilities of a hosted service or a self-managed installation. n8n publishes current platform and API documentation. A human review or approval needs a real place in the workflow rather than an unverified assumption that the output will be checked later.

Its inspectable technical workflow environment supports recognition. Self-managed and hosted arrangements allocate operating responsibilities differently, and licensing should be reviewed for the actual intended use. The assessment follows documented process functions and does not treat agent branding as proof of autonomy or reliability.

Pipefy

• Provider / operator: Pipefy
• Headquarters: San Francisco, California, United States
• Provider founded: 2015

Pipefy organizes business processes through configured requests, records and workflow stages. Its current agent features are interpreted within that substantive process environment rather than as proof of unrestricted autonomous action. Human tasks and system integration can participate in the same process without becoming the same operating responsibility. Their handoff should remain visible to an administrator.

Teams can coordinate intake and recurring operational work while relating the current request state to the person or integration responsible for the next step. Agent orchestration guidance is interpreted through the configured process and its application actions, without inferring unrestricted autonomous access to external records. Pipefy maintains developer and orchestration documentation. Current technical guidance helps reviewers identify supported actions and the point at which another application becomes responsible.

Its defined request-and-process workflow supports recognition. Agent participation and connected system actions require explicit authority and operating boundaries. Its contribution is considered within that documented scope rather than through a provider’s unrelated software portfolio.

Quickbase

• Provider / operator: Quickbase
• Headquarters: Boston, Massachusetts, United States
• Product-business origins: 1999 (product-business origins)

Quickbase provides configurable applications and workflow automation around shared business records. Its eligible scope supports ongoing organizational processes rather than a spreadsheet template or one-off consulting-only automation. AI and agent interfaces add another possible participant to an automated process. Their value depends on the action taken and the authority surrounding that action.

A team can connect a record change with a supported automated action and relate the result to the people managing that business process. Current workflow and API guides give the shared application record a defined relationship to supported automation and connected system actions. Quickbase maintains current API and workflow guidance. A human review or approval needs a real place in the workflow rather than an unverified assumption that the output will be checked later.

Its coherent record-and-application operating model supports recognition. Legacy automation and current integration functions should be distinguished according to the product documentation and configuration. The assessment follows documented process functions and does not treat agent branding as proof of autonomy or reliability.

Tonkean Process Orchestration

• Provider / operator: Tonkean / Coupa
• Product-business location: San Francisco, California, United States (Tonkean business)
• Product-business origins: 2015 (Tonkean business origins)

Tonkean Process Orchestration provides enterprise intake and process orchestration across functions such as procurement, legal and IT. The current Coupa relationship is identified without duplicating a separately listed provider in this workflow series. Case-oriented work often requires a flexible sequence while preserving responsibility for the underlying business outcome. The platform must connect individual actions with that continuing context.

Organizations can coordinate a request across participating people, applications and agent components while preserving a place for review and the business decision behind the action. The provider describes orchestration across procurement, legal and IT, establishing broader process scope than an agent limited to one isolated use case. Current Tonkean material describes the maintained orchestration platform and its enterprise process scope. A practical evaluation includes incomplete information, an exception and a change after a task has already been assigned.

Its cross-functional workflow purpose supports recognition. Acquisition integration and the exact product package should be checked for the proposed deployment. The assessment recognizes the named workflow proposition without inferring a measured reduction in handling time.

Tray.ai

• Provider / operator: Tray.ai
• Headquarters: San Francisco, California, United States
• Provider founded: 2012

Tray.ai provides integration-led workflow orchestration with current agent-related platform functions. The evaluated software connects substantive application actions and business data rather than relying on an assistant interface alone. An enterprise workflow connects people, records and system actions across a continuing process. Its design must represent both the normal sequence and the decisions that interrupt it.

Organizations can manage workflows and connected application operations within the chosen platform configuration, retaining explicit responsibilities for external system changes. Workflow and platform API references identify how a configured automation can be inspected or managed within the selected Tray environment. Tray publishes workflow, embedded and platform API references. The useful review follows a request through assignment, authorization and completion, including a returned or rejected task.

Its documented cross-application orchestration model supports recognition. The platform services and any embedded deployment should be assessed through their actual permissions and operational boundaries. Its standing reflects documented orchestration and governance rather than an assumed automation benefit.

Zapier

• Provider / operator: Zapier
• Provider operating model and business base: Distributed organization; San Francisco, California, United States business base
• Provider founded: 2011

Zapier coordinates multi-application workflows through triggers, actions and supported integrations. Its general-purpose automation role is distinct from a bespoke one-off workflow supplied only by an external consultant. A specialist workflow engine can provide substantial depth without including every office or business application. Its intended runtime and integration model should be explicit.

A business can connect events and application actions and include an approval-related workflow where supported, making the intended sequence more explicit than a collection of manual handoffs. Approval-workflow material gives an example of a business decision within cross-application automation, alongside the maintained developer and API environment. Zapier maintains developer, API and workflow resources. The relevant evaluation connects the process definition with the application or worker that performs each step and records the result.

Its accessible integration-led operating model supports recognition. Task limits, connected-account authority and subscription-specific functions should be checked for the proposed process. Recognition therefore concerns inspectable workflow provision rather than an assumed universal enterprise-suite scope.

---

Remarks

Workflow automation is an operating relationship between a request, its current state and the next authorized action. A coherent platform makes that relationship understandable to participants and maintainable by the organization. The presence of a visual designer or a connector is useful evidence, but it does not replace the need for an identifiable executable process.

The tiers reflect weighted editorial assessments of documented workflow depth, enterprise utility, integration and controls, implementation resources and operating clarity. Focused platforms can provide substantial depth around requests, records or process engines. A lower-band offering may therefore fit an organization’s architecture more directly than a broader suite.

Provider facts distinguish product-business origins, company formation, current ownership and published operating locations where necessary. Combined providers are not counted twice within the series. Product documentation is interpreted within its actual scope: a sibling platform’s BPM functions, an open-source edition’s interfaces or a provider’s consulting services do not automatically establish the evaluated product’s capabilities.

Tier I is ordered, while Tiers II and III are alphabetical. Commercial licensing, sponsorship and badge interest affect no eligibility decision, score or tie resolution. Buyers should verify the required runtime, subscriptions, connected-account permissions, process-change responsibilities and support arrangements before applying the comparison to a production workflow.

---

Recognition

Inclusion in the Top 30 Business Workflow Automation Platforms 2027 ranking is an editorial determination of The Economy Rankings and does not require licensing, advertising, sponsorship, or other commercial participation.

Ranked organizations may factually refer to their inclusion in the ranking in their own communications. When describing the result, entities should accurately reflect the tier structure and methodology used in the published ranking.

How the ranking should be interpreted

• Tier I represents the Top 5 entities, and the published order within Tier I reflects the ranking order.
• Tier II represents entities ranked within the Top 15, following Tier I. Entities within Tier II are displayed alphabetically; their displayed order should therefore not be interpreted as an individual numerical ranking.
• Tier III represents entities ranked within the Top 30, following Tiers I and II. Entities within Tier III are also displayed alphabetically, and their displayed order should not be interpreted as an individual numerical ranking.
• An entity's tier, rather than its alphabetical position within Tier II or Tier III, should therefore be used when describing its standing.

Referencing the ranking

Depending on the entity's published tier, appropriate factual descriptions may include:

• Tier I: “Ranked Tier I” or “Ranked among the Top 5”
• Tier II: “Ranked Tier II” or “Ranked among the Top 15”
• Tier III: “Ranked Tier III” or “Ranked among the Top 30”

Entities should not describe an alphabetical position within Tier II or Tier III as a specific numerical rank.

Use of The Economy Rankings recognition materials

Editorial inclusion in a ranking does NOT by itself grant permission to use The Economy Rankings badges, seals, logos, official recognition graphics, licensed quotations, or other proprietary recognition materials.

Organizations wishing to use official The Economy Rankings recognition materials in corporate websites, marketing materials, investor communications, client presentations, social media, press releases, or other external communications should refer to the applicable licensing terms and usage policies:

• The Economy Rankings License Structure — available licence levels and permitted recognition uses
  The Economy Rankings License Structure | The Economy Rankings
• The Economy Rankings License Policy — licensing conditions governing use of The Economy Rankings recognition, marks, and related materials
  The Economy Rankings License Policy | The Economy Rankings
• Recognition Use Guide — guidance on permitted wording, presentation, attribution, and use of ranking recognition
  Recognition Use Guide | The Economy Rankings

Purchasing or holding a recognition-materials licence does not confer inclusion or a higher tier.

Recognized organizations may reference the designation in:

• corporate websites
• investor communications
• marketing materials
• client presentations

Licensing inquiries:
[email protected]