Save Outlook emails and attachments to Clio: four practical workflows

For a law firm running on Microsoft 365, Outlook is the front door for almost everything that arrives by email: opposing counsel correspondence, expert reports, signed engagement letters, executed agreements, court NEFs, banking confirmations, insurance acknowledgements, and the day-to-day client back-and-forth. Most of these emails have one or more attachments. Most of those attachments are the actual artifact — the email body is context, but the PDF is the document the matter needs.

Clio is where the document needs to live. Specifically, it needs to live inside the right matter, in a folder that makes sense, under a filename that someone will be able to find six months from now when the file gets pulled for production or appeal.

The mismatch between the two is what creates the workflow problem. Outlook organizes by sender and thread; Clio organizes by matter. Outlook keeps attachments named whatever the sender called them; Clio benefits from filenames that include the parties, the document type, and the date. Outlook is per-user; matter documents are firm-wide. Closing the gap takes work, and the cost of doing it badly is documents that go missing or sit in someone's inbox instead of the matter file.

The four workflows below are the paths most firms actually use. They aren't mutually exclusive — most firms mix them depending on volume and the type of attachment.

Power Automate (the workflow tool included with most M365 business plans) gives you full programmatic access to Outlook and to Clio's REST API. The general flow: a trigger fires when an email arrives, the flow filters by some criterion (subject line tag, sender, mailbox), extracts the attachments, looks up the right Clio matter, and POSTs each attachment to Clio's Documents endpoint.

What it's good at. Automating recurring patterns. If your firm has a shared mailbox where opposing counsel sends discovery, or where carriers send claim updates, you can route attachments into the corresponding matter without any manual click. The same is true for "anything tagged [Smith v Jones]" workflows — paralegals tag the subject, the flow does the rest. Once it's built, it's invisible.

What it costs. A premium Power Automate license is needed if you're using the standard HTTP action to call Clio's API (premium connectors are required for arbitrary REST). Many firms already have these licenses bundled in their M365 plan; some don't. The build itself is one afternoon for a tech-comfortable paralegal, an hour or two for an outside consultant, and ongoing maintenance is low — the main upkeep cost is matter-mapping logic when your firm changes how it names matters.

The matter-mapping problem. Power Automate doesn't know which matter an email belongs to. You have to tell it. Common patterns: (a) require subject-line tags like [Matter 2024-103] (adapt the format to your firm's own matter-naming convention) and parse them; (b) look up the matter by client email address (works only when the sender is the client, not opposing counsel); (c) drop into a triage inbox and have a human assign matter manually before the flow files. (a) is the most common because it's the most reliable.

Where it doesn't shine. One-off attachments that don't fit a pattern. Power Automate is built for repeatable workflows; the cost of building a flow for a single workflow you'll run twice is higher than just clicking through. It's also less useful when the trigger is an attachment that arrived via a non-email channel (a portal download, a court e-filing notice link, a Dropbox share) — those are the cases where browser-based tools fit better.

A category of tools that sit in the browser and let you right-click any download link to send the file directly to Clio without ever touching your computer. They work wherever a document is reachable as a download link — Gmail attachments, court portals, evidence platforms, and any other browser-served file. Outlook on the web is the exception: it serves attachments through an internal API call rather than a link, so these tools cannot reach them from the reading pane, and the attachment has to be saved to disk first. Examples include Send to Case and a handful of similar browser extensions purpose-built for legal practice. Each has its own trade-offs on supported sites, file-size limits, pricing, and feature depth (smart filenames, folder routing, batch upload).

What this category is good at. The cases where the attachment matters more than the email envelope. Most files don't need the email body preserved — a signed contract, a witness statement, a deposition exhibit — and a browser tool delivers the bytes to the matter without the surrounding noise. Its real reach is outside the inbox: the same right-click delivers a court NEF, a Dropbox-shared discovery production, or an insurance carrier upload. For a paralegal whose day mixes Outlook with browser portals, it covers the portal half well and the Outlook half only after a save to disk.

Where it doesn't shine. If you need the email itself as a record — the headers, timestamps, the body language — a browser tool that only captures attachments isn't the right answer. Clio's official integration (Option 1) or Power Automate (Option 2) are better when provenance of the email matters as much as the file. The bigger limit is Outlook itself. These tools need a download link to act on, and Outlook on the web serves attachments through an internal API call instead, so there is no link to right-click; Outlook for Windows is outside the browser altogether. Either way the attachment has to be saved first, which removes most of the advantage. If your document volume arrives predominantly as Outlook mail, Option 1 or Option 2 will serve you better.

Time to first attachment. Manual is instant — zero setup. Clio's official integration takes 5-15 minutes to install and authorize for your user. A browser tool is roughly the same: install, connect to Clio, ready. Power Automate is the outlier: building the first flow takes one to three hours including matter-mapping logic and testing.

Cost per attachment after that. Manual is the slowest — two to three minutes per attachment for a paralegal, including matter navigation and filename cleanup. The official integration is faster (closer to 30-60 seconds) but still requires a human click per email. A browser tool is roughly the same range as the official integration. Power Automate, once running, is functionally free per attachment — the human cost is in handling the cases the flow's matter-mapping logic can't resolve.

Licensing. Manual is free. The official Clio integration is included in Clio Manage. Power Automate may require a premium license depending on your M365 plan; verify with your IT before promising the build to partners. Most browser tools have a free tier with a monthly upload cap; paid tiers handle higher volume.

What firms actually do. The realistic answer is some combination. Solos and small firms typically run manual + Clio's official integration and call it a day; the volume doesn't justify automation. Mid-size firms with active intake or carrier-correspondence workflows usually add Power Automate or a browser tool to handle the high-volume slice. Firms that work heavily out of court portals and insurance systems often lean on browser tools as the primary surface because Outlook isn't actually their hottest document source — the portals are.