hermes-gmail-send

To send Gmail from headless cron jobs without interactive OAuth, this skill uses a standardized token-driven workflow via the send_gmail.py script to dispatch emails automatically using pre-configured token files and client secrets.

Before automating Gmail sending, you need a valid OAuth token file and a client secret configured in your environment. The skill performs pre-flight checks to verify token presence and client secret availability before attempting to send.

The OAuth token workflow handles email automation in Hermes production by applying a standardized, token-driven approach that bypasses interactive login, allowing cron-driven notifications and other automated tasks to dispatch Gmail safely in headless environments.

Yes, you can pipe large email bodies via stdin when sending automated Gmail notifications. The skill supports both plain body text through the --body flag and stdin-based large bodies through --stdin for automation and notifications.

A key limitation of using OAuth tokens for automated Gmail in headless environments is the strict dependency on a valid token file and client secret; if these are missing or expired, the pre-flight checks will block the send attempt to prevent failures.