Workflow automation, with AI and without AI
Describe di workflow. Make e dey run.
No integration platform wey you go wire by hand, no engineer wey you go wait for. Talk the job in one sentence and watch am start to run — e go pass how you for finish explain am to one consultant.
~2 minutes to get one workflow wey don build34M rows of reference data, as one step175+ live event source dem0 cost for steps wey no call any model
Try am here — no need account, nothing to install
Open one workflow. Or talk am, come watch as dem dey build am.
Pick one ready-made workflow and e go open on di canvas sharp sharp. Or write one sentence about di work come watch di trigger, di steps and di links dey come as you dey wait. Drag di blocks, open one to change im settings — and keep wetin you make.
or describe your own
Ideas wey you fit start from
How e dey go
Talk wetin you want make dem do
"When order don get payment, raise the invoice, reduce the stock, and text the customer tracking link the moment e ship." Plain words. No template to pick, no blank canvas to dey look.
Dem don build am, inside like two minutes
Wetin come back na real workflow: every step, every branch, every wait, and the connections wey e need. No be suggestion and no be diagram — na the real thing, ready to open.
Set am up, then switch am on
You go check am, connect your accounts, change the wording, move one wait from two days to one, simulate one run to see exactly wetin e go do — and turn am on. E go dey work well well from dat time.
Why dis one, and no be the others
Everything wey dem connect to, plus one platform wey dem no get
castomFLOW dey do wetin Make, Zapier and n8n dey do: e connect your apps and move work between dem over ordinary HTTP. Then e add something wey none of dem fit offer, because none of dem own one — one whole platform of e own, dey sit behind the same step picker.
Thirty-four million rows of reference data, as one step
Countries, currencies, languages, 13.4 million populated places and geographic features, 19 million name variants, two million postal codes, airports, seaports, vehicle makes. For every other tool, na paid third-party integration with key and quota. Here, na step wey you just drop in.
Validate address against real postal data. Turn "Kraków" into coordinates and timezone. Check currency code before e reach your accounts package. None of am need account, because na the same platform wey your workflow already dey run on.
Enrich contactcastomAPI data
- 1Input"ul. Powstańców Śląskich 5, 53-332 Wrocław, PL"
- 2Postal code match53-332 → Wrocław, Dolnośląskie, PL
- 3Place resolve51.0938 N, 17.0226 E · Europe/Warsaw · population 674,079
- 4Dem don write am backSix fields wey dem don fill wey one person for don type by hand.
No API keyNo charge per lookup
Wetin dey happen for world, as trigger
Live feed of events wey dey happen all over world — concerts, festivals, expos, sports matches, conferences — dey sit beside earthquake, flood warning, air-quality level, flight delay and service outage. Pass 175 sources, dem dey refresh am every ten to twenty minutes, each one carry im licence and attribution.
So one workflow fit start because something happen out there, no be only because something happen inside your database. Red weather alert for region wey you get crews. Festival wey dem announce for city wey you get three venues. Outage for provider wey you dey depend on.
When alert show upcastomAPI events
- ⚡Wetin dey start amCategory
alert, country PL, severity "Severe" - 2ConditionWe get crews inside the affected voivodeship? Yes — 14.
- 3Quiet timeDem override am for severity Severe. Dis one dey wake people on purpose.
- 4Send SMS14 messages, dem dey track delivery states, one vocabulary.
Dem dey poll am every 10–20 minPrice and severity dem keep am honest
Pictures, video and audio, wey get licence and attribution
Royalty-free media library wey dey search eleven providers at once, import wetin you pick, and keep the licence and attribution attach to the file instead of inside person memory.
E matter the moment one workflow dey produce something people go see: post, page, newsletter, printed sheet. The picture arrive with im credit line already written, and the credit line dem generate am from the same record wey the picture come from — so e no fit go stale.
Fetch one imagecastomAPI media
- 1Search"autumn market stall" — eleven provider dem, one result set.
- 2Bring enterDem store am locally. Licence: CC0. Author and source URL dem record am.
- 3Use amDem drop am inside the post wey the next step go publish, credit line included.
Eleven providersAttribution dey travel with the file
Send, book, charge, shorten, notify — from inside di flow
The rest of the platform dey the same shelf: e-mail, SMS and push delivery with one shared event vocabulary; booking slots; payments; short links with counted redirects; company-lookup service; chatbot; dashboards. Each one of dem na step, dem authenticate am with the same account, and no integration to maintain.
You fit still call anything else you like over plain HTTP — most workflows dey do both.
For the same shelfOne akount
- ✉Send amE-mail, SMS, push and printed letter dem, plus delivery event dem.
- 📅BookOffer one slot, hold am, confirm am, put am inside calendar feed.
- €PayTake one payment, watch for the webhook, continue the run.
- ↗LinksShort link per recipient, dem dey count redirects, no tracker anywhere.
No key wey you go rotateNo integration to keep am alive
With AI, without AI, or both of dem
Most steps no suppose think, and na that be the point
Automation tools don start to reach for model on every step, because na wetin dem dey sell. Na the wrong default for most work: reconciliation, invoice, nightly export no need judgment — dem need make the same thing happen the same way, every time, for one-tenth of penny.
Deterministic steps
Fetch, transform, branch, wait, write, send. Same input, same output, always. Fast, free to run, and dull the way infrastructure suppose dull.
AI steps
Classify dis one, draft dat one, summarise, choose between three options. Structured input go in, structured output go come out — e no go ever waka pass di shape wey you define.
One workflow, di two kinds
One single flow dey move between dem freely. Na di task go decide which part go think and which part go just run — and you go only pay for di ones wey think.
How dem dey use am
Seven shapes of work wey dis one build for
Every single one of dem na workflow wey somebody go describe in one sentence and e don dey run before di coffee cold.
E-commerce
Order to invoice to shipping notice. Abandoned baskets. Stock warning before shelf empty. Returns wey no need person to start am.
Learn moreMarketing
Brief go turn copy, di copy go get licensed picture, di post go go out on schedule, and di numbers go come back inside report wey write imsef.
Learn moreOperations
Di nightly reconciliation. Di document wey suppose reach four systems. Di approval wey don dey sit with somebody for three days.
Learn moreReference data
Validate, normalise and enrich anything wey get address, country, currency, language or place name inside am.
Learn moreEvents & alerts
Start workflow because of something wey dey happen for di world — severe weather alert, fixture, outage, festival.
Learn moreAgency dem
Build one workflow once, run am for thirty clients with thirty sets of credentials, and give each of dem report wey dem fit read.
Learn moreWhen e matter
Editing live workflow no go disturb anybody wey already dey inside am
A run go follow di version wey e enter on. You fit rewrite workflow while ten thousand contacts dey halfway inside am, and every one of dem go finish di flow wey dem start — na exactly di thing wey dey spoil for tools wey materialise di whole downstream at entry.
Simulate am before you publish am
Dry-run one real record through di workflow and read back di exact path wey e take and every message wey e go send. Nothing go leave di building.
Retries wey no fit send two times
A step na pure function of im inputs, and im effects commit with di run own advance. Worker wey die mid-step go resume without sending anything two times.
Log wey you fit actually read
Every run, every step, every branch wey dem take and why, with di values wey decide am. When somebody ask wetin happen on di fourteenth, answer dey.
Part of one ecosystem, and e useful on im own
castomFLOW na di workflow engine of di castomo family. castoMIND dey drive am to build and run di products wey e assemble; dash-b dey put di numbers wey workflow produce on board; iKonekt dey give am conversations; clickSomo dey give am campaigns. One account go sign into all of dem, and one wallet go pay for all of dem.
You no need any of dem to use am. Plenty workflows here no dey touch anything except di customer own systems over HTTP — di platform dey there when e be di shortest path, and e dey comot for road when e no be am.
Di honest comparison: if all you need na "when dem add row to spreadsheet, post to channel", every tool for dis category go do am, including dis one. Di reason to dey here na di second half of di job — di address wey need validation, di picture wey need licence, di alert wey need watching, di message wey need sending, and di report wey somebody need on di first of di month.
Tell us di task. We go show you di workflow.
Usually with screenshot of am dey run, because dat one fast pass paragraph about am.