1 messages · Page 1 of 1 (latest)
Best supported path today is: give it a separate Gmail / Google Workspace account, not your personal inbox.
What I’d recommend:
- Create a dedicated mailbox like
bot@yourdomain.com - Connect that account to OpenClaw via Gmail/gog
- If you want it to react to new mail automatically, set up Gmail Pub/Sub
- Start with read + draft, then add send once you trust the setup
Why this is the best route:
- it keeps blast radius small if something goes wrong
- Gmail is the email path OpenClaw has solid docs/tooling for
- it’s much cleaner than handing your bot full access to your main inbox
If this is for a company/shared setup, the better pattern is a delegate account with limited scopes, not direct access to everyone’s mailbox. The docs are pretty explicit about starting small and using least privilege.
Relevant docs:
- Delegate architecture: https://docs.openclaw.ai/concepts/delegate-architecture
- Gmail Pub/Sub setup: https://docs.openclaw.ai/automation/cron-jobs#gmail-pubsub-integration
If you want, I can give you the exact setup steps for either:
- a simple personal Gmail bot inbox, or
- a proper Google Workspace delegate setup.
and icloud