Announcing o11's backing from Y Combinator.
AI for monday.com
AI that drives the board.
- Edit items and columns straight from chat.
- Chain board automations without writing recipes by hand.
Engineering Sprint 24
Sprint 24 — In progress
| Item | Status | Priority | Date | Pts |
|---|---|---|---|---|
| Onboarding flow QA | Working on it | High | 4/24 | 5 |
| Backfill audit log gaps | Done | Critical | 4/22 | 8 |
| Refactor billing webhooks | Working on it | High | 4/26 | 5 |
| Latency regression on /search | Stuck | Critical | 4/24 | 3 |
| CSV export for orders | In review | Medium | 4/25 | 5 |
Sprint 24 — Backlog
| Item | Status | Priority | Date | Pts |
|---|---|---|---|---|
| Pricing page rewrite | Not started | High | 5/02 | 8 |
| Spike: token refresh strategy | Not started | Medium | 5/03 | 2 |
| Index analytics by region | Not started | Medium | 5/05 | 5 |
| Bug bash for v3.5 prep | Not started | Low | 5/08 | 3 |
o11 for monday.com: an AI agent layer for the work OS
o11 is an AI execution layer that runs inside monday.com. The agent updates items, builds board automations, and chains workflows across boards — without sending an ops lead into the recipe builder to wire what they already described in plain English.
If you have searched for AI for monday.com, a monday AI agent, or an alternative to monday AI for actual workflow execution, the difference comes down to one question: does the AI suggest a recipe or run the recipe?
What teams use o11 for in monday.com
- Board automation. Compose multi-step automations, edit existing recipes, and audit what is firing where without leaving the board.
- Item updates. Bulk-update statuses, owners, dates, and custom columns from a single instruction.
- Workflow chaining. Trigger updates across linked boards, dashboards, and docs together so cross-team work stays in sync.
- Intake to action. Turn form submissions, emails, and Slack threads into properly-typed items on the right board.
Why o11 differs from monday AI
monday AI ships as in-product blocks for content generation, summaries, and smart suggestions. The execution still ends with a human editing the item, wiring the recipe, or copying the result into another board. o11 is built to drive those edits. The chat is the control surface, monday.com is where the work lands.
Built for teams that live across systems
monday.com is one part of a much larger stack — usually paired with Slack, CRMs, GitHub, and a doc tool. o11 is positioned to act across all of them. A new client kickoff can become a set of monday items, a CRM update, a Slack channel, and a kickoff doc without anyone re-typing the same intent into four tools.
Where monday.com teams typically start with o11
- Ops leaders with intake forms, board hygiene, and weekly rollups.
- Marketing teams with campaign planning and request management.
- Creative agencies with project boards and client status updates.
- PMOs with portfolio and program-level reporting.
How o11 respects monday.com permissions
The agent operates with the user’s own account. Board permissions, item ownership, and view restrictions apply exactly the way they do for that user in the UI. Nothing is bypassed. That is what makes o11 deployable in organizations that cannot trust a tool that runs as an over-privileged service account.
FAQ
How is this different from monday AI?
monday AI ships in-app blocks for content and summaries; o11 drives item updates and cross-tool workflows.
Who is it for?
Ops, PMO, marketing, and creative teams running boards in monday.com.