This blog post provides describes how to invoke orchestration processes and provides examples of things that can invoke orchestration processes with the Orchex Enterprise Orchestration Engine.
Update 15.Dec.2025: After years of frustration with WordPress, I am finally abandoning this blog. The content will likely stay here for some time, but new content will appear here:
A single Rust API, the invoke_processor() function of the Processor struct, implements the orchestration process. Rust code can call this method directly, which is how the invoke_processor() JavaScript function calls out to Rust to invoke processors, sending the orchestration context that was passed to JavaScript to another processor in Rust. The scheduling engine also calls the invoke_processor() method, in this case without information from an HTTP request.
Most orchestration processes begin with a webservice API call inbound to Orchex. In this case, routing leads to the invoke_orchestration_process() function in the Process struct, which creates an orchestration context using information from the HTTP request and calls the invoke_processor() function.
Assuming the Orchex server is exposed publicly, anything connected to the Internet can invoke the webservice API that initiates an orchestration process. This can include:
Clients
Developers often use tools such as curl and Postman. For HTTP GET APIs, you can even use a browser (you can use a browser for POST too, if you are working with a form or it’s worth implementing one to work with the API).
Solutions
A common use case for an enterprise orchestration engine is to implement a backend-for-frontend (BFF) for a digital experience management solution, which is basically a dynamic modern website. Clients including browsers and native mobile apps can invoke Orchex APIs directly.
Webhooks
You can configure webhooks in other systems to invoke orchestration processors, whether by using the default Orchex route to invoke an orchestration processor or by defining a custom route.
Scheduled Processes
Orchex scheduled processes invoke orchestration processes.
Orchestration Processors
Orchestration processors can invoke the Orchex webservice APIs to invoke other processors, which can make reusable chains of processors.
Enterprise Message Bus and Event Systems
An EOE can provide a facility for composable applications to interact with enterprise message bus and event systems.
Anything Else
Considering technical opportunities such as the Internet of Things (IoT), the potential use cases for an orchestration engine are virtually unlimitted.
deliverystack.net 
3 thoughts on “-What Invokes Orchex Orchestration Processes?”