SCYTIAN
Menu

PLATFORM / AUTOMATIONS & CONNECTIONS

You write one sentence. The whole process appears.

Not a canvas you have to wire by hand. Steps, branches, exceptions and every system it touches, built from the words you already use. Watch it happen below.

Get your agent
Operations{{ status }}
CHAT

{{ typed }}

Got it. Here is the process, step by step. Tell me if anything is off.

{{ r.label }}{{ r.cond }}
ApproveChange
Message Operations…

{{ foot }}

HOW THE PROCESS GETS BUILT

Five things happen before it touches anything of yours.

Writing the sentence is the easy half. This is the half that decides whether it holds up, and it is the same every time.

01

The connections get sorted

What has to be reachable, how we get in, what is missing.

our problem, not yours
CONNECTIONSwhat has to be reachable
Shared mailboxconnected · IMAPorders arrive here
Company registerconnected · public APIcredit check
QuickBooksconnected · your keycustomers, invoices, stock
Production sheetshared with usGoogle Sheets
Transport portalbooks by e-mail insteadno API
usually the slowest part · our problem, not yours · you hold the keys
02

You get the plan

Every step, every field, every decision, and what will never happen, in plain language.

the only step that waits for you
THE PLANwaiting for you
1Order comes in: reads customer, items, delivery address
2Check the customer: in the register; bad credit → stop and ask you
3Split into deliveries: by stock; out of stock → order from supplier, tell customer new date
4Production told · transport booked
⊘Never ships to a customer with bad credit
⊘Never books transport twice for one delivery
ApproveRequest changes
no code is written before this
03

The script gets written

Rules, not guesses. Whatever can be a rule is a rule. That is what makes a run cost nothing.

0.00 € per run
THE SCRIPTrules, not guesses
whenan order arrives in the mailbox
readcustomer · items · address · requested date
checkcompany ID in the register → credit rating
ifrating below B → stop, ask you, keep the order on hold
splititems by warehouse stock → deliveries
ifitem out of stock → supplier order + new date to customer
writeproduction sheet · one row per delivery
sendtransport order by e-mail, PDF attached
deterministic · same result every time · runs in 0.4 s · 0.00 € per run
04

It gets reviewed

Against a checklist of the ways integrations break in practice. Money is checked twice.

independently
REVIEWbefore it goes live
Same order arriving twicehandled: one order, one set of deliveries
Register down or slowretries, then holds the order and tells you
Customer name spelled differentlymatched on company ID, never on the name
Amounts and currencieschecked against the order line by line
Transport e-mail bouncesyou are told the same hour
Money is touchedsecond, independent review
a checklist of the ways integrations break in practice · 6 of 6 passed
05

It runs where you can see it

Every run in the Timeline: what arrived, what each step did, what it cost.

watch mode first, live when it scores
TIMELINEbig orders · first week
Tue 08:12Order 1189 · 3 deliveries · transport booked0.6 s
Tue 10:40Order 1190 · out of stock → supplier ordered, customer told0.7 s
Wed 09:05Order 1191 · bad credit → on hold, asked youwaiting
Wed 09:31Order 1191 · you approved · shipped1 tap
Thu 07:50Order 1192 · 1 delivery0.4 s
what arrived · what each step did · what it cost · nothing happens off-screen

Monday you said it. Monday afternoon you approved the plan. Tuesday it ran in watch mode on your own files. It went live the day it scored. That is the usual pace.

WHEN IT RUNS

Five ways it starts. The same process every time.

What sets it off is decided in the plan, not left to chance, and more than one can be switched on at once.

TRIGGERSfive ways in · one process
Something arrivesan invoice · a form · a file
On a scheduleevery 15 min · 06:00 · 1st of month
Another system callsyour shop · CRM · software
A record changesa deal moves · a status flips
You just askin the chat · once
more than one can be switched on at once · decided in the plan, not left to chance

WHAT IT CONNECTS TO

If your company pays for it, it can be part of a process.

No catalogue of connectors to wait for. These are the ones already running. The list grows with every customer.

Accounting & ERP
QuickBooksSageZoho BooksDynamics 365SAPOdooXeroand more
CRM & sales
PipedriveHubSpotSalesforcePodioand more
Tables & databases
AirtableGoogle SheetsPostgreSQLMySQLSupabaseNotionand more
Banks & payments
Open bankingWiseRevolut BusinessPayPalStripeand more
E-commerce
ShopifyWooCommercePrestaShopand more
Mail & messaging
Microsoft 365GmailGoogle CalendarSlackany IMAP mailboxand more
Work & projects
monday.comAsanaJiraTrelloand more
Files & documents
Google DriveSharePointDropboxDocuSignand more
YOUR SYSTEM{{ anyTyped }}

Not on the list? That is the normal case. If it has an API, the agent reads its documentation and writes the connection itself, in hours, not in a release cycle.

WHO SEES OUR PASSWORDS?

The agent writes the code. You hold the keys.

You paste a key into the platform once. It is encrypted on save and never shown back: not to you, not to us, not to the agent.

Narrowest access that works
Read-only where reading is enough
Revoke any time, on your side
ADD CONNECTIONyou, not the agent
SYSTEMQuickBooks
API KEY••••••••••••••••
SaveEncrypted on save. Never shown back.
The agent runs against the system without ever receiving the value.

HOW A RUN ACTUALLY GOES

Cheap when it is routine. Clever when it is not.

Most days a small script does the work in under a second, for free. The day something you don’t control changes, the agent steps in, then fixes the script so tomorrow is cheap again.

TIMELINEbig orders · one week
MON 06:00script0.4 s · 0.00 €
TUE 06:00script0.4 s · 0.00 €
WED 06:00script failed: the register changed its form
agent finished it another way14 s · 0.03 €
rewrote the script
THU 06:00new script · back to 0.4 s0.4 s · 0.00 €
FRI 06:00script0.4 s · 0.00 €
no ticket · no fix · no morning lost · you got one line in Friday’s report

By default, a script does the work

Same result every time, under a second, and the AI bill for it is zero. That is most days.

On purpose, it hands over a judgement call

Is this the same supplier under a different name? The script does the mechanical part, the agent decides, with everything it already knows.

When it breaks, the agent finishes it anyway

Today’s work is done today, not after somebody fixes it. Then it rewrites the script, and tomorrow is back on the cheap path.

Name the two systems that should be talking to each other.

Your Operations agent arrives set up for exactly that, by the next working day.

Get your agent