--- title: "Shortcut (Clubhouse) Integration" description: "Connect AI agents to Shortcut (formerly Clubhouse), the project management platform for software teams. Agents search, create, and update stories, organize epics and iterations, and read workspace projects, workflows, and members." url: https://flowrunner.ai/integrations/clubhouse date_modified: 2026-08-04T10:04:16-07:00 --- # Shortcut (Clubhouse) [Project Management](https://flowrunner.ai/integrations/category/project-management-productivity) Connect AI agents to Shortcut (formerly Clubhouse), the project management platform for software teams. Agents search, create, and update stories, organize epics and iterations, and read workspace projects, workflows, and members. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 10 actions · API key · available [Shortcut (Clubhouse) website](https://shortcut.com/) · [Platform Documentation](https://developer.shortcut.com/api/rest/v3) · Capability data verified 2026-08-12 1. A bug report arrives as a new issue in the product repository 2. Search Stories runs "type:bug" with keywords from the report to check for an existing story 3. List Workflows resolves the team's triage state ID for placement 4. Create Story files the bug with type Bug, the report distilled into the description, and the repo link attached 5. Agent scores severity from the report's content, crash versus cosmetic, customer-facing versus internal 6. The on-call engineer confirms severity before the story jumps the iteration queue, because a false critical burns a sprint and a missed one burns a customer 7. Update Story sets the estimate, owner, and iteration from that decision 8. The story's app URL posts back to the reporting thread ## What This Integration Enables Shortcut is opinionated about structure, stories typed as Feature, Bug, or Chore, moved through explicit workflow states, grouped into epics and iterations, and that structure is exactly what makes it automatable. FlowRunner agents speak the structure natively: they search with Shortcut's operator query language, create stories placed by workflow state ID, update states, owners, estimates, and iterations, stand up epics, and resolve all the workspace metadata, members, workflows, projects, iterations, that story operations depend on. The result is a tracker where the structure is maintained by machines and the judgment calls, severity, priority, what gets archived, remain visibly human. - File stories from bug reports, tickets, forms, and inbound email, deduplicated first - Bulk-triage: move states, reassign owners, retype, re-estimate, archive with review - Sync trackers during migrations, with workflow states mapped explicitly - Group work into epics and schedule it into iterations - Export sprint and backlog state via operator queries ### Without FlowRunner **Bugs live in three places**: Reports in the repo, duplicates in the tracker, and truth in neither **Triage is a standing meeting**: Untyped, unowned stories pile up until Thursday's ritual sorts them **Sprint reports are archaeology**: Someone excavates the iteration every Friday to reconstruct what happened ### With FlowRunner **One story per bug, linked both ways**: Duplicate search runs before filing, and the repo issue carries the story URL **Triage happens on arrival**: Stories arrive typed, placed in a workflow state, and routed to a human only for severity **Sprint state exports itself**: Operator-language searches feed reports the day they are asked for ## Use Case Scenarios ### Repo issue to sprint-ready story An issue opens in [GitHub](https://flowrunner.ai/integrations/github). The agent searches for an existing story, files Create Story with type Bug into the triage state, and posts the story URL to [Slack](https://flowrunner.ai/integrations/slack) and back onto the issue. When the engineer confirms severity, Update Story assigns the owner UUID from List Members and schedules the iteration from List Iterations. The bug is in the sprint conversation the same hour it was reported, with one canonical record. ### The sprint review that writes itself Before each review, the agent runs Search Stories with "iteration:current" variants, pulls full detail with Get Story for the highlights, and writes the rollup to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): completed by type, carried over, unestimated strays. The same queries power a stakeholder digest with app URLs, so non-engineers click through to real stories instead of reading a paraphrase. Nobody spends Friday reconstructing the sprint. ### Tracker migration without the death march A team is moving from [Jira](https://flowrunner.ai/integrations/jira-issues) to Shortcut. The agent pulls issues in batches, maps each status to a Shortcut state ID resolved from List Workflows, and calls Create Story with type, description, owners matched by email against List Members, and labels carried over by name. Epics get created first with Create Epic so stories land grouped. The migration runs as a supervised flow with a reviewable log, not a weekend of copy-paste. ## Human-in-Loop Highlight Update Story can archive a story, and archiving is how work disappears in Shortcut: archived stories drop out of boards, searches default away from them, and the iteration burndown quietly forgets they existed. A hygiene agent that archives everything untouched for 60 days will eventually archive the story that was blocked on a vendor contract, and the commitment it tracked evaporates without a decision. There is a second trap in the same action: supplied owner and label lists replace rather than merge, so a careless bulk update can silently strip every owner from a hundred stories. FlowRunner flows therefore treat two things as human-gated: any archived-status change, presented as a docket with each story's state, owners, and last activity, and any bulk update that supplies owner or label lists, previewed as before-and-after. "Archive 23 stories from Q1 backlog? Two have owners and one sits in a started state." The engineering lead answers in one click, with the docket preserved. Cleanup stays cheap; erasing commitments stays deliberate. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 10 actions ### Stories 4 - **Search Stories** Searches the workspace with Shortcut's operator query language, such as "state:started owner:jane type:bug", returning IDs, names, types, workflow states, and a pagination cursor. - **Get Story** Retrieves one story by public ID in full: description, type, workflow state, epic, iteration, owners, tasks, labels, comments, and external links. - **Create Story** Creates a story with a name and a placement, workflow state preferred over legacy project, plus optional type (Feature, Bug, Chore), description, epic, iteration, estimate, owners, and labels. Returns the new ID and app URL. - **Update Story** Updates only supplied fields: workflow state, epic, iteration, type, description, estimate, owners, labels, archived status. Owner and label lists replace rather than merge, and archived changes are gated in FlowRunner flows. ### Epics 2 - **List Epics** Lists epics with ID, name, state, milestone, and progress counts. The grouping layer for roadmap-scale work. - **Create Epic** Creates an epic with a name, plus optional description, deadline, milestone, and owners. Returns the new ID and app URL. ### Projects 1 - **List Projects** Lists legacy projects with ID, name, description, team, and colour, for workspaces still placing stories by project. ### Workflows 1 - **List Workflows** Lists workflows with their ordered states, Unstarted through Done, supplying the state IDs that position every story. ### Members 1 - **List Members** Lists workspace members with UUID, name, mention name, email, and role. The resolution step behind every owner and requester assignment. ### Iterations 1 - **List Iterations** Lists time-boxed sprints with ID, name, start and end dates, status, and team. The scheduling reference for sprint placement. ## Frequently Asked Questions ### What can FlowRunner do with Shortcut (Clubhouse)? FlowRunner agents can run Search Stories, Get Story, and Create Story in Shortcut (Clubhouse), plus 7 more actions. ### Does connecting Shortcut (Clubhouse) to FlowRunner require OAuth? No. Shortcut (Clubhouse) connects to FlowRunner with an API key, no OAuth flow required. ### Can Shortcut (Clubhouse) trigger a FlowRunner workflow automatically? Shortcut (Clubhouse) doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Shortcut (Clubhouse)?** This integration exposes Shortcut (Clubhouse) to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/clubhouse. Site index: https://flowrunner.ai/llms.txt