Focus on your business.
Zervanor drives your automation engine.
Workflows, connectors and agents your product runs on — with local invoicing, payment and logistics rules already modelled. Below is what the engine runs today.
Every entry is grounded in a versioned connector pack the engine can actually execute — a trigger, its steps, and the agents that handle the judgement.
Marketplace Question Draft Reply v2
Every hour the oldest unanswered customer question on Trendyol is picked up. A support agent drafts a short Turkish reply from the question and product context, and the seller sees the draft next to the original question and approves or rejects it. Only approved text is ever sent to the customer. Marketplace answer-time directly affects seller rating, and questions arrive faster than a small team can watch them.
Month End e-Archive Close v2
On the fifth of each month the sales invoices in Parasut are scanned for ones that never had an e-Document issued against them. The owner sees the list before anything happens, and on approval an e-Arsiv is issued through Parasut for each one. Invoices without their e-Document are a quiet compliance debt: the sale is recorded, the tax document is not, and nobody notices until the accountant closes the period.
New Employee Onboarding Kit
Each morning the employee list in Kolay IK is checked for people whose employment started since yesterday. After HR approves, every new hire is assigned the mandatory occupational safety (ISG) training, an orientation calendar event is created, and HR gets an SMS. ISG training assignment is a legal obligation in Turkey, and in a small company it depends on somebody remembering — this removes the remembering.
Overdue Invoice Payment Chase v2
Every morning the open sales invoices in Parasut are scanned for ones past their due date with a balance still outstanding. After the owner approves, each customer gets an SMS reminder. Three days later the same invoices are re-read, and only those still unpaid go to a second approval for a firmer notice. Small businesses lose collectable money simply because nobody has time to run the ladder by hand.
Parasut to Hepsiburada Stock Sync
Each morning the stock counts in Parasut (the source of truth) are compared against the live Hepsiburada listings. Products whose stock differs go to the owner for approval, and on approval the Hepsiburada listings are set to the Parasut value. Tracked products that have no Hepsiburada listing at all are reported. Overselling on a marketplace because the accounting stock moved is one of the most expensive small mistakes a multichannel seller makes.
Rejected e-Invoice Patrol v2
Each morning the last seven days of outgoing e-Invoices are checked against the tax authority's status. Any that came back rejected or errored are collected and the accountant gets one SMS with the count and the total at risk. A clean week produces no message at all. Rejected e-Invoices are easy to miss because nothing in the accounting package changes when the rejection happens — the money is simply never collectable until someone notices.
Trendyol Commission Invoice Reconciliation
Every month, Trendyol's commission invoices are matched against the purchase bills recorded in Parasut. Commission invoices that were never entered are surfaced for accounting approval, and the approved ones are written back to Parasut as purchase bills. Marketplace sellers routinely miss these: unrecorded commission overstates profit and loses the VAT deduction.
More local automations for your region are on the way — meanwhile, these global operations work anywhere.
Prefer to build it yourself? A visual canvas with real depth.
Chat-to-Build and the visual builder produce the same thing — one real workflow. Snap triggers, control flow, and actions together as blocks your team inspects, governs, and extends. Everything the chat assembles, you can open and edit here.
Visual workflow builder
Compose flows on a canvas, inspect every run, and open any Chat-to-Build draft to refine it by hand.
43 node types
Triggers, control flow (switch, loop, parallel, filter, merge, wait), data transforms, connector actions, agent steps, human approval, code, and Tables — the platform’s own data store, so an automation can remember between runs.
Agent hosting included
Long-running AI agents run as isolated pods on the same runtime — no extra infrastructure.
Real workflow blocks in the Zervanor builder.
The building blocks
The real node palette — the same step types the chat grounds against and the engine runs.
cloudeventSchedule / CronscheduleWebhookwebhookManualmanual conditionSwitch (multi-way)switchLoop (for-each)loopParallelparallelFilterfilterMergemergeDelaydelayWait (durable)waitStopterminateNo-opnoop edit_fieldsTransform (JSONata)transformSortsortSummarizesummarizeAggregateaggregateTable (org data store)table_action connector_actionRun agentagent_actionAgent taskagent_taskHuman approval (HITL)human_taskCode (Deno sandbox)script_actionSub-workflowworkflow_actionEmit eventemit_event A catalog that compounds — and doubles as agent tools.
Every connector is a versioned pack validated against a canonical schema. Certify one once and it is instantly available to both your workflows and your AI agents.
Live counts from the platform — plus thousands more providers mapped and queued in the pipeline.
Run on the platform — or on your own device.
The same agent runs in the managed cloud or on your own machine, draws on a routed mix of cloud and on-device models, and is reachable through a chat interface.
Cloud or your device
The same agent — one manifest, one SDK — runs in a managed cloud pod or on your machine via the Zervanor Desktop app. It connects outbound, so it works behind a firewall.
Smart model routing
One catalog of cloud, platform and on-device models behind named routers with automatic fallback. Choose a model per agent; run inference locally when you want.
Conversations
A persistent, model-routed chat that can drive your connectors and agents as tools — with a confirmation step before anything changes.
Desktop runtime host today; a mobile host is on the roadmap.
Enterprise-grade underneath, SMB-simple on top.
Multi-tenant isolation, access control and observability from day one — the operational floor a product has to stand on before it ships to anyone.
Tenant isolation
Per-tenant Kubernetes namespaces keep every organization separated — from day one, not an upsell.
Access control
Role-aware access and identity integration for teams that need operational control.
Observability
Event history, OpenTelemetry tracing, and a token-free public status page.
Start building your first automation
Create a free account and build on the live platform — describe what you want in chat, or compose it on the visual canvas. No credit card required.