Why workflows
You probably have a few jobs you run the same way every week — pulling a client memo, summarizing inbound emails, drafting a court filing from a template. Workflows let you describe that job once and re-run it on demand, on a schedule, or whenever something changes in your firm's data.
We used to spend an hour every Monday building the same status report. Now it runs at 8am and lands in our inbox.
— Pilot user · mid-size litigation firm
Two kinds of workflows
Sque has two flavors of workflows, and the difference matters when you're deciding which one to build.
You hit Run and watch the workflow execute step-by-step in the chat UI. Best for ad-hoc jobs where you want to review each step.
Runs unattended on a trigger (schedule, inbound email, new case file). You cannot start it manually — it fires when its trigger fires.
A workflow's kind is fixed at creation time. To switch from interactive to background, duplicate it and pick the new kind in the duplicate dialog.
Anatomy of a workflow
A step is one of:
| Step type | What it does |
|---|---|
| Prompt | Sends a prompt to the model with selected context |
| Tool call | Invokes an MCP connector (e.g. Gmail, Westlaw) |
| Branch | Routes the run based on the previous step's output |
| Wait | Pauses for a duration or until a condition is met |
| Output | Writes the result to a destination (briefcase, email) |
Build your first workflow
- 1
Open Workflows from the left nav and click New workflow.
- 2
Pick a kind — Interactive for hands-on, Background for fire-and-forget.
- 3
Drop in steps from the right-hand palette. Drag to reorder.
- 4
Wire inputs by clicking a step and selecting which previous step's output feeds it.
- 5
Publish when ready. Drafts only run for you; published workflows run for everyone in your firm.
Start with a single prompt step. You can always add tools and branches later — most useful workflows are 2–4 steps, not 20.
Real examples our customers run
Runs Mon & Thu at 8am. Summarises open matters and emails partners. Steps: Trigger → Prompt → Email.
On demand. Drafts a memo and conflict check from a client email. Steps: Email → Tool → Memo.
On demand. Builds a draft motion from a template and case file. Steps: Template → Cite → Docx.
Important notes
Background workflows count against your run quota even when no one is watching. Check Settings → Billing for your firm's monthly cap before publishing one that runs every 5 minutes.
Tool steps require an active connector. If the underlying connector is removed or its OAuth token expires, the workflow will fail at that step with a clear error — but it won't auto-retry.
Workflows respect the same permission model as the rest of Sque. A user who can't see a matter can't run a workflow that writes to it.
FAQ
Can I share a workflow with my team?
Yes — publishing it makes it available to everyone in your firm. Drafts stay private to you.
Can workflows call other workflows?
Not yet. It's on the roadmap; for now compose your logic in steps inside a single workflow.
What happens if a step fails halfway?
The run is marked failed and any partial output is preserved. You'll see which step failed and why in the run timeline.
What's next
Open Workflows in the left nav and click New workflow. Start with the Weekly digest template if you'd like a working example to remix.