A canvas, not a DSL
Drag nodes from a catalog palette, wire edges between handles, configure each node in a side panel. Data flows with {{trigger.body.name}} templates — whole-token values keep their types.
Automation without the improvisation. Visual DAGs for the glue work that doesn't need an LLM.
Pipelines are deterministic glue: company-scoped DAGs of typed nodes that fire manually, on a secret-token webhook, or on cron. Routines are AI-driven; Pipelines are wire-driven — same result every run, no model call unless you explicitly put an AI employee in the middle of the flow.
- 14 node types across 4 families
- Manual, webhook, and cron triggers
- 21 Integrations callable as nodes
- Every run logged and auditable
genosyn.com / pipelines / stripe-large-charge
stripe-large-chargeLiverun #88 · completed in 1.2s
Trigger
Stripe webhook
Branch
amount > $1,000
AI employee
Ask Alex to summarize
Message
Post to #wins
{{trigger.body.amount}} → $4,200 · branch: true · reply captured → {{ask-alex.reply}}
What ships in the box
Pipelines, in detail.
Three ways to fire
A manual Run-now button, incoming webhooks with unique secret URLs, or a 5-field cron schedule on a 30-second heartbeat that advances before firing, so slow runs can't double-fire.
Write into your workspace
Six built-in actions post a channel message, add a todo, create a project, append a Base record, ask an AI employee, or write a journal note — straight into the primitives your team already uses.
Branches, delays, HTTP
If/else branches with color-coded true/false edges, set-variable nodes, delays, and a full HTTP request node with method, headers, and body — responses auto-parse as JSON.
Call any Integration
One node invokes any tool on any connected Integration — Stripe, Gmail, GitHub, Notion, Linear, Airtable, Postgres, Telegram, and more — with the result captured for downstream nodes.
Runs you can replay
Every execution records status, which trigger fired, the payload, per-node outputs, and a step-by-step log. The Runs tab lists the last 50 and auto-refreshes while a run is in flight.
With AI employees
Where wires meet judgment
Pipelines and AI employees are complements, not competitors. Keep the deterministic 90% on wires and drop a model in only where a decision is genuinely needed.
Ask AI employee, mid-flow
One node sends a message to an employee and captures its reply for downstream nodes — a webhook arrives, the employee summarizes or decides, the pipeline carries on deterministically.
Routines can pull the trigger
An employee running a Routine can POST to a pipeline's webhook URL, so AI-driven work can kick off wire-driven work.
Authoring stays human
Pipelines run as the company and are built by Members in the UI — employee Grants are never bypassed by an employee-authored flow, by design.
Questions
Frequently asked.
How are Pipelines different from Routines?
Routines are scheduled work performed by an AI employee — a model is always in the loop. Pipelines are deterministic DAGs of typed nodes: same result every run, no LLM involved unless you explicitly add an Ask-AI-employee node. Routines are AI-driven; Pipelines are wire-driven.
What can trigger a pipeline?
Three trigger types: Manual (a Run-now button), Webhook (each node gets a unique secret URL and the POST body becomes the trigger payload), and Schedule (standard 5-field cron on a 30-second heartbeat). A pipeline can carry multiple triggers, and each run records which one fired.
Can a pipeline talk to my other tools?
Yes. The Call-integration node invokes any tool on any connected Integration — 21 are registered, including Stripe, Gmail, GitHub, Notion, Linear, Airtable, Postgres, MySQL, ClickHouse, Redis, Telegram, X, Reddit, and LinkedIn. For everything else there's a generic HTTP node.
How do I debug a failed run?
Open the Runs tab: every execution keeps its status, trigger kind, payload, per-node outputs, any error, and a step-by-step log. Safety rails cap runs at 200 steps and delays at 60 seconds, so a wiring mistake can't loop forever.
Do I need to learn a DSL or write code?
No. You build on a visual canvas with a node palette and per-node config forms. Data flows between nodes with {{trigger.body.name}}-style templates, and whole-token templates preserve types like numbers and arrays.
More in the box
All productsAI Employees
Persistent AI teammates with a written constitution, markdown playbooks, and cron-scheduled work — every execution captured as a readable Run.
Learn moreWorkspace
Slack-style channels and DMs where AI employees are real members — @mention one and it joins, replies, and reports back from its Routines.
Learn moreTasks
A Linear-style task manager where any todo can be assigned to a human or an AI employee — with an in-review flow that closes the trust gap.
Learn moreBases
Multi-table workspaces with typed fields, saved views, comments, and attachments — and 21 built-in tools for granted AI employees.
Learn moreMeet your first AI employee.
One command pulls the image and starts Genosyn on localhost:8471. Write their soul. Schedule their first routine.
$curl -fsSL genosyn.com/install.sh | bash