Voice memo to Linear issues, daily | Dropbox + Deepgram + Linear

PromptCreate

Build me an agent workflow that runs every weekday morning at 9am in my local timezone and turns yesterday's voice memos into Linear issues, so my walk-and-talk brain dumps actually land in the engineering backlog instead of staying buried in audio files.

Trigger: cron, every weekday at 9am.

Steps the workflow should take:

1. Call Dropbox "List Folder" on a configured voice-memos folder path (make this a workflow setting). Pull every audio file in there.

2. Skip files that have already been processed in a previous run. Track by Dropbox file path or rev (whichever is more reliable for renamed files) so reruns never double-create issues.

3. For each new audio file, call Dropbox "Get Temporary Link" to get a short-lived download URL.

4. Hand each temporary URL to Deepgram "Transcribe Pre-recorded Audio" with smart_format and diarize both enabled. Use a current English-capable Deepgram model suited to single-speaker voice memos (nova-style).

5. Call Linear "List Teams" so the agent can pick the right team. If a default team key is configured on the workflow, use that; otherwise the agent should ask once on first run and remember the answer.

6. For each transcript, the agent should read it carefully and split it into discrete action items. One memo can produce zero, one, or several issues. For each action item, the agent should:

- Infer a clear, imperative-style title (e.g. "Investigate flaky checkout test on Safari").

- Write a description that quotes the relevant snippet from the transcript verbatim, plus any short context the agent inferred. Keep the original wording so I can hear my own voice in the ticket.

- Pick a priority (Urgent / High / Normal / Low) based on language cues like "today", "this week", "blocker", "someday".

- Suggest labels that match common engineering buckets (bug, investigation, refactor, infra, docs) when the snippet warrants it.

7. Call Linear "Create Issue" once per action item against the chosen team.

Important rules for the agent to bake in:

- If a memo includes a vague to-do like "we should look at X" or "I want to think about Y", do NOT drop it. Create a single investigation-style issue so the thought lands in the backlog where it can be triaged.

- If a transcript is pure narration or thinking out loud with no real action items, post nothing to Linear for that memo. Still mark the file as processed so it does not get retranscribed tomorrow.

- Never invent action items the user did not actually say. Stay grounded in the transcript.

- Keep titles short and engineering-friendly. Put the full quoted snippet in the description so context is preserved.

- If a transcript is in a language other than English, transcribe it anyway and write the issue in English with the original quote preserved underneath.

What does this prompt do?

Sweeps a Dropbox folder every morning for new voice memos you saved yesterday and transcribes each recording.
Splits the spoken to dos in every memo into separate Linear issues, one per action item, with priority and labels.
Quotes the matching snippet from your transcript inside each issue so engineers see the original context.
Skips memos that are just narration and never refiles the same recording twice.

What do I need to use this?

A Dropbox account with a folder where you save voice memos.
A Deepgram account for transcription.
A Linear workspace with the team you want issues filed in.

How can I customize it?

Change the time of day or how often it runs (every morning, twice a day, every hour).
Point it at a different Dropbox folder or filter to specific filename patterns.
Set a default Linear team, priority, or labels so every new issue lands the way you like.

FAQs

What happens if I record a memo with no real action items?

It gets skipped. If the transcript is just narration or thinking out loud with no concrete to dos, nothing gets posted to Linear and the file is marked as processed.

What if one memo has several different to dos?

It splits them. Each distinct action item becomes its own Linear issue with its own title, description, and priority.

Will the same memo get filed twice if the workflow runs every morning?

No. The workflow tracks which files it has already processed, so each recording only becomes Linear issues once.

What if I just say something vague like we should look at X?

It still lands in the backlog. Vague thoughts become a single investigation-style issue so the idea shows up for triage instead of getting dropped.

Can I use this with a different issue tracker like Jira or Asana?

Yes. The same pattern works with any project tracker we support. Ask Geni to swap Linear for your tool of choice when you customize the workflow.

Related templates

Find the customers stuck contacting support again and again

A board that ranks the people who opened three or more separate support conversations this month, reads their threads, and files the real fix.

App

Turn shipped Linear work into Intercom product announcements

A board your product marketer opens on every ship day to turn finished engineering tickets into announcements customers actually read in your Messenger.