Google Docs Integration

The Google Docs integration lets your AI employee create a fully-formatted document in Google Docs, populate it with structured content (headings, paragraphs, lists, quotes, images), and share it with specific people as editor / commenter / reader. This is most visible in the Content Calendar Pipeline — every daily blog draft is delivered as a Google Doc in your Drive with you added as a reviewer — but the endpoint is available on demand for any workflow that needs "build me a Doc with this content and email the link to Sarah."

Docs are not created as plain text — they are built from a list of structured sections that Google Docs renders with proper formatting. Five section types are supported: headings (three levels, H1/H2/H3, for article titles and section breaks), paragraphs (body text, with HTML tags stripped so the rendered text is clean), lists (bullet items for enumerations), quotes (indented and italicized for callouts and pull quotes), and images (embedded inline with an optional caption and credit link underneath). The order of sections in the request is the order they appear in the Doc. This structured model is what lets a blog draft come out looking like a real article — hero image at the top, H1 title, alternating body paragraphs and subheadings, pull quotes where appropriate — rather than a wall of text.

When your AI employee creates a Doc, it can share it with any number of email addresses in a single call, specifying the role each person gets (writer/editor, commenter, or reader). The Google Drive API's permissions system handles the access grants, and the recipients get the same "Shared with you" experience they would get from any other shared Doc — the Doc appears in their Drive, they can open it with their normal Google account, and edits (if they have writer access) sync normally. Notification emails are suppressed by default to keep your AI employee from spamming everyone every time it creates a draft — the Doc shows up in the recipient's Drive quietly, and you decide when to notify them yourself.

Use a Google Doc when the content is long enough that it benefits from structured formatting, when you expect collaborative editing or commenting (multiple reviewers leaving inline notes), or when the content will be iterated on over several drafts. Use a plain email when the content is a single message meant to be read once and archived — a short update, a transactional notice, a one-off question. A rough heuristic: more than ~500 words or more than one reviewer, use a Doc; otherwise, send it as email text.

By default, Docs are created under the Sarudo service account's Drive and shared with you. For enterprise setups where you need Docs to appear directly in your own Drive (for audit, retention, or compliance reasons), Sarudo can be configured with Google Workspace Domain-Wide Delegation so the service account impersonates a user in your domain — Docs are then created as that user and show up in their real Drive rather than "Shared with me". This is a setup-team configuration, not a per-request option; mention it during onboarding if your compliance requirements need it.