Ticket intake
A single workflow composes seven workers — read the inbox, classify the request, validate the fields, apply the routing rule, persist to your database, request human review, send the reply.
Workers
Twelve families of reflexes. Compose what you need.
The atomic units of Sommatic — AI, IO, integrations, identity, flow control, ops, triggers, code, HITL. The building blocks for everything your operation does.
What it is
Workers are the atoms of the cognitive layer. Each one does one thing — classify an email, push a row to Postgres, request a human approval, fire a webhook — and does it reliably, with evidence and governance built in.
You don’t write workers from scratch; you compose them. Pick the ones you need, wire them together inside a workflow, and you have a reflex your operation can run forever — the same way, every time.
And when you do need something custom, write your own worker in JavaScript, Python or shell. It shows up next to the built-in catalog like it always belonged there.
What you get
- Twelve families across the catalog
- Deterministic and observable by default
- Custom workers in JS, Python or shell
- Drop-in connectors to the systems you already run
What this looks like in practice
Refund agent
An agent calls four workers in sequence — look up policy, verify identity, gate by amount, run the refund sub-workflow. The same building blocks, recomposed for a new job.
Your custom worker
A short Python script that calls your legacy mainframe. Drop it in. Reuse it across every workflow that needs it. No special treatment.