Academy → Using HermesOfficial documentation · clear explanation

Google Workspace — Gmail, Calendar, Drive, Sheets & Docs

Google Workspace — Gmail, Calendar, Drive, Sheets & Docs

Developer9 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Google Workspace — Gmail, Calendar, Drive, Sheets & Docs as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Setup, Gmail, Searching, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Google Workspace — Gmail, Calendar, Drive, Sheets & Docs without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Official page description

Send email, manage calendar events, search Drive, read/write Sheets, and access Docs — all through OAuth2-authenticated Google APIs

Topic map

What does the source say, and in what order?

  1. 01
    Setup

    Start here to understand the core idea or structure.

  2. 02
    Gmail

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Searching

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Reading

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Sending

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Custom From Header

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Replying

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Labels

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Calendar

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Drive

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

$GAPI gmail search "is:unread" --max 10 $GAPI gmail search "from:boss@company.com newer_than:1d" $GAPI gmail search "has:attachment filename:pdf newer_than:7d"
$GAPI gmail get MESSAGE_ID
# Basic send $GAPI gmail send --to user@example.com --subject "Hello" --body "Message text" # HTML email $GAPI gmail send --to user@example.com --subject "Report" \ --body "<h1>Q4 Results</h1><p>Details here</p>" --html # Custom From header (display name + email) $GAPI gmail send --to user@example.com --subject "Hello" \ --from '"Research Agent" <user@example.com>' --body "Message text" # With CC $GAPI gmail send --to user@example.com --cc "team@example.com" \ --subject "Update" --body "FYI"
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Google Workspace — Gmail, Calendar, Drive, Sheets & Docs” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?