Use Cases for OpenClaw
Pre-built workflows you can deploy to your OpenClaw instance
Each use case is a guided setup session that walks you through connecting external services, configuring DNS, collecting API keys, and deploying OpenClaw agents — all through the same tunnel you already use for setup.
Cold Email Outreach Engine
Automated prospecting with verified emails and personalized outreach
Set up a complete cold email pipeline: find prospects, verify emails with Hunter, draft personalized messages with OpenClaw, and send through your own Google Workspace domain. Includes DNS authentication (SPF/DKIM/DMARC), mailbox setup, and a 5-agent OpenClaw workflow for research, verification, drafting, approval, and reply triage.
Intelligent Email Triage
AI-powered inbox management with style-matched replies and priority alerts
Connect your existing Gmail or IMAP inbox to an OpenClaw agent that scans, classifies, and drafts replies in your writing style. Includes PII protection via Zedly Shield, long-term memory via QMD and Dreaming, Telegram priority alerts, and a daily email digest. The agent gets smarter over time by learning your preferences from every interaction.
Vibe Coding — DevOps from Your Phone
Ship code, review PRs, and deploy from Telegram — with Shield safety rails and codebase memory
Turn OpenClaw into a mobile command layer for coding. Trigger feature work from Telegram, spawn a 4-agent team (planner, coder, tester, reviewer), and deploy to Vercel — without leaving your phone. Built-in Shield safety rails auto-redact API keys and gate destructive commands (force push to main, rm -rf, prod deploys, new npm installs) until you confirm in chat. QMD + Dreaming memory learns your codebase conventions over time so the agent gets genuinely smarter week by week.
Frequently Asked Questions
Zedly Shield is a runtime security layer (shieldd daemon) that sits between your OpenClaw agents and the LLM providers. Before any content leaves your machine, Shield intercepts it and replaces personally identifiable information — email addresses, phone numbers, names, financial details — with opaque tokens like [EMAIL_1] or [PHONE_2]. The LLM only ever sees tokenized data. When the response comes back, Shield rehydrates the tokens with the original values locally. Your raw data never reaches third-party servers.
Not in raw form. When workflows like Intelligent Email Triage process your inbox, Zedly Shield automatically redacts all PII before the content is sent to an LLM for classification or reply drafting. The LLM sees sanitized text with placeholder tokens. After processing, Shield restores the original values locally on your machine. You can verify and adjust exactly what gets redacted through the Shield dashboard at /shield on your Zedly instance.
Yes. Shield policies are fully configurable through the /shield dashboard or directly in the shieldd.toml configuration file. You can enable or disable redaction categories (emails, phone numbers, addresses, financial data), add specific terms to an allowlist so they pass through unredacted, or create custom redaction patterns for domain-specific sensitive data like internal project codes or client IDs.
Yes. Credentials you provide during setup — Gmail OAuth tokens, IMAP passwords, Telegram bot tokens — are encrypted and stored exclusively on your machine inside the OpenClaw credential store. Zedly’s servers never see or store your API keys. The setup tunnel only carries commands and responses; credential values are written directly to your local filesystem through the SSH connection.
When you disconnect the SSH tunnel, the session key is automatically revoked and no further access is possible. Zedly retains a log of commands executed during the session for your audit trail, but no files, emails, documents, or credentials are copied from your machine. All workflow data — processed emails, draft replies, memory files — stays entirely on your hardware.
The email workflows support Gmail natively via OAuth 2.0 with granular API scopes, and any other provider (Outlook, Yahoo, Fastmail, self-hosted) via standard IMAP/SMTP with app passwords. Gmail users get richer features like label management and thread grouping. IMAP users get full inbox scanning, classification, and reply drafting with the same Shield protection.
Yes. Workflows that support learning — like Intelligent Email Triage — use OpenClaw’s three-layer memory architecture. Daily Notes capture short-term context, QMD (Quiescent Memory Distillation) provides medium-term retrieval using hybrid BM25 and vector search, and Dreaming consolidates long-term patterns overnight. The agent gets smarter at categorizing your email, matching your writing style, and recognizing your VIP contacts over weeks and months.
Yes. Every OpenClaw agent runs in its own workspace with a separate memory store, configuration files, and credential scope. A triage agent cannot read a cold-outreach agent’s emails or memory, and vice versa. QMD indexes and Dreaming consolidation are scoped per-agent, so learned patterns from one workflow never leak into another.