PROJECT MANAGEMENT
PTO-Sprint Conflict Detector
When a PTO event is added to the shared Google Calendar, checks whether that person owns committed Linear work overlapping their time off and warns the assignee and lead if it…
How it runs
The automated pipeline, trigger to output.
- TriggerNew PTO event on shared Google CalendarGoogle Calendar
- ActionQuery assignee's active Linear issues in leave windowLinear
- LogicBranch on whether overlapping work exists
- ActionWarn assignee and lead in SlackSlack
- OutputComment absence flag on affected Linear issuesLinear
What it does
Catches the moment someone books time off that collides with work they own. When a new PTO entry lands on the shared Google Calendar, it looks up that person's in-progress and committed Linear issues whose due dates fall inside the leave window. If there's an overlap, it warns both the assignee and their lead so the work can be reassigned or rescheduled.
When to use it
Use this when last-minute PTO keeps blindsiding sprints. It closes the gap between the calendar and the board so nobody discovers a blocker only after a teammate has already left.
How it works
- 1A new Google Calendar PTO event triggers the run.
- 2It identifies the person and the leave date range from the event.
- 3It queries Linear for that assignee's active issues with due dates inside the window.
- 4A logic step branches: if no overlapping issues exist, the run ends quietly.
- 5If overlaps exist, it posts a Slack warning listing the at-risk issues to the assignee and their lead.
- 6It adds a comment on each affected Linear issue flagging the upcoming absence.
Set it up
What you configure once, before turning it on.
- 1Connect Google CalendarEvents, attendees, availability.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.