Manage Your Shortcut Stories and Epics Through Your Muse
Through a Composio custom connector, a muse can search your Shortcut workspace, create stories and epics, add comments, and update work in bulk, without you opening the project board.
What it does
Shortcut is a project tool where teams track work as stories grouped into larger epics, planned in timed rounds called iterations. Connecting it through Composio gives the muse tools for that workspace. It can search stories and epics by the terms you give, list the stories inside an epic or an iteration, and read a story in full, including its comments and history. It can create a single story, create several stories in one request, and create a new epic, for example an epic for a quarter's goals. It can add a threaded comment to an epic or a story, update one story or many at once, and link two stories so the relationship is recorded. Name the project, epic, or story each time.
How to use it
- Make a Composio account, open its Muse page, and copy your API key. The key starts with ck.
- In a new chat, ask the muse to create a custom connector for the Composio server and open the secure credentials store. Paste the key there, never in the chat.
- Back in the chat, ask the muse to connect Shortcut. Follow the sign-in link, sign in, and approve the access. Check the connection shows as active in the dashboard.
- Start with a search, such as finding every story in one epic, and check the list against Shortcut.
- Then create one story and open it on the board to confirm the details landed correctly before you ask for bulk work.
What you need
- A Muse account that can add custom connectors
- A free Composio account and its API key
- A Shortcut workspace you are a member of
What to watch for
- Bulk changes touch many stories at once. Ask for the list of matching stories first, read it, and only then approve the update.
- Comments post under your account. Read the exact comment text before you approve it, the same way you would read your own message before sending.
- Search terms decide the results. A short or vague term can pull in stories from other projects, so include the project or epic name in the request.
- Never paste the API key into a chat. If you do, treat it as exposed: make a new key in the Composio dashboard, delete the old one, and add the new key through the secure store.