From download to your first legal workflow.
This guide explains what each part does, how to install n8n, import the legal workflow package, connect approved accounts, link Hermes and run a safe first test.
The conversation
You describe the task in plain language. Hermes selects the appropriate approved tool.
The workflow engine
n8n follows the defined steps: read, check, route, draft, record and return.
The controlled bridge
Model Context Protocol lets Hermes see and call tools that an administrator has exposed.
Prepare the basics
You do not need to know programming. You do need administrator access to the computer or server where n8n will run, plus permission to connect any firm accounts used by the workflows.
Self-hosted n8n
Run n8n on a firm-controlled Mac, PC or server. Docker is the simplest repeatable installation for most technical administrators.
n8n Cloud
n8n hosts the workflow engine. Setup is simpler, but the firm must review n8n Cloud’s current terms, region, access and retention controls.
- Download the starter ZIP using the button above and extract it to a private folder.
- Choose an administrator who can manage n8n, credentials, backups and updates.
- Choose a test workspace with synthetic matters—never begin with real client files.
- List approved systems such as Google Workspace, Microsoft 365, a database and an AI or OCR provider.
Install and open n8n
Ask your IT administrator to use the installation path appropriate for the firm. The commands below start a simple local Docker pilot and preserve n8n data in a Docker volume.
docker volume create n8n_data docker run -it --rm \ --name n8n \ -p 5678:5678 \ -v n8n_data:/home/node/.n8n \ docker.n8n.io/n8nio/n8n
- Open http://localhost:5678 on the same computer.
- Create the first n8n owner account when prompted.
- Keep the terminal window open while using this simple pilot command.
Production hosting needs HTTPS, a fixed encryption key, access restrictions, backups, log retention settings, updates and monitoring. Follow the official n8n Docker documentation.
Import the legal workflows
A workflow JSON file is a blueprint. Importing it adds the connected steps to n8n; it does not supply credentials or make the workflow safe to activate.
- Sign in to n8n and open Workflows.
- Choose Import from File from the workflow menu.
- Open the extracted hermes-n8n-workflow/n8n-workflow folder.
- Select one JSON file and import it. Repeat for each workflow you want to evaluate.
- Keep every imported workflow inactive until the credential and test steps below are complete.
Import one low-risk workflow first. Read every node from left to right and confirm what data it reads, where it writes, and whether it contacts an external provider.
Connect only approved accounts
Imported nodes will show missing credentials or placeholder settings. Open each node and select a firm-approved n8n credential. Never paste secrets directly into workflow text fields.
| Connection | Why a workflow may need it | What to check |
|---|---|---|
| Google or Microsoft | Email, calendars and matter documents | Use a dedicated service account where possible; restrict folders, mailboxes and calendar permissions. |
| PostgreSQL | Rules, case states, review queues and audit records | Create a limited database user; use parameterised queries and backups. |
| AI model | Classification, summaries and draft narratives | Review provider terms, retention, training policy, region and privilege implications. |
| OCR service | Reading scanned notices or PDFs | Do not send client material until the firm approves the provider and data-processing terms. |
| Court or legal data | Case status, cause lists, judgments and updates | Use an authorised source and verify results against the official record. |
- Replace every sample email address, folder ID, Sheet ID, database name and webhook URL.
- Add authentication to all webhooks and MCP triggers.
- Remove public-link permissions and restrict every output to named users.
- Configure n8n execution-data retention so unnecessary client content is not preserved.
Connect Hermes to n8n
Hermes needs an approved bridge before it can inspect or manage the n8n instance. The included optional n8n bridge uses the local n8n URL and an API key.
- In n8n, open Settings → API and create an API key for the Hermes connection.
- In Hermes, open Settings → MCP, find the optional n8n integration and install it—or ask the administrator to run the command below.
- Enter the n8n base URL, normally http://127.0.0.1:5678 for a same-machine pilot, and store the API key as a secret.
- Enable only the tools the user needs. Keep workflow activation and other mutating tools disabled initially.
- Start a new Hermes session so it loads the n8n tools.
hermes mcp install official/n8n
The bridge lets Hermes inspect or manage your n8n instance. The MCP Server Trigger inside n8n exposes selected legal workflows as agent tools. An administrator must authenticate and permission both layers before use.
Run one safe test
Use a fictional client, fictional counterparty and synthetic documents. Watch the n8n execution step by step before allowing Hermes or a schedule to start it automatically.
- Open the workflow in n8n and choose Test Workflow.
- Supply synthetic sample inputs and watch each node turn successful.
- Check the destination system: was the correct draft, folder or record created?
- Deliberately try missing data, duplicate data, an unavailable service and an unauthorised request.
- Confirm the workflow fails safely and records enough information for an administrator to investigate.
- Activate the workflow only after the responsible lawyer and administrator approve the test evidence.
No client data, no public links, no automatic external communication and no deadline relied upon without lawyer verification.
Six controls that are not optional.
A workflow that runs is not necessarily a workflow that is safe for a law firm. Treat production approval as a separate stage with documented owners and evidence.
Authenticated endpoints
Bearer or header authentication for MCP triggers and webhooks; no public unauthenticated entry points.
Least privilege
Dedicated accounts that can access only the mailboxes, folders, calendars and tables required.
Human approval
Mandatory approval before sending, sharing, filing, accounting or changing a material client record.
Data boundaries
Written approval for every AI, OCR, cloud-storage, court-data and notification provider.
Legal verification
Dates, authorities, conflict outcomes, status updates and compliance rules checked against primary sources.
Recovery and audit
Backups, error alerts, execution retention, incident procedures and an auditable change process.
Common setup questions.
Do I need to know coding?
No for ordinary use. A technical administrator should still review connections, expressions, permissions, hosting and failure behaviour before the firm uses the workflows with real data.
Does importing the ZIP immediately connect my data?
No. Extract the ZIP and import the JSON files individually. Credentials, folder IDs, recipients, database details and provider settings must be supplied separately.
Why should imported workflows remain inactive?
An active email trigger, schedule or webhook may begin processing immediately. Keep workflows inactive until you understand every node, replace placeholders, configure authentication and complete safe tests.
Is everything kept on my computer?
Not necessarily. Self-hosted n8n keeps the workflow engine under your control, but Gmail, Drive, cloud AI, OCR and data providers process selected information in their own systems. Use local services if complete data locality is required.
Can I activate every workflow together?
Do not do this for a first deployment. Start with one low-risk workflow, approve its permissions and outputs, test failures, document the result and expand gradually.
Where can I get official n8n help?
Use the official n8n documentation for current installation, credential, workflow and security instructions. This LexEdge page explains the legal-workflow package but does not replace upstream product documentation.
Download. Import. Test safely.
Begin with one synthetic matter and keep every external action behind human approval.