Read.ai to Shortcut
A feature is rarely settled in one call, and the decisions end up spread across several Read.ai recordings. Pick up to three of them and Spectr turns them into one spec sheet and a set of Shortcut stories with acceptance criteria and estimates. You go through the set before a single story is created.
How it works
A call is imported from Read.ai. Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to Shortcut, and the requirements, scope log and project memory update from the same call.
Read.ai over OAuth, approved on its consent screen and refreshed by Spectr from then on. Shortcut with an API token from your Shortcut account settings, pasted into the project and stored encrypted.
No Read.ai plan requirement. Once Shortcut is connected you can set a default team and starting workflow state; agree on both with whoever runs the board.
When something raised in a Read.ai meeting falls outside what the project agreed, Spectr flags it in the scope log, dated and traced to the meeting it came from. You see the flag on the spec sheet and decide whether the work belongs in Shortcut.
Pick a single Read.ai meeting or up to three about the same feature. A combined run gives each meeting its own reading budget and produces one spec sheet, so the stories reflect where the conversation ended up rather than where it started.
Drafts are assigned from the project's team, which Spectr syncs from your Shortcut workspace members, so the owner set in review is a real Shortcut user when the story is created.
When a status refresh finds a story completed in Shortcut, Spectr marks it done, and that is what moves the project's budget projection.
In Spectr, open the project you want to connect and go to Integrations.
Choose Read.ai, click Connect, and approve access on Read.ai. Spectr refreshes the token from then on.
In Shortcut, create an API token from your account settings.
Choose Shortcut and paste the token, then optionally set a default team and starting workflow state.
Import a meeting from Read.ai. Spectr gathers project context, extracts a structured spec, and drafts a story for each requirement and bug.
Approve the drafts worth keeping and publish them to Shortcut. Any scope flag the meeting raised stays in the scope log, to settle separately.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. Read.ai doesn't list Shortcut, and Zapier has no route between the two. Spectr connects to Read.ai over OAuth and to Shortcut with an API token.
The starting state you set under Story defaults, so stories arrive where your team expects new work. Without one, they land in the first unstarted state of your first workflow.
The ones visible to the Read.ai account that approved the connection. Connect with the account that records this project's calls.
Use case
Import a call, get a draft backlog, approve what is right
Connect Read.ai over OAuth and mix its meetings freely with Fathom and Granola in one project
Publish stories into a Shortcut team and read their workflow state back
