Business workflow automation, built on real code.
Every workflow in Archestack is a script that fires on an entity event. Create an invoice, AfterCreate runs. Update a customer's credit limit, BeforeUpdate runs. The scripts are real C#, version-controlled, debuggable. Not a tangle of arrows on a canvas.
Triggers, not no-code spaghetti.
Visual workflow tools have a place for very simple cases. They fall apart the moment the workflow needs a branch the canvas can't express, an external API call the connector library doesn't support, or a state machine that loops back on itself.
Archestack picks the other model. Workflows are scripts. They take typed entity context as input, they run real C#, they return a result. If/else and loops are if/else and loops, not boxes. Source control sees them as code, not an opaque blob.
What you can wire up.
Validation that says no
BeforeCreate / BeforeUpdate triggers can block the operation. Customer over their credit limit? The trigger throws a friendly error and the user never sees a half-saved invoice.
Side-effects on save
AfterCreate / AfterUpdate runs once the database commits. Send the confirmation email, push the order to a 3PL's API, enqueue the PDF job. All transactional with the save.
Recompute derived state
An invoice line changes, the header's total recalculates. A stock movement lands, the location's available count updates. Triggers keep the derived rows honest without nightly batch jobs.
External integrations
The script has full access to .NET. HttpClient, the database, queues, anything. Wire to Stripe, Mollie, your accounting system, a route-optimization API, whichever shape the integration needs.
How it compares to Zapier / Make.
Tools like Zapier and Make sit between two systems and shuttle records across. They're good at that. Archestack workflow automation sits inside your system and runs when your data changes. Different layer.
Because the triggers run in-process against your database, they're transactional, fast, and have no per-zap pricing model. They also handle the workflows the integration tools can't: validation that needs to block a save, recomputation that needs to happen synchronously, business rules that need to know about three related entities at once.
Try the workflow engine.
Free 7-day trial. Hook a script to an entity, watch it run on the next save.