Requirements
Connecting Google Docs takes an active account plus OAuth client credentials, granted by signing in with your account — no other setup is required.[3]
Get your Google Docs credentials
You’ll be redirected to sign in and approve access — your password is never shared with WEXTL.
- Client IDtext
Optional. Your own OAuth 2.0 Client ID from Google Cloud Console. Leave empty to use the platform app.
[1] - Client Secretpassword
Optional. Client Secret for the same OAuth client. Leave empty to use the platform app.
[1] - Additional Scopesarray
Optional. Extra Google OAuth scopes to request on top of the default ones, one full scope URL per item (for example https://www.googleapis.com/auth/drive). Duplicates of the default scopes are ignored. Use this with your own Client ID, and enable the same scopes on its OAuth consent screen.
[1]
Connect Google Docs in WEXTL
- Log in to your WEXTL account, add the Google Docs node module to your workflow, and click Create new credential.
- Optional: In the Credential name field, enter a name for the credential.
- Enter the authentication credentials you copied from your Google Docs account, or follow the on-screen instructions to create the credential.
- If prompted, authenticate your account and confirm access.
- If you want to make changes to your credential in the future, follow the steps in Manage credentials →

Notes
Credentials are org-scoped; share them with teammates from the Credentials picker on any of its nodes.For detailed information on connecting an application, see Connect an application →
Google Docs node modules
The list below is a reference of every Google Docs node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.
Expand any Google Docs node module below to see exactly what it takes in, what it returns, and what connection it needs.
| Field | Type |
|---|---|
DocumentRequired | choice |
Suggestions View Mode | choice |
Include Tabs Content | boolean |
| Field | Type |
|---|---|
Document ID | text |
Title | text |
Revision ID | text |
Suggestions View Mode | text |
Tabs | array |
Body | object |
Document Style | object |
Named Styles | object |
Headers | object |
Footers | object |
Footnotes | object |
Lists | object |
Named Ranges | object |
Inline Objects | object |
Positioned Objects | object |
Suggested Document Style Changes | object |
Suggested Named Styles Changes | object |
| Field | Type |
|---|---|
Title | text |
| Field | Type |
|---|---|
Document ID | text |
Title | text |
Revision ID | text |
Suggestions View Mode | text |
Tabs | array |
Body | object |
Document Style | object |
Named Styles | object |
Headers | object |
Footers | object |
Footnotes | object |
Lists | object |
Named Ranges | object |
Inline Objects | object |
Positioned Objects | object |
Suggested Document Style Changes | object |
Suggested Named Styles Changes | object |
Templates
Look for Google Docs templates in the WEXTL template library.
Browse templates →Explore alternative apps
- Bitwarden[2]Manage organization members, groups, collections, and policies in Bitwarden.
- BoxStore, share, and automate files and folders in Box.
- BitbucketBitbucket Cloud REST 2.0 — repositories, pull requests, pipelines, commits, and webhooks.
- AdafruitAdafruit IO cloud for IoT feeds, groups, and device data streams.
- AssemblyAISpeech AI APIs for transcription, understanding, and voice-powered applications.
References
- WEXTL® Google Docs Source Code connector implementation.
- Our users use cases and automations.
- Official API Documentation for Google Docs.
- WEXTL® visual workflow builder data.
Last updated: Jul 22, 2026 23:18
