Voice to Notion with Cue

Quick answer: capture a note, not an unsupported conclusion

Open a private Notion draft you can edit, focus its text block, and use Cue Dictation to speak one observation at a time. Review the inserted text, add source links yourself, and give the page a descriptive project-and-topic title. Finish with separate Observation, Interpretation and Open question sections.

You need: Cue on Mac or Windows, the permissions and shortcut shown in your installed Cue settings, an editable Notion text field, and material you are allowed to record. You will make: a small source-linked knowledge note, not a meeting transcript, a task tracker or an automatically synchronized database.

Use a private practice page. Shared pages may expose edits while you are still drafting; do not assume that a later “send” step protects unfinished text. Check page access and inherited access before entering real information. See Notion's sharing and permissions guidance.

Set up a retrievable knowledge note

A useful knowledge note answers a future question. “Harbor export terminology — button and help-guide mismatch” is easier to recognize than “Quick thought.” It also tells a future reader which part of the project this note does and does not cover.

1. Choose one question. Write the project, topic and observation date in the draft. Keep the original source open beside it. For this exercise, use only the fictional material below.
2. Check the destination. Confirm you are in the intended workspace and a private editable page. Click the intended text block and type a harmless test word; remove that word yourself before dictating.
3. Choose Dictation, not Agent. Use the Dictation shortcut shown in Cue Settings. Confirm the recording state, speak a short factual passage, end recording using the current Cue control, then wait for processing. Check that the text arrived once in the intended block before continuing. For setup details, use the voice typing tutorial.
4. Label your reasoning. Say the words “Observation,” “Interpretation” and “Open question,” then manually format the headings as needed. Do not rely on a spoken command to create Notion blocks, tags or page properties.
5. Add evidence and retrieval cues. Paste the source link from the original source yourself, with a short label and date. Type a consistent project name and a few topic keywords in the note body. If your workspace uses database tags, set them yourself and follow its conventions.

Dictation enters the words you say; it is not a request to research a claim or reorganize a workspace. If you want a separate review, invoke Cue Agent using its configured shortcut and explicitly supply the relevant, authorized excerpt. Available app context depends on permissions and version. If the excerpt is missing, paste it into the task yourself. Ask for a draft only; the workflow here does not promise a native Notion connection, page creation or database synchronization.

Practice: a product terminology mismatch

This fictional example is about capturing project knowledge, not reporting completed work. None of the counts or labels below describe Cue, Notion or an actual usability study. Source IDs are practice references, not clickable evidence.

Speak the note itself

With Dictation active in your private practice block, try:

Read back the names, date, counts and uncertainty. Then add source IDs and format the note yourself. Copy real source links from their original location in a real project; do not dictate a guessed URL or let a model invent one.

Illustrative edited note, not a recorded Cue result

The important transformation is from a passing thought into a bounded claim with provenance. Do not upgrade “4 of 6 checked sections” to “most customers are confused,” or turn the open question into an approved task. Keep this note as context that a person or Agent can inspect later.

Reuse the note and review brief

Copy this structure into your private draft. Replace each placeholder yourself; leave missing facts explicitly unknown. You can dictate each section separately and organize it manually.

Title: [project + topic + specific observation]
Observed on: [date; version or environment when relevant]
Observation: [what I directly saw or what the source states]
Source: [source ID + verified link + relevant excerpt]
Interpretation: [my explanation, clearly marked as a hypothesis]
Open question: [what the evidence does not yet establish]
Retrieval words: [project name + topic + terms I would search]
Access: [who is allowed to read this note and its sources]

For an optional Cue Agent review, use the instruction below in an Agent task, not in Dictation. Supply only this note and the needed excerpts. This does not grant access to your whole Notion workspace or automatically transfer its context to other Agents.

Review this project knowledge note; do not publish or edit Notion.
Use only the note and source excerpts I provide below.
Separate direct observations, interpretations and open questions.
Attach a source ID to every factual statement.
Preserve counts, dates, names and uncertainty.
Flag unsupported conclusions, contradictions and missing source links.
Do not invent URLs, user-test findings, decisions, owners or deadlines.
Suggest a descriptive title and plain-text retrieval words.
Return a proposed note plus a short list of questions for me.

Note: [paste the draft]
Sources: [paste the authorized excerpts with their IDs]

Review that proposal against the original material before manually putting accepted changes into Notion. For a broader task handoff, see the Cue Agent tutorial.

Check evidence, retrieval and access

• Evidence: Can each observation be traced to the specified source? Do the denominator, date and environment survive? In the example, the evidence is a six-section documentation check, not a customer study.
• Uncertainty: Is the explanation still labeled a hypothesis? Is the unanswered question still unanswered? Remove any model-added claim that cannot be verified.
• Retrieval: Leave the page and try finding it by its distinctive title words in Notion workspace search. Notion's database search and workspace search cover different fields; tags alone are not a substitute for a useful title and body. Consult Notion's search guidance for the search mode you use.
• Links: Open each real source link yourself. A working link for you does not prove a teammate has access; verify the intended audience without broadening permissions unnecessarily.
• Sharing: Recheck the page and parent access before moving it into a shared area. Keep confidential excerpts out of public pages and out of prompts sent to services your organization has not approved.

The exercise is complete when you can find the note again, distinguish the three claim types, and return to the evidence. A longer note or an attractive layout is not a replacement for those checks.

Recover without losing or duplicating text

Dictation does not start or text goes to the wrong place

Check the microphone and app-control permissions requested by Cue, your configured shortcut, and the focused editable block. Follow your installed settings rather than assuming every Notion field behaves the same way. If the current Cue result view offers Copy, review that text and explicitly paste it into the intended private block. If it does not, do not assume a recovery clipboard exists; type a short note manually or retry only the missing passage.

The note appears twice or is only partly inserted

Inspect the destination before retrying. Preserve the correct text and remove duplicates deliberately. Canceling Cue stops an operation; cancellation is not an undo for text already entered or changes already visible to collaborators. If you need to revert an edit, inspect the page and use the editor's available recovery controls carefully.

An Agent turns a guess into a fact

Reject that sentence, retain the source excerpt, and ask for a revision that marks the claim unknown or hypothetical. Do not forward an unreviewed summary to Claude Code, Codex or another Agent as settled context. Include the source IDs and unresolved questions in any later handoff.

For a Cue problem, email eli@sophoninc.com with your OS, Cue version, Dictation or Agent mode, target field, and a short redacted description of what happened. Send no passwords, tokens, private workspace links or confidential source notes. Read Cue's privacy information before sharing diagnostic material.

FAQ