Nishi FamilyCompare › Workflow Automation

Nishi vs the Field

Workflow Automation — mechanically measured, liar-killed, sovereign.

Nishi vs Zapier and n8n and Temporal and Microsoft Power Automate

How this is scored. Every Nishi cell is measured: the generator reads the real organ source on disk and requires the implementing symbol to exist (no self-grading). Competitor cells record documented capability presence. Best=leads this axis, Yes=present, Part=partial, No=absent. This is capability presence, not depth or scale: the majors lead on index size and neural ranking. Nishi's genuine exceeds are the sovereignty / neutrality / determinism axes.

Feature matrix

CapabilityNishiZapiern8nTemporalPower AutomateNotes
Trigger-action rules engine (rules as data)YesYesYesPartYesEvent-cond-action rules validated whole before load; Temporal is code-first not rules
Idempotent exactly-once firing by event idYesPartPartBestPartDedup ledger by event id; Temporal exactly-once execution is the reference
Scheduled recurring execution (tickless + RRULE)YesYesYesYesYesTickless bounded scheduler sleeps to next due job; RRULE incl YEARLY
Reminder automation with once-only ledgerYesPartPartNoYesLead-day reminders; sent-once guaranteed by an additive ledger
Multi-channel send incl physical mailYesPartPartNoPartEmail plus print-ready postcard letter card composed in-house; rivals need Lob-class connectors
Bulk personalized merge to a segmentYesPartYesNoYesPlaceholder-validated personalization; unknown placeholder fails loud
Document-generation action (real .docx)YesPartPartNoYesCoordination fields become a versioned Word document
Autonomous dispatch runs registered workYesNoNoPartNoMachine leases a stream, runs its gate, marks DONE only on GREEN
Durable crash recovery (ledger replay + revive)YesPartPartBestPartReflog replay plus boot revive; Temporal durable execution is the reference
Run liveness heartbeats ALIVE/STALLEDYesYesYesYesYesLiveness recomputed from real beats vs the clock, not self-reported status
Ops pipeline automation with auto-rollbackYesNoPartPartNoNever-brick health-gated promote; upload-unpack-build-deploy over one API
Outbound event stream (SSE)YesYesYesYesYesGET /api/events text/event-stream
Unified multi-step durable workflow engineYesPartYesBestYesR1 LANDED gated GREEN: event-sourced run ledger, per-step retry, durable dedup, crash-resume; Temporal still leads depth (timers, signals, child workflows)
Sovereign organ-connector catalog (any organ as a step)YesYesBestYesYesR3 LANDED gated GREEN: exec-organ over a GREEN fail-closed catalog, proven composing the real ICS organ; n8n node ecosystem is the OSS reference
Inbound webhook triggersNoBestYesYesYesZapier built the category
Third-party SaaS connector catalogNoBestYesNoYesZapier 8000-plus external apps; Power Automate 1500-plus; the sovereign-internal catalog above is ours
Visual no-code workflow builderNoYesBestNoYesn8n node canvas is the open-source reference
NL-to-workflow LLM copilotNoYesPartNoYesZapier and Power Automate ship Copilot builders; n8n AI nodes partial
Human-in-the-loop approval stepsYesPartPartPartBestR4 LANDED gated GREEN: approve step parks the run until an APPROVED or DENIED ledger decision lands, deny wins fail-safe; Power Automate Approvals still leads UI depth
Process mining / run observabilityYesYesYesBestYesR6 LANDED gated GREEN: run board + 0-JS HTML derived by ledger replay, nothing self-reported; Temporal visibility UI still leads depth
RPA UI-level automationNoNoNoNoBestPower Automate Desktop leads this cohort
Record-actions macro recorder (watch and replay)NoNoNoNoBestPower Automate Desktop recorder defines this category; we have NO capture-my-actions capability anywhere
Data passing between steps (outputs to inputs, variables)YesBestBestYesYesR8+R8b LANDED gated GREEN: event fields auto-bind as run vars, set-var derives, connector>var CAPTURES organ stdout, placeholder substitution into any step arg incl forked argv, last-write-wins, unknown fails loud; Zapier and n8n field-mapping UIs still lead
Mid-flow branching / conditional pathsYesYesBestYesYesR9 LANDED gated GREEN: per-step k=v condition vs the run variable plane, mismatch SKIPs recorded in the ledger; n8n IF/Switch canvas still leads expressiveness
Loops / iterate over a collectionYesPartYesYesYesR11 LANDED gated GREEN: for-each forks a connector per comma-list item, {item} bound per iteration, WFITER records, failed item fails the step; n8n and Power Automate loop nodes still lead expressiveness
Error-handling branches (on-failure path)YesYesYesBestYesR10 LANDED gated GREEN: exhausted step routes to a later handler step, failure stays recorded, wf_error vars set, run can RECOVER to DONE; Temporal compensation patterns still lead depth
Flow versioning / draft-test-liveYesYesYesBestYesR12 LANDED gated GREEN: @version directive, runs stamp WFVER, resume records WFVERDRIFT on cross-version resume, CLI verify validates drafts without firing; Temporal replay-safe versioning still leads depth
Template gallery / marketplaceYesBestYesNoYesR13 LANDED gated GREEN: gallery index + fail-closed instantiate that validates the copied definition whole; 2 real templates ship (venue-agreement, expense-approval); Zapier's thousands-of-Zaps marketplace is still the distribution moat
U1 product visual design (vs the Zapier editor)YesBestYesNoYesR7 LANDED: nx_wflow_ui console CERTIFIED 1000permil by nx_ui_judge (DE/US/CR/AX/CO all 1000), live /compare/automation/bench; tokens + gradient + SVG + responsive + a11y; Zapier editor still leads as an interactive product
U2 interaction UX (drag, inline test, edit-in-place)NoBestBestNoYesZapier editor and n8n canvas set the interaction bar
U3 run information design (dashboard)YesYesYesBestYesThin: one 0-JS run board page; Temporal UI leads info design
U4 product polish (onboarding, docs, accessibility)NoBestYesNoYesMature-product polish entirely absent
Sovereign own-stack zero-per-task costBestNoPartPartNoOwn language compiler TLS store on your hardware; Zapier bills per task; n8n and Temporal self-host on Node and Go stacks
Additive never-lose tamper-evident run historyBestPartPartPartPart144 of 144 concurrent writes zero lost measured vs live git; rivals cap run-history retention
coverage 764/1000EXCEEDS 2PRESENT 24ABSENT 8
Honest verdict. Nishi has broad, sovereign search-engine presence — a real organ behind every core ranking and crawl axis, built bits-up in one language. It is not yet a scale or neural-ranking rival: the majors lead on index size (billions to trillions vs a Common-Crawl-seeded slice) and trained rerankers. Nishi's genuine exceeds are structural — owning the whole stack, neutrality by construction, and a zero-JS integer-deterministic result page. The climb is a bigger index and a trained reranker.

Generated by nx_swcompare_matrix (sovereign NishiLang organ) from knowledge/compare/automation.matrix — every Nishi cell verified against real organ source on disk. Zero JS, zero trackers.