Google Docs
Askel connects to your customer's Google Workspace account and generates or updates documents in their Google Drive. Your product can create contract drafts, onboarding guides, and reports as native Google Docs without any manual copy-paste.
What you can do
Create documents from structured content
Use the Docs API batchUpdate endpoint to create a new Google Doc with headings, paragraphs, tables, and inline formatting from your product's data.
Insert content into existing documents
Append or insert paragraphs, tables, and named ranges into a document that already exists in the customer's Drive, useful for appending audit logs or progress sections.
Read document body and structure
Fetch the full structural content of a document, including paragraph elements, table cells, and inline objects, for parsing or summarising.
Set document sharing permissions
Create sharing permissions via the Drive API to make a document accessible to specific users or groups within the customer's domain.
Organise documents into Drive folders
Create folders or move newly created documents into an existing folder using the Drive files.update call, keeping the customer's Drive tidy.
Export documents in other formats
Download a Google Doc as PDF or DOCX using the Drive export endpoint, useful for archiving signed versions or attaching them to your product's records.
Generating onboarding welcome packets for new enterprise customers
You sell a compliance training platform. Ridgeline Software signs a new enterprise contract and expects a customised onboarding welcome packet in their Google Drive within 24 hours of signing. The packet includes account details, assigned courses, and the point-of-contact name.
- 1
Connect once
Ridgeline's Google Workspace admin completes OAuth in your product, approving the Drive and Docs scopes. Askel stores the refresh token.
- 2
Identify the target folder
Askel calls Drive files.list to enumerate the customer's top-level folders. Your CS team picks the Onboarding Documents folder as the destination.
- 3
Populate the template
Your product substitutes the account name, contract tier, assigned course list, and CS contact details into a document template using batchUpdate insert operations.
- 4
Create the document
Askel creates the new Google Doc in the selected folder and sets the sharing permission so all users in ridgeline.software can view it.
- 5
Write back the document URL
Askel returns the Google Doc URL to your product, which stores it on the customer record and sends it to the primary contact by email.
OAuth 2.0
The customer's Google Workspace admin or an individual user completes a standard Google OAuth consent flow, approving scopes for https://www.googleapis.com/auth/documents and https://www.googleapis.com/auth/drive. Askel stores the refresh token and handles silent renewal. No credentials are exposed to your codebase, and token refresh happens automatically.
How Askel sits between your product and the customer's system
FAQ for Google Docs
Does this require Google Workspace or does a personal Google account work?+
Can we update specific sections of an existing document?+
What scopes does Askel request?+
What happens if the customer revokes access?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.