Test it before anyone depends on it
Run the automation in Sandbox against payloads you keep, and read what every step produced before a version goes anywhere near live traffic.
ArboRule Engine
Connect your apps, your database and your own APIs into a flow you can test, version and roll back — and open any run from months ago to see exactly what it did.
Free for 150 runs a month. No card, no sales call.
run_8f6b91lead routed to #leads1120 msOne tick is one run — and one billed run — however many steps it took.
Billed by run, not by step. Tested before it ships. Traced after it runs.
What you can build
This is the product canvas, not a diagram drawn for a landing page. Pick one and watch it run.
The parts
28 packaged providers, plus a Custom Connection for anything with an HTTPS endpoint and an API key.
When something breaks
A timeout, a 429, or any 5xx from the service you are calling is retried on a widening gap that spans a little over 24 hours. That is long enough to survive a maintenance window without hammering a service that is already struggling.
When the last attempt fails, your workspace admins get an email naming the endpoint, the event and the response code — once per endpoint per day, so a dead URL on a busy flow does not turn into a thousand messages.
Why it stays working
Most automation tools give you one live copy that everyone edits. That is fine until the automation matters — and then a Tuesday afternoon change is the reason Friday's orders never reached the warehouse.
Run the automation in Sandbox against payloads you keep, and read what every step produced before a version goes anywhere near live traffic.
Live traffic runs a published version. Editing the draft changes nothing that is running, so a half-finished change cannot leak into production.
Send a percentage of runs to the new version and the rest to the old one, or mirror live traffic onto a candidate in shadow mode and compare before you switch.
Every run keeps the version that served it, the path it took, and the value each step produced. Open run #8,412 from March and see exactly what happened.
Pricing
Tools that bill per step make you pay for how you built the automation. A run here is one execution of a published version, start to finish. Splitting a step in two does not change your bill.
1 run counted
150 runs / month
Unlimited testing in Sandbox on top of the allowance. No card to start.
1,000 runs / month
For the first automations a team actually depends on.
4,000 runs / month
For a workspace running its operations on these.
15,000 runs / month
For automations carrying real volume across several teams.
Above your allowance, runs keep going at US$ 10 per 1,000 runs — nothing pauses, nothing queues, and no automation stops mid-month.
Coming from somewhere else
There is no importer for another vendor's file format, and we are not going to pretend otherwise — you rebuild the automation here. That takes an afternoon for most of them, and it is the only honest way to end up with something you can test and version.
If you already have ArboRule flows somewhere, those import directly, versions and subflows included.
Before you start
One run is one execution of a published flow version, from the trigger to the last step. A flow with three steps and a flow with thirty each count as one run, and a branch that is not taken costs nothing. Sandbox runs and live runs draw from the same monthly allowance, so there is one number to watch.
No. ArboRule Engine is priced on runs, not seats. Everyone who touches the automation — whoever built it, whoever operates it, whoever gets paged when it fails — works in the same workspace without changing what you pay.
Three things. An HTTP call to the flow's own endpoint, which returns the result in the response. An Inbound Webhook node, which gives you a URL to hand to another service. Or a scheduled job, which reads rows from a database, an S3 bucket or an uploaded file and runs the flow over each one on the schedule you set.
Outbound deliveries are retried six times on a widening gap — immediately, then after 5 seconds, 30 seconds, 5 minutes, 1 hour and 23 hours — which spans a little over a day in total. If the last attempt still fails, your workspace admins are emailed with the endpoint, the event and the response code, throttled to one message per endpoint per day.
Yes. There are 28 packaged providers, and a Custom Connection speaks any HTTPS or JSON API you have credentials for. Six databases connect directly: Postgres, MySQL, Snowflake, BigQuery, Redshift and MongoDB.
Yes, and that is the point of the product. Build and run it in Sandbox as many times as you like, read what every step produced, then publish a version when it is right. Live traffic only ever runs a published version, so editing a draft cannot change what is already running.
Most of the category gives you one live copy of an automation that everyone edits, and a run log that answers whether it succeeded. ArboRule Engine gives you versions you publish, a sandbox you test in, traffic you can move a slice at a time, and a stored trace for every run showing the exact path and the value each step produced. If your automations are small and rarely change, that machinery is overhead you do not need.
Start with one
Create a workspace, wire up the automation you already worry about, and let the run tape tell you whether it is behaving.