#Openclaw / Google Drive integration

1 messages · Page 1 of 1 (latest)

fleet whale
#

Created my assistant Jethro a dedicated Gmail account. Want Jethro to create content I. Google Drive not .md files. Litttle help??

worn tokenBOT
timid radishBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

worn tokenBOT
shadow dawnBOT
#

Let me verify the docs path and the Google tooling specifics so I don't make up config.

#

I found the relevant bit: OpenClaw can use the gog Google Workspace CLI, but I want to confirm whether it can actually create/edit Google Docs directly or only search/export/copy them.

#

Yep, with one important catch.

The clean path is to give Jethro the gog Google Workspace skill and auth it to that dedicated Gmail:

gog auth credentials /path/to/client_secret.json
gog auth add jethro@gmail.com --services gmail,calendar,drive,contacts,sheets,docs
gog auth list

Then set GOG_ACCOUNT=jethro@gmail.com for that agent, and start a new session so the skill shows up.

The catch: based on the current bundled gog skill, it’s solid for Drive search, Gmail, and Sheets, but Google Docs support is mostly read/export/copy, not rich in-place doc authoring. So:

  • Sheets / Drive workflows: yes
  • True “write directly into Google Docs” workflows: not really first-class out of the box yet
#

If by “Google Drive” you mean actual Google Docs, I’d use a tiny custom skill/script against the Google Docs API. If you mean files stored in Drive, that’s easier.

Docs:

If you want, I can sketch the exact setup for either:

  1. Jethro writes to Google Sheets / Drive
  2. Jethro writes to real Google Docs

Also, what does openclaw --version show?

fleet whale
#

Anyone know how to set a history limit in open claw? My token usage claims with every single interaction.

shadow dawnBOT
#

Let me check the docs/code for the exact config name, I don’t want to guess and send you on a wild goose chase.

#

Yep, but there are 2 different “history” knobs in OpenClaw.

1) Raw chat history pulled in from Discord

If you want fewer recent Discord messages included each turn:

{
  messages: {
    groupChat: { historyLimit: 20 },
  },
  channels: {
    discord: {
      historyLimit: 20,
      dmHistoryLimit: 10,
    },
  },
# 
}
  • messages.groupChat.historyLimit = global default for group/channel chats
  • channels.discord.historyLimit = Discord override
  • dmHistoryLimit = DMs
  • 0 disables it

2) Session history across turns

There is not really a simple “keep last 20 turns” setting for the agent session itself.

For that, the usual controls are:

{
# 
  session: {
    reset: { mode: "idle", idleMinutes: 60 },
  },
  agents: {
    defaults: {
      compaction: { mode: "safeguard" },
      contextPruning: { mode: "cache-ttl", ttl: "1h" },
    },
  },
}

And manually:

  • /new
  • /reset