Workflows that connect the work.
Feature pages explain what Ghost can do. These guides show how a real job moves from source to reviewed result across meetings, notes, tasks, accounts, research, browser work, and execution.
- Publication rule
- One page per recognizable job—not one page per mathematical feature pair.
Choose the outcome, then inspect the handoffs.
Every guide has its own search intent, one product-grounded example, a source-to-result sequence, review boundaries, and links back to the canonical feature owners.
Meeting lifecycle
Prepare with current context, carry decisions into work, and follow through after the call.
- Meeting notes to tasksTurn meeting notes into source-linked tasks with the stated owner, timing, Kanban status, and Epic context kept ready for follow-through.
- Meeting follow-up automationAssemble a meeting recap, source-linked tasks, a grounded email draft, and a later check without treating a draft as an automatic send.
- AI meeting prepBuild an AI meeting brief from Calendar, earlier meetings, open tasks, notes, email, and project context before the conversation starts.
Work intake
Turn requests and source material into work that remains traceable.
- Email to tasksTurn a request or commitment in Gmail into a source-linked Focus task with review, priority, Kanban state, and the original thread attached.
- Notes to tasksTurn selected note content into reviewable tasks with the source, reason, stated owner, timing, Kanban status, and Epic context still attached.
- Meeting notes to JiraTurn meeting evidence into reviewable Jira issue proposals with issue type, assignee, acceptance criteria, and a route back to the source.
- Voice to taskTurn a supported voice note into a reviewed task, note, scheduled run, or Calendar action while keeping the transcript and ambiguity visible.
- Slack to-do listTurn a Slack request or commitment into a source-linked to-do with the right owner, timing, Epic, Kanban state, and follow-through kept visible.
Research and creation
Move from source gathering to a reviewed artifact without losing evidence.
- Research to presentationMove from an AI research question to a source-backed brief, audience-specific outline, and reviewable presentation without losing the evidence.
- Website to spreadsheetTurn permitted website data into a reviewable spreadsheet or CSV with defined columns, source URLs, sample validation, and explicit refresh boundaries.
- Coding agent sandboxGive an AI coding agent a scoped repository workspace to inspect, edit, build, test, and return as reviewable changes without confusing a preview with deployment.
- AI web scraperUse an AI web scraper to collect permitted website data, retain source URLs, validate the fields, and continue into a spreadsheet, report, or scheduled check.
- AI report generatorUse an AI report generator to turn notes, web research, files, and data into a source-backed report, then continue into tasks, slides, or publishing.
Proactive operations
Run recurring or multi-step work with a clear trigger, state, and result.
- AI daily briefingCreate one selective AI daily briefing from Calendar, actionable email and Slack, open tasks, and unclosed meeting commitments.
- AI workflow automationUse AI workflow automation to understand incoming work, gather context, act across connected tools, request approval, and keep following the result.
Useful pages before more pages.
Ghost will add a workflow only when research shows a distinct job and the current product can explain it honestly. Search Console query overlap should decide whether adjacent pages expand, narrow, merge, or redirect. See the underlying feature index for the complete capability map.
Questions about connected workflows.
What is a connected AI workflow?
A connected AI workflow moves one job across the capabilities it actually needs—for example, from a meeting record to a reviewed task and follow-up—while keeping sources, state, and authorization boundaries visible.
Why not create a page for every pair of features?
Most mathematical feature pairs do not represent a distinct search intent or useful job. Ghost publishes a workflow page only when it has a clear input, transformation, output, and boundary from the existing feature pages.
Are these separate Ghost products?
No. The workflows explain how meetings, notes, to-dos, memory, connected accounts, browser work, and managed execution can participate in one requested outcome.
Start with one real workflow.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access