Skip to content

Self-improving AI Employees for everyone

14.3 KB
Raw Blame

Node Logic Flow Documentation

Behavioural contract for every workflow node. One file per node, grouped by category. Keep each card aligned with its plugin and execution path; historical diagrams do not override the current shared execution contract.

How to use

  • Adding a node: copy _TEMPLATE.md into the right category folder and name it <type>.md -- the filename stem must equal the registered type string exactly (camelCase or snake_case, whatever the plugin declares) as set on the backend plugin at server/nodes/<group>/<plugin>/__init__.py.
  • Refactoring a node: update the matching contract test in server/tests/nodes/test_<category>.py first, then change the handler, then update this doc.
  • The index below is generated. Run company docs nodes after adding, renaming or removing a card; company docs nodes --check fails when a registered node has no card. Do not hand-edit between the AUTO-GENERATED-INDEX markers.

Conventions

  • Mermaid for flow diagrams (renders natively in GitHub & VS Code).
  • Tables for inputs/outputs/parameters - greppable, diffable in PRs.
  • Cross-link to the existing skill at server/skills/.../SKILL.md rather than duplicating tool-mode behaviour.
  • Keep "Side Effects" honest: every DB write, broadcast, subprocess, and HTTP call must be listed.

Shared execution contract

Cards describe a node's operation. The workflow layer owns cooperative admission and continuation for new controlled generations (execution_control_version=1): Stop allows admitted work and result bookkeeping to finish, then waits; Resume begins the next pending action in the same execution. Already-admitted parallel tools drain concurrently. An operation's sleep or approval wait is part of its admitted Activity when the node runs as an Activity; it is not automatically a control checkpoint. Legacy cancellation branches in a card describe explicit cancellation or older execution paths, not the new generation's Stop behavior.

Controlled push triggers are definitions and Signal queues in WorkflowControlWorkflow; controller polling uses provider fetch Activities, and cron uses Temporal Schedules plus CronTriggerWorkflow. Separate listener/poller workflows remain legacy compatibility paths. Stable event IDs, durable pending-key protection, and Continue-As-New fences apply to the versioned controller; interactive canvas waiters remain process-local. Signal acceptance acknowledges receipt into Temporal history, while completed Updates acknowledge transitions and read-only Queries return status.

Read Workflow control, Node creation, and Event Waiter System for topology, Activity policies, compatibility, producer delivery gaps, and known naming limits. This shared contract applies to all cards below; individual cards call out provider identities and operation-specific stopping boundaries.

Index

For the current browser architecture, see Browser runtime and Browser workspace. The registered node is browser; the browserHarness card is retained only as historical migration documentation. Inclusion in this generated document index does not establish that a retired node remains registered.

ai_agents

ai_chat_models

ai_tools

android

chat_utility

cli_integrations

code_fs_process

discord

document

dodo_payments

email

google_workspace

http_proxy

language

microsoft

mobile

search

specialized_agents

stripe

telegram_social

twitter

web_automation

whatsapp

whatsapp_business

workflow

workflow_triggers