Most of us here have written the same glue script more than once, the one that catches a form submission and pushes it somewhere else, then quietly rots in a cron job nobody documented. This is a look at an open source engine that gives that glue a proper home on your own server, written for anyone who has priced a hosted automation tool and done the math.
What It Actually Is
Workflow Chain Engine is a visual workflow automation engine you host yourself. You draw a flow in the browser, call an API, branch on the answer, loop over a list, and end in success or fail. The whole system is one small PHP application with a single SQLite file. No framework, no build step, no dependency install, and the editor library ships inside the project, so nothing is loaded from a CDN at runtime.
That constraint is the interesting part. It means the tool is at home on a three dollar shared host, a VPS, or a Docker container, which matters when the process you are automating is worth ten dollars a month rather than two hundred.
The Parts That Matter in Practice
Six node types cover the logic you need: calling out, branching, looping, and terminating in a success or fail state. Variables carry data between steps, so the response from one API call is available to the next node without writing any glue of your own to move it there.
Triggers come in four flavors: a webhook, a schedule, a call from your own code, or a button someone clicks. That last one is underrated. A lot of internal automation is really a task somebody runs by hand at an unpredictable time, and handing that person a button beats handing them a runbook.
The Run Log Is the Feature
Every run leaves a step by step log you can actually read. That sounds mundane right up until you have debugged a hosted automation whose entire error report was the phrase workflow failed. Knowing which node fired, what it received, and what it returned is the difference between a five minute fix and a lost afternoon.
Loop protection is built in as well, which is the other thing you want in place before you point a webhook at something capable of calling itself.
Worth a Look If
You are already self hosting the database and the object storage but still renting the glue. The code is MIT licensed and on GitHub, so the cost of finding out is one afternoon.