Workflows
Templates and real use cases
Starter graphs you can rebuild in the editor—plus who uses them, how they are triggered, and links to step-by-step patterns.
Templates and real use cases
Templates here are blueprints: the same steps you add on the Build canvas, connected left → right. The product does not yet ship one-click “import template” files; copy the graph below, then tune prompts, keys, and URLs for your org.
For exact step tables and sample webhook JSON, use Example workflows after you pick a template below.
Starter templates (graphs to build)
Each row is a minimal chain. Extend it with Transform, Log, or extra LLM / HTTPS steps as needed.
| Template | Graph (in order) | Typical triggers | Maps to |
|---|---|---|---|
| Sanity check | Input → Output | Manual | Proves Run now and inputs work. |
| AI text pass-through | Input (e.g. message) → LLM → Output | Manual, Webhook | Summarize text (any prompt, not only summaries). |
| Grounded answer | Input (question) → KB preflight → LLM → Output | Manual, Webhook | Knowledge-assisted answer. |
| Classify & monitor | Input → LLM (strict JSON) → Transform → Log → Output | Webhook | Classify and branch. |
| Notify another system | Input → LLM (short summary) → HTTPS (POST) → Output | Webhook | HTTP callback after enrichment. |
| Daily / hourly digest | Input (optional defaults) → KB preflight or LLM → Output | Schedule, Manual | Scheduled digest. |
| Search on a live thread | Input (thread + session + query keys) → Agent tool (searchTool) → Output | Webhook, Manual | Agent tool on an existing conversation. |
| External app action | Input → MCP tool → Output | Webhook | MCP: create a task. |
| Custom script | Input → Code → Output | Webhook, Manual | Sandbox code. |
Webhook and schedule setup live under Run & automate in the editor. Secrets and URLs are described in Triggering workflows.
Real use cases (who, trigger, outcome)
These are how teams actually use linear workflows—not a feature guarantee for every integration, but realistic designs on top of the steps above.
Support and success
| Use case | Who | Trigger | What the flow does |
|---|---|---|---|
| Ticket summary for agents | Support leads | Webhook when a ticket is created or updated | Input receives ticket text; LLM produces bullets; Output returns summary for the helpdesk UI or a follow-up step. |
| Escalation prep | Tier-1 support | Manual or webhook | Input with thread/session ids; Agent tool (escalateConversationTool or your custom tool); Output returns tool result. |
| Canned KB reply draft | Success / support | Manual | KB preflight + LLM so drafts stay close to uploaded policies; human sends the final message in the channel. |
Sales and marketing
| Use case | Who | Trigger | What the flow does |
|---|---|---|---|
| Lead notes → CRM note | RevOps | Webhook from form or CRM | LLM turns free-text into a short CRM-safe note; HTTPS POSTs to your API; see HTTP callback. |
| Inbound email classification | Marketing ops | Webhook | LLM returns structured JSON (priority, topic); Transform + Log for routing; pattern in Classify and branch. |
Operations and internal tools
| Use case | Who | Trigger | What the flow does |
|---|---|---|---|
| Morning digest | Ops / leadership | Schedule | Same as Scheduled digest—fixed or default Inputs plus LLM or KB preflight. |
| Create tracking task | Any team with MCP | Webhook | MCP tool to Notion, Jira, or Slack (after integration is connected)—MCP example. |
Developers and platform teams
| Use case | Who | Trigger | What the flow does |
|---|---|---|---|
| CI / release blurb | Engineers | Webhook from CI with changelog text in JSON | Input → LLM (release notes style) → Output for Slack or email body. |
| Normalize payload | Backend | Webhook | Input → Code (parse, validate, reshape) → HTTPS or Output—Sandbox code. |
Choosing a template
- Event from another product → start from a Webhook row, match Input keys to the JSON you will POST (see cli-and-sdk).
- Recurring report → Schedule + Input defaults + LLM or KB preflight.
- Must use live chat context → plan Input keys for thread/session and use Agent tool or Agent turn only when those ids already exist—see warnings in Example 6.
Related
- Knowledge workers — grounded internal Q&A
- Managers — decks & PDFs — agent-generated .pptx and .pdf
- GitHub & engineering — repo tools + runbooks
- Example workflows — Step tables and sample JSON
- Workflows overview — Step types and triggers
- Triggering workflows (HTTPS & CLI) — curl and
wisebot workflow trigger - Use cases overview — Broader product scenarios (agents, channels, roadmap)