PROJECT MANAGEMENT
Register a cross-board blocker from any tool via webhook
Accepts a webhook when someone declares a blocker living on another team's board, validates that the blocker exists, links the two tasks bidirectionally.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook declares a cross-board blockerHTTP webhook
- LogicValidate payload and both task ids
- ActionConfirm blocker exists on home boardmonday.com
- ActionWrite bidirectional dependency linkmonday.com
- OutputConfirm linkage in SlackSlack
What it does
It gives any tool or form a single endpoint to declare "this task is blocked by that item on another board." The workflow verifies the blocker is real, creates the cross-board link on both sides, and confirms it — so dependencies get recorded the moment they're discovered.
When to use it
Use it when blockers surface in standups, chat, or intake forms before anyone records them in the tracker, and you want a frictionless way to capture cross-board dependencies without hunting through both boards manually.
How it works
- 1An HTTP webhook trigger receives the blocked task id, the blocker task id, and the source.
- 2A logic step validates the payload and confirms both items exist; malformed requests are rejected.
- 3The workflow looks up the blocker on its home Monday board to confirm it's open and a valid dependency.
- 4It writes the cross-board link onto the blocked task and back-references it on the blocker.
- 5It posts a Slack confirmation to the requester summarizing the linked dependency and the blocker's current status.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect monday.comVisual work management for teams.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Project Management workflows
Zoom Sprint-Retro Audio to Themed Linear Action Board
Transcribes a recorded Zoom sprint retrospective, clusters the discussion into themes, and creates assigned Linear issues for each action item with the spoken owner attached.
Escalate Overdue Cross-Team Dependencies to Owners and Stakeholders
Each morning checks Linear for dependency-labeled issues past their due date and nudges the owner in Slack, escalating to the requesting team's lead if it stays unresolved.
CEO-Authored Weekly Cross-Team Dependency Risk Briefing
Weekly, the CEO agent gathers all tracked dependencies across Linear and ClickUp, reasons about which handoffs threaten upcoming milestones.
Scan Notion Meeting Notes for Action Items and Open ClickUp Dependency Tasks
On a schedule, parses recently edited Notion meeting-notes pages for action items that one team owes another and creates a ClickUp task for each, with due date and owner mapped.
Sprint-Retro Recap to Slack with Owner DMs
After a Zoom retro, posts a themed recap to the team Slack channel and direct-messages each owner the specific action items they committed to during the call.
Turn GitHub Blocking Comments into Tracked Cross-Team Promises
When a reviewer comments that a PR is blocked waiting on another team, the flow registers a tracked dependency in Linear and notifies the team that owes the unblock.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.