Voice workflows

Understand triggers and automation

Learn the difference between voice phrases, hotkeys, desktop actions, AI tool calls, and workflow triggers before you automate a Vowise flow.

Audience: Users and builders who want voice commands, Shortcuts, AI Chat tools, or repeatable capture-to-review workflows.

Time: 18 minutes

Level: Advanced

Scenario

Start with the workflow this guide is designed for before moving into the steps.

As an automation user, I want to know which trigger starts which action so I do not confuse a visible shortcut with an AI workflow or a backend job.

You can design one safe trigger, choose whether it should be read-only or workflow-triggering, test it with demo data, and know where to disable it.

Complete steps

Name the job before the trigger

Write the job in one sentence: search records, start capture, paste text, take a screenshot, open a URL, ask AI Chat, or start a review/content workflow.

The action has one owner and one expected result.

You know whether the result is visible immediately or finishes later.

Choose the trigger family

Use hotkeys or desktop buttons for local actions, voice phrases for hands-free control, Shortcuts/API for repeatable external flows, and AI tool triggers only when the assistant needs to decide from context.

Local system permissions are granted before desktop actions run.

External triggers keep API keys and private data out of screenshots.

Set the risk level

Separate read-only actions from workflow triggers and write actions. Search, summarize, and inspect can be lightweight; creating follow-up tasks, queueing review, or starting content generation needs clearer confirmation.

Read-only actions cannot silently mutate records.

Workflow triggers show what will be created or queued.

Test with a visible fallback

Run the trigger with demo data first. Keep the manual button, search field, or normal workflow visible so you can recover if recognition or automation chooses the wrong path.

The trigger works twice with the same phrase or shortcut.

You know how to disable or edit it from settings.

Audit what happened

After a workflow trigger runs, look for the visible result: a new record, a queued review item, a content job, a follow-up task, or an AI Chat response with source context.

The output points back to the source record or command.

Unexpected results are edited, disabled, or reported before using private data.

Details

Trigger types

A trigger is only the starting signal. The important part is the action it is allowed to start.

Voice phrase: good for hands-free search, capture, screenshot, link, and assistant actions.
Hotkey or floating control: good for fast desktop recording and paste/insert behavior.
Shortcuts/API: good for repeatable external flows with stored secrets.
AI tool call: good when AI Chat needs to search Vowise data or trigger a scoped workflow.

Live AI and trigger workflows

Live AI conversation is a conversation mode, not a replacement for every workflow trigger. Use it for quick spoken clarification, then hand off to record chat, Content Studio, Journal, or API flows when the result should use sources or create something.

Realtime voice input can create the prompt faster, but the workflow still needs the right source and confirmation.
Record-grounded questions should run from the record or AI Chat source context.
Content generation should land in Content Studio so topics, images, items, and review state remain visible.
Automation triggers should have an obvious stop, edit, or disable path.

Read-only vs workflow trigger

Public docs should make this distinction explicit because the user experience is different.

Read-only: search records, search favorites, inspect journal context, or summarize visible material.
Workflow trigger: start research, start content generation, queue review, create a follow-up task, or save a journal reflection.
Write or external actions need stronger confirmation and should stay out of first tests.