Import: Outlook Emails (Lawvable)
What it does
This import adapter migrates a Lawvable Outlook email-processing skill into the mini-claude-for-legal standard format. Lawvable is a legal AI platform; its Outlook integration allows emails to be ingested, analysed, and routed into legal workflows. This adapter maps the Lawvable data model to the mini-claude-for-legal connector/import format so the email-processing logic continues to work in the new environment.
Legal email processing has specific requirements beyond standard email handling: privilege detection, matter tagging, deadline identification (limitation periods, response deadlines, regulatory notification windows), and client-communication classification (privileged, third-party, administrative).
Import config
| Field |
Source mapping |
Default if absent |
auth_method |
Legacy auth |
microsoft_graph_oauth2 |
mailbox_scope |
Legacy mailbox |
shared_legal_mailbox |
thread_depth |
Legacy thread_depth |
full (entire conversation chain) |
privilege_detection |
Legacy detect_privilege boolean |
true |
matter_tagging |
Legacy matter_tags config |
Auto-detect from subject line + sender |
action_extraction |
Legacy extract_actions boolean |
true |
deadline_detection |
Legacy detect_deadlines boolean |
true |
output_format |
Legacy format |
email_brief |
language |
Legacy lang |
auto-detect |
Dry-run preview
IMPORT PREVIEW — outlook-emails-lawvable
Source shape : Lawvable Outlook email integration
Auth : Microsoft Graph OAuth2
Mailbox : shared_legal_mailbox
Thread depth : full
Privilege detection: enabled
Matter tagging : auto-detect
Action extraction : enabled
Deadline detection : enabled
Output : email_brief
Email processing pipeline (post-import)
- Authentication: Microsoft Graph API OAuth2; application-level permissions for shared mailbox access; ensure
Mail.Read and Mail.ReadBasic scopes; do not request Mail.Send unless required.
- Ingestion: fetch emails with metadata (sender, recipients, date, subject, attachments); preserve threading via
conversationId.
- Privilege classification:
- Attorney-client privilege: sender or recipient is
[name]@[lawfirm]; subject line contains "privileged", "legal advice", "confidential"
- Work product: created in anticipation of litigation
- Mark non-privileged external communications separately
- Matter tagging: match subject/sender against matter reference database; tag with matter ID.
- Language detection: detect Arabic, French, English, other; route accordingly.
- Action extraction: identify:
- Requests for action (reply needed, document needed, decision needed)
- Deadlines stated in email body
- Regulatory notification windows (e.g. "please respond by [date]")
- Output: structured email brief per thread.
Legal-specific processing rules
- Privileged emails must never be sent to third-party AI services without explicit client consent and appropriate DPA/NDA coverage.
- Arabic emails: UAE government correspondence and local counsel emails are frequently in Arabic; ensure Arabic-language parsing is enabled.
- Bilingual threads: MENA legal correspondence often mixes Arabic and English in the same thread; handle language switches gracefully.
- Regulatory correspondence: emails from DFSA, CBUAE, UAE Ministry of Justice, Lebanese Ministry of Justice, ACPR (France) should be flagged with HIGH priority and deadline detection applied rigorously.
- Limitation period triggers: a demand letter or notice of claim starts the limitation clock; always flag and record the date received.
Failure modes
| Error |
Likely cause |
Resolution |
auth_failure |
OAuth2 token expired or scope insufficient |
Refresh token; verify Mail.Read scope is granted |
thread_truncated |
Legacy set thread_depth: 1 |
Override to full for legal context |
privilege_false_positive |
Law firm email domain not configured |
Configure firm domains in privilege-detection config |
arabic_garbled |
Encoding issue in Arabic emails |
Force encoding: utf-8; re-ingest |
deadline_missed |
Email contained informal deadline not detected |
Expand deadline-detection keywords to include informal language |
Related skills
- [[import-meeting-briefing-anthropic]]
- [[import-docx-processing-anthropic]]
- [[import-pdf-processing-anthropic]]
- [[connector-outlook-graph]]
- [[ops-legal-inbox-triage]]
1---2name: import-outlook-emails-lawvable3description: Use when migrating a Lawvable Outlook email-processing skill into the mini-claude-for-legal format. This adapter maps the legacy Lawvable email-ingestion configuration — Microsoft Graph API authentication, email threading, legal-matter tagging, privilege flagging, and action-item extraction — into the standard skill model. Triggers on import of any Lawvable-native Outlook integration workflow.4license: MIT5metadata:6 id: import.outlook-emails-lawvable7 category: import8 jurisdictions: [__multi__]9 priority: P310 intent: [__import__, outlook, email-processing, lawvable, migration, legal-ops]11 related: [import-meeting-briefing-anthropic, import-docx-processing-anthropic, import-pdf-processing-anthropic, connector-outlook-graph]12 source: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/import-outlook-emails-lawvable13 upstream: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)14 version: "1.0"15---1617# Import: Outlook Emails (Lawvable)1819## What it does2021This import adapter migrates a **Lawvable Outlook email-processing skill** into the `mini-claude-for-legal` standard format. Lawvable is a legal AI platform; its Outlook integration allows emails to be ingested, analysed, and routed into legal workflows. This adapter maps the Lawvable data model to the `mini-claude-for-legal` connector/import format so the email-processing logic continues to work in the new environment.2223Legal email processing has specific requirements beyond standard email handling: **privilege detection**, **matter tagging**, **deadline identification** (limitation periods, response deadlines, regulatory notification windows), and **client-communication classification** (privileged, third-party, administrative).2425## Import config2627| Field | Source mapping | Default if absent |28|---|---|---|29| `auth_method` | Legacy `auth` | `microsoft_graph_oauth2` |30| `mailbox_scope` | Legacy `mailbox` | `shared_legal_mailbox` |31| `thread_depth` | Legacy `thread_depth` | `full` (entire conversation chain) |32| `privilege_detection` | Legacy `detect_privilege` boolean | `true` |33| `matter_tagging` | Legacy `matter_tags` config | Auto-detect from subject line + sender |34| `action_extraction` | Legacy `extract_actions` boolean | `true` |35| `deadline_detection` | Legacy `detect_deadlines` boolean | `true` |36| `output_format` | Legacy `format` | `email_brief` |37| `language` | Legacy `lang` | `auto-detect` |3839## Dry-run preview4041```42IMPORT PREVIEW — outlook-emails-lawvable43Source shape : Lawvable Outlook email integration44Auth : Microsoft Graph OAuth245Mailbox : shared_legal_mailbox46Thread depth : full47Privilege detection: enabled48Matter tagging : auto-detect49Action extraction : enabled50Deadline detection : enabled51Output : email_brief52```5354## Email processing pipeline (post-import)55561. **Authentication**: Microsoft Graph API OAuth2; application-level permissions for shared mailbox access; ensure `Mail.Read` and `Mail.ReadBasic` scopes; do not request `Mail.Send` unless required.572. **Ingestion**: fetch emails with metadata (sender, recipients, date, subject, attachments); preserve threading via `conversationId`.583. **Privilege classification**:59 - Attorney-client privilege: sender or recipient is `[name]@[lawfirm]`; subject line contains "privileged", "legal advice", "confidential"60 - Work product: created in anticipation of litigation61 - Mark non-privileged external communications separately624. **Matter tagging**: match subject/sender against matter reference database; tag with matter ID.635. **Language detection**: detect Arabic, French, English, other; route accordingly.646. **Action extraction**: identify:65 - Requests for action (reply needed, document needed, decision needed)66 - Deadlines stated in email body67 - Regulatory notification windows (e.g. "please respond by [date]")687. **Output**: structured email brief per thread.6970## Legal-specific processing rules7172- **Privileged emails must never be sent to third-party AI services** without explicit client consent and appropriate DPA/NDA coverage.73- **Arabic emails**: UAE government correspondence and local counsel emails are frequently in Arabic; ensure Arabic-language parsing is enabled.74- **Bilingual threads**: MENA legal correspondence often mixes Arabic and English in the same thread; handle language switches gracefully.75- **Regulatory correspondence**: emails from DFSA, CBUAE, UAE Ministry of Justice, Lebanese Ministry of Justice, ACPR (France) should be flagged with HIGH priority and deadline detection applied rigorously.76- **Limitation period triggers**: a demand letter or notice of claim starts the limitation clock; always flag and record the date received.7778## Failure modes7980| Error | Likely cause | Resolution |81|---|---|---|82| `auth_failure` | OAuth2 token expired or scope insufficient | Refresh token; verify `Mail.Read` scope is granted |83| `thread_truncated` | Legacy set `thread_depth: 1` | Override to `full` for legal context |84| `privilege_false_positive` | Law firm email domain not configured | Configure firm domains in privilege-detection config |85| `arabic_garbled` | Encoding issue in Arabic emails | Force `encoding: utf-8`; re-ingest |86| `deadline_missed` | Email contained informal deadline not detected | Expand deadline-detection keywords to include informal language |8788## Related skills8990- [[import-meeting-briefing-anthropic]]91- [[import-docx-processing-anthropic]]92- [[import-pdf-processing-anthropic]]93- [[connector-outlook-graph]]94- [[ops-legal-inbox-triage]]