Workflows · ontology/workflows/

Workflows: the routine work, done on time, by the rules.

Workflows run the routine work of the company on their own: every morning, after a record changes, or when another service calls. They work through the same records, actions and permissions as your team, can hand work to the company agent, and keep a history of every run.

One workflow as a map read from its code: what starts it, each step with what it reads and calls, and what happens when a step fails.

segmentstream.com
One workflow in the console, drawn as a map from its code: the daily bookkeeping, started each weekday at 09:00 UTC, its steps in order with the records each reads, what happens when a step fails, and its runs below

Routine work, done without anyone remembering to do it

Each one runs as its own user, under the same rules as your team, and reports to a person in the team’s chat when a decision is needed.

  • Every morning at 07:00

    Reconcile the books

    Matches yesterday’s bank transactions to invoices and bills, and posts the three that don’t match to #finance with a suggested fix.

  • Weekdays at 08:00

    Follow up on leads

    Finds the leads nobody has followed up for three days and asks each owner in their chat whether to send the drafted follow-up.

  • When a deal is won

    Prepare the contract

    Drafts the contract from the deal and the client’s record, attaches it, and asks finance to approve before it goes out.

  • When an email arrives

    Sort the inbox

    Reads each new message to the shared inbox, files it on the customer’s record and flags the ones that need a reply today.

  • Every Sunday night

    Clean the CRM

    Merges duplicate companies and contacts, fills missing fields from your connections and lists what it could not resolve.

  • When Stripe calls

    Record a payment

    Records the payment against the invoice, updates the client’s balance and thanks them from your own domain.

Triggers: schedule, record change, webhook

A workflow starts on a schedule, after an action changes a record (a deal is won, an invoice is approved), or when another service calls it: a payment, a form, a webhook.

Runs under your rules

Each workflow runs as its own user with its own role. Every step goes through the same actions and permission checks as a person, and history names the workflow.

Durable runs you can inspect

Steps are durable: a failed step is retried on its own, waits can last days, and every run and step is recorded in the console.

Agents inside the workflow

A step can ask a model to read, classify or draft, or hand the work to the company agent, which reports back or asks a person in the team’s chat when a decision is needed.

Start one when you need it

Members with the right role start a workflow from the app, the CLI or their AI tool, and read its runs.

In code

ontology/workflows/
// ontology/workflows/remind-stale-leads.tsexport default workflow("remindStaleLeads", {  description: "Remind owners of leads nobody touched for 3 days.",  role: "reminders",  input: Schema.Struct({ olderThanDays: p.integer({ min: 1, max: 90 }) }),  run: remindStaleLeads,  triggers: [    cron("weekdayMorning", "0 8 * * 1-5", { input: { olderThanDays: 3 } }),  ],});
Ontology SDK reference →

Use it, build on it, or have it built

Use it

Runs, steps and their results are in the console; members start the ones their roles allow.

Build it with your agent

Your coding agent writes a workflow in ontology/workflows/ and its trigger; the deploy checks it and it starts running.

Have our engineers build it

Our engineers map your routine work into workflows with you during a pilot.

Replaces Zapier and Make scenarios outside your system, Cron jobs on someone’s server and Reminders in a spreadsheet.

Works with

Solutions built with it

Read more

Enterprise pilot

Start a pilot.

Want workflows set up for you? Our forward-deployed engineers build it with you in your workspace, as code you own.

  • One solution, on your data, in your own workspace
  • First version live in two weeks
  • Parity proven before anything is switched off
  • Fixed scope and price, credited to your contract if you continue

Not ready for a pilot? Send the form anyway with your question. An engineer will reply, not a sales rep.

How the pilot works

Goes to our founder’s inbox. No sales queue, no newsletter.

Build your company’s own software. Let agents run it.

$ segmentstream workspace create acme --region eu --subdomain acme

▸ Created workspace acme · database, warehouse and a private git repository

$ segmentstream workspace WORKSPACE-ID clone acme && cd acme

▸ your coding agent builds what your team asked for and runs the checks

$ git add -A && git commit -m "First version"

$ segmentstream deploy

▸ app, company agent, API and MCP tools live for your invited members

Start a pilot

Our engineers build the first version on your data in two weeks, at a fixed price.

Or build it yourself with your coding agent:

curl -fsSL https://segmentstream.com/install.sh | sh

We’ll email you product updates, tips and onboarding help. Unsubscribe anytime.