Google Docs that a workflow keeps up to date

Google Docs in MadMax is a writing target and a reading source. A workflow creates a document, appends text to the end of one, and reads a document's content back out. That is enough for the jobs that actually come up: a running log that an AI agent keeps current, a report generated on a schedule and approved before it exists, a policy doc an agent answers questions from. Because append_text always adds at the end, a document becomes an append-only log several workflows can write to in order. Reading pairs with save to knowledge: fetch the document, flatten its body to plain text with a short code step, and index it so an agent answers from it. There are no Docs triggers, so runs start from a schedule, a webhook, a form, an email or another app's event, and sharing a document you created is a Google Drive operation on the same account. Describe it in plain English and MadMax builds the workflow, runs the summary on a real record, and previews the exact text it would append before touching the document.

What teams build

• A webhook receives each call summary from your phone system, an AI summarize step turns the transcript into four lines with the customer name and the one follow-up, and append_text adds them with the date to the team's call-notes doc, newest at the bottom.
• A Friday schedule reads the week's numbers from a data store, an AI agent writes the report as plain prose, an approval emails the manager a one-click approve or reject, and on approve create_document makes "Ops report, week 43" and the text is appended into it.
• A nightly schedule runs get_document on the support policy, a code step flattens the body to text, and a save to knowledge step indexes it under the document's id, so a support agent in another workflow answers refund and shipping questions from the current policy.

How it connects

One click. Press Connect on the Google Docs card in Settings → connectors and approve the documents permission on Google's consent screen. MadMax stores the grant encrypted, refreshes the access token before it expires, and never shows it back; a revoked grant shows a reconnect button that re-authorizes the same connection. Connections are per workspace, private to you or shared with the team, and each Docs step picks which account it writes as. See managing connections.

Related

• Save to knowledge
• Code step
• Approval step
• Managing connections
• Google Drive automation