Workflows Overview
Workflows automate repetitive legal tasks in August. Define the task in natural language, and August plans execution steps. Run workflows on demand or on a schedule, and track progress through activity logs. The objective is consistency and time savings on recurring work.
This video demonstrates how to build and run workflows for repetitive legal tasks.
How to Build and Run a Workflow
Workflows are built once by an admin or power user, then run by any team member. The full pipeline runs five steps automatically.
Build — One-time setup
Name & describe
Give the workflow a clear name and describe the task in plain language.
Define steps + playbooks
Configure each step: document intake, AI analysis, playbook review, generation, tabular extraction. Add conditional logic (e.g., "if non-compete clause → flag for partner").
Set output + delivery
Choose output format—Word, Excel, email, or DMS—and configure delivery settings.
Test, publish → team-ready
Run a test pass, validate outputs, and publish so the whole team can execute it.
Run — Any team member
Pick workflow
Select the saved workflow from the Workflows panel.
Provide input docs
Upload or connect the relevant documents.
Click Run → Word · Excel · DMS
The workflow executes autonomously and delivers outputs in the configured format. Monitor progress in the activity log.
Build once · run as many times as the matter demands.
Running Workflows from Uploaded Documents
You can also initiate a workflow directly from an uploaded document. This is useful when you're working with a specific file and want to apply a workflow without navigating to the Workflows panel first.
Open document
Locate the document in your folder or upload it directly to your workspace.
Select workflow action
From the document actions menu, choose the workflow you want to run. Available workflows depend on your team's configuration.
Execute and monitor
The workflow executes on the selected document. Monitor progress in the activity log and access outputs when complete.
Running workflows from individual documents is ideal for one-off analysis when you don't need batch processing across multiple files.
Creating Workflows with Natural Language
Describe what you want accomplished in everyday language:
"Every Monday, review new documents in the ABC Matter folder and generate a summary of key developments."
"When new contracts are uploaded to the NDA folder, extract term, renewal, and termination provisions into a table."
"Daily: Check for new emails from opposing counsel and flag any mentioning deadlines."
Refine the request if outputs are too broad or too narrow. Use specific scope statements to improve repeatability.
Manual vs. Scheduled Runs
Mode | Best For |
|---|---|
Manual runs | One-off tasks, pilot testing, ad-hoc analysis |
Scheduled runs | Recurring reporting, regular review tasks, ongoing monitoring |
Choose cadence based on matter rhythm and stakeholder needs. Validate early runs before relying on scheduled automation.
Monitoring Workflow Activity
Activity logs provide visibility into step-by-step execution:
See which steps completed and in what order
Identify where adjustments are needed
Review outputs at checkpoints, especially for high-impact tasks
Treat activity review as part of quality control. Logs are useful for team visibility and process refinement.
Common Workflow Patterns for Legal Teams
Workflows follow pass-based patterns: orientation, issue spotting, and summary output.
First-pass Diligence Summaries
Upload a data room, run a workflow to extract key terms across all agreements, and generate an executive summary. Review the structured output, then drill into specific documents for deeper analysis.
Issue-Based Document Triage
Set a workflow to scan incoming documents for specific provisions—assignment clauses, change of control triggers, termination rights. Flag any that require attorney attention.
Internal Update Generation
Schedule a weekly workflow to summarize developments in a matter folder and produce a status update for the deal team or client.
When to Use Workflows
Use workflows when:
Tasks are repeatable and structured enough for consistent execution
Inputs follow a predictable pattern (same document types, same extraction goals)
You want to reduce manual effort on high-volume, lower-judgment work
Escalate judgment-heavy or novel issues to attorney review. Workflows handle the repetitive work so you can focus on decisions that require legal expertise.
Best Practices
Start narrow: Begin with a focused scope and expand once the workflow proves reliable.
Validate early runs: Review outputs carefully before putting a workflow into production.
Keep prompts concise: Specific, well-defined instructions produce more consistent results.
Use checkpoints: For multi-step workflows, build in review points to catch issues early.
What to Read Next
Assistant Overview for conversational task execution
Tabular Review for structured extraction across document sets
Playbooks to apply firm standards consistently