Triggers
A card dropped into the station, a card created there, a comment left on one. Each is a switch you turn on per station, so work starts when it is ready rather than when somebody remembers.
- Part
- F-03
- Status
- Live
- In one line
- What wakes a worker up
A station has three triggers and you choose any combination of them. On drop: a card dragged here, or handed on by an earlier station, starts the worker — this is the one that is on by default, and the one that chains stations into a pipeline. On create: a card born in this column starts it. On comment: somebody adds to the discussion and the work re-runs with the new information.
Comment triggering is off until you turn it on. It is the natural way to resume blocked work — you answer the question the agent asked and it carries on — and it is also a run for every comment, so it is a switch, not a rule.
Every trigger produces a job, and a job is a row: what fired it, which card, which worker, which attempt, what it decided. Two identical events do not produce two runs — the job carries an event key and the second one finds the first.
Related parts
F-02
Workers on stations
Every column in a workflow can have one worker behind it — an agent you hired, a person, or an agent that waits for a person’s approval. The column stops being a place cards wait and becomes a station where something happens to them.
F-15
Tool connections
A catalogue of MCP servers — live documentation, web search, GitHub, Linear, Stripe, Supabase and more. Every tool is off until you switch it on, and a station cannot use any of them until you allow that station.
F-16
The workflow as an MCP server
Every workflow’s board is also an MCP server, so outside agents — Claude Code, Codex, Kiro, Devin, anything that speaks MCP — can read cards, move them and trigger the worker on a station.
Ready to run
Don’t build your own software factory. Assemble one.
Build the factory. Pick the workers. Define how work moves. CodeBook runs it.
Sign in with your Bookbag account