Workflow automation, with and without AI

Describe the workflow.Have it running.

No integration platform to wire by hand, no engineer to wait on. Say the job in one sentence and watch it start running — faster than you'd finish explaining it to a consultant.

~2 minutes to a built workflow34M rows of reference data, as a step175+ live event sources0 cost for steps that don't call a model

What makes it different

Try it here — no account, nothing to install

Open a workflow. Or say one, and watch it build.

Pick a ready-made workflow and it opens on the canvas at once. Or write a sentence about the job and watch the trigger, the steps and the links arrive while you wait. Drag the blocks, open one to change its settings — and keep what you made.

or describe your own

Ideas to start from

How it goes.

Say what you want done

"When an order is paid, raise the invoice, drop the stock, and text the customer a tracking link the moment it ships." Plain words. No template to pick, no blank canvas to stare at.

It is built, in about two minutes

Back comes a real workflow: every step, every branch, every wait, and the connections it needs. Not a suggestion and not a diagram — the actual thing, ready to be opened.

Set it up, then switch it on

You go through it, connect your accounts, change the wording, move a wait from two days to one, simulate a run to see exactly what it would do — and turn it on. It works like a charm from then on.

How the two minutes actually work

Why this one, and not the others

Everything they connect to,
plus a platform they do not have.

castomFLOW does what Make, Zapier and n8n do: it connects your apps and moves work between them over ordinary HTTP. Then it adds something none of them can offer, because none of them owns one — a whole platform of its own, sitting behind the same step picker.

See the steps nobody else has

Thirty-four million rows of reference data, as a step

Countries, currencies, languages, 13.4 million populated places and geographic features, 19 million name variants, two million postal codes, airports, seaports, vehicle makes. In every other tool that is a paid third-party integration with a key and a quota. Here it is a step you drop in.

Validate an address against real postal data. Turn "Kraków" into coordinates and a timezone. Check a currency code before it reaches your accounts package. None of it needs an account, because it is the same platform your workflow already runs on.

Enrich contactcastomAPI data

1Input"ul. Powstańców Śląskich 5, 53-332 Wrocław, PL"
2Postal code matched18 ms53-332 → Wrocław, Dolnośląskie, PL
3Place resolved22 ms51.0938 N, 17.0226 E · Europe/Warsaw · population 674,079
4Written backSix fields filled that a person would otherwise have typed.

No API keyNo per-lookup charge

What is going on in the world, as a trigger

A live worldwide events feed — concerts, festivals, expos, sports fixtures, conferences — sitting beside earthquakes, flood warnings, air-quality bands, aviation delays and service outages. More than 175 sources, refreshed every ten to twenty minutes, each carrying its licence and attribution.

So a workflow can start because something happened out there, not only because something happened in your database. A red weather alert in a region where you have crews. A festival announced in a city where you have three venues. An outage at a provider you depend on.

When an alert appearscastomAPI events

⚡TriggerCategory alert, country PL, severity "Severe"
2ConditionDo we have crews inside the affected voivodeship? Yes — 14.
3Quiet hoursOverridden for severity Severe. This one wakes people on purpose.
4Send SMS05:1214 messages, delivery states tracked, one vocabulary.

Polled every 10–20 minPrice and severity kept honest

Pictures, video and audio, licensed and attributed

A royalty-free media library that searches eleven providers at once, imports what you pick, and keeps the licence and the attribution attached to the file rather than in somebody's memory.

Which matters the moment a workflow is producing something people will see: a post, a page, a newsletter, a printed sheet. The picture arrives with its credit line already written, and the credit line is generated from the same record the picture came from — so it cannot go stale.

Fetch an imagecastomAPI media

1Search"autumn market stall" — eleven providers, one result set.
2ImportStored locally. Licence: CC0. Author and source URL recorded.
3UseDropped into the post the next step publishes, credit line included.

Eleven providersAttribution travels with the file

Send, book, charge, shorten, notify — from inside the flow

The rest of the platform is on the same shelf: e-mail, SMS and push delivery with one shared event vocabulary; booking slots; payments; short links with counted redirects; a company-lookup service; a chatbot; dashboards. Each of them is a step, authenticated by the same account, with no integration to maintain.

You can still call anything else you like over plain HTTP — most workflows do both.

On the same shelfOne account

✉SendE-mail, SMS, push and printed letters, with delivery events.
📅BookOffer a slot, hold it, confirm it, put it in a calendar feed.
€PayTake a payment, watch for the webhook, continue the run.
↗LinksShort link per recipient, redirects counted, no tracker in sight.

No keys to rotateNo integration to keep alive

With AI, without AI, or both

Most steps should not think,
and that is the point.

Automation tools have started reaching for a model on every step, because that is what they are selling. It is the wrong default for most work: a reconciliation, an invoice, a nightly export do not need judgment — they need the same thing to happen the same way, every time, for a tenth of a penny.

Deterministic steps

Fetch, transform, branch, wait, write, send. Same input, same output, always. Fast, free to run, and dull in the way infrastructure should be dull.

AI steps

Classify this, draft that, summarise, choose between three options. Structured input in, structured output out — never left to freelance beyond the shape you defined.

One workflow, both kinds

A single flow moves between them freely. The task decides which parts think and which parts simply run — and you only pay for the ones that think.

Every trigger, action and flow step

Use cases

Seven shapes of work.
Built for every one.

Every one of these is a workflow somebody describes in a sentence and has running before the coffee goes cold.

E-commerce

Order to invoice to shipping notice. Abandoned baskets. Stock warnings before the shelf is empty. Returns that do not need a person to start them.

Marketing

A brief becomes copy, the copy gets a licensed picture, the post goes out on schedule, and the numbers come back into a report that writes itself.

Operations

The nightly reconciliation. The document that has to reach four systems. The approval that has been sitting with somebody for three days.

Reference data

Validate, normalise and enrich anything with an address, a country, a currency, a language or a place name in it.

Events & alerts

Start a workflow because of something happening in the world — a severe weather alert, a fixture, an outage, a festival.

Agencies

Build a workflow once, run it for thirty clients with thirty sets of credentials, and hand each of them a report they can read.

All use cases, in detail

When it matters

Edit a live workflow.
Nobody inside it notices.

A run walks the version it entered on. You can rewrite a workflow while ten thousand contacts are halfway through it, and every one of them finishes the flow they started — which is exactly the thing that goes wrong in tools that materialise the whole downstream at entry.

Simulate before you publish

Dry-run a real record through the workflow and read back the exact path it takes and every message it would send. Nothing leaves the building.

Retries that cannot double-send

A step is a pure function of its inputs, and its effects commit with the run's own advance. A worker killed mid-step resumes without sending anything twice.

A log you can actually read

Every run, every step, every branch taken and why, with the values that decided it. When somebody asks what happened on the fourteenth, there is an answer.

How runs are kept honest

Part of one ecosystem, and useful on its own

castomFLOW is the workflow engine of the castomo family. castoMIND drives it to build and run the products it assembles; dash-b puts the numbers a workflow produces on a board; iKonekt hands it conversations; clickSomo hands it campaigns. One account signs into all of them, and one wallet pays for all of them.

None of which you need in order to use it. Plenty of workflows here never touch anything but a customer's own systems over HTTP — the platform is there when it is the shortest path, and out of the way when it is not.

The honest comparison: if all you need is "when a row is added to a spreadsheet, post to a channel", every tool in this category will do that, including this one. The reason to be here is the second half of the job — the address that needs validating, the picture that needs a licence, the alert that needs watching, the message that needs sending, and the report somebody needs on the first of the month.

Tell us the task.
We will show you the workflow.

Usually with a screenshot of it running, because that is faster than a paragraph about it.

Open castomFLOW Try the demo Talk to a person