Import Google Docs from Drive into WordPress drafts—editorial inbox, field mapping, and secure OAuth on your server.

4wpdev

Anatoliy Dovgun

4WP Drive connects a Google Drive folder workflow to WordPress: writers drop documents in Drive, editors review them in an admin Inbox, and approved content becomes draft posts—without copy-paste.
A plugin by <a href="https://4wp.dev/" rel="nofollow ugc">4wp.dev</a>.
<h4>Perfect for</h4>
<ul>
<li>Editorial teams that draft in Google Docs but publish in WordPress</li>
<li>Agencies with a shared Drive <code>incoming/</code> folder and a review step before publish</li>
<li>Content pipelines that need structured front-matter (title, slug, categories, SEO fields) parsed from the doc header</li>
<li>Sites that want API credentials stored encrypted and OAuth handled server-side</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install and activate 4WP Drive.</li>
<li>Create Google OAuth credentials and connect Drive in Storage sources.</li>
<li>Set your Drive root folder ID; the plugin uses <code>incoming/</code> and <code>published/</code> subfolders.</li>
<li>Drop a Google Doc (with optional image) into <code>incoming/</code> or run Sync.</li>
<li>Open Inbox → Preview → Import as Draft or Reject.</li>
<li>On import, files move to <code>published/</code> in Drive.</li>
</ol>
<h4>Key features</h4>
<ul>
<li>Google Drive OAuth — connect an admin Google account; tokens stored encrypted</li>
<li>Folder sync — scan <code>incoming/</code> for new Google Docs and images</li>
<li>Admin Inbox — preview HTML, import as draft, or reject</li>
<li>Document template — front-matter lines before a separator (<code>---</code> or <code>=====</code>) map to post fields; body becomes post content (headings, lists, bold preserved)</li>
<li>Configurable field map — title, slug, categories, tags, author, dates, SEO meta (when supported)</li>
<li>Featured image — import image from the same Drive subfolder</li>
<li>REST API + WP-CLI <code>wp forwp-drive sync</code> for manual sync</li>
<li>Roadmap sources — GitHub Markdown/MDX and additional storage providers registered for future releases</li>
</ul>
<h4>Privacy</h4>
OAuth tokens and Google API credentials are stored in your WordPress database (encrypted). Document content is fetched from Google Drive only when an administrator runs sync or import. No visitor-facing tracking.
4WP is our project brand; the letters “WP” appear only as part of that brand name, not as a reference to WordPress. This plugin is not affiliated with, endorsed, or sponsored by WordPress.
Source code: <a href="https://github.com/4wpdev/4wp-drive" rel="nofollow ugc">github.com/4wpdev/4wp-drive</a>
<h4>Development</h4>
Human-readable PHP source is in the public GitHub repository above. The plugin ZIP includes <code>src/</code> (PSR-4 autoload via <code>src/Autoload.php</code> when <code>vendor/</code> is absent). No npm build step — admin scripts ship as plain JS in <code>assets/</code>.
Run tests: <code>composer install && composer test && composer run lint</code>
<h3>External services</h3>
This plugin connects to Google services when an administrator configures OAuth and syncs or imports documents.
<h4>Google OAuth 2.0</h4>
Used to authorize access to the connected Google account’s Drive files.
<ul>
<li>Authorization URL: <code>https://accounts.google.com/o/oauth2/v2/auth</code></li>
<li>Token URL: <code>https://oauth2.googleapis.com/token</code></li>
<li>Scope: <code>https://www.googleapis.com/auth/drive</code></li>
</ul>
When an administrator clicks Connect Google Drive, the browser is redirected to Google to sign in and grant access. WordPress stores refresh and access tokens encrypted in the site database. Client ID and Client Secret are stored encrypted (or may be defined in <code>wp-config.php</code>).
Google terms: https://policies.google.com/terms 
Google privacy: https://policies.google.com/privacy
<h4>Google Drive API</h4>
Used to list folders, download Google Docs (export as HTML/DOCX), and move files after import.
<ul>
<li>API hostname: <code>https://www.googleapis.com/drive/v3/</code> (and related export endpoints)</li>
</ul>
Requests are made server-side only when an administrator runs sync, preview, or import. Document metadata and file content are processed on your server to create WordPress posts.
Google Drive API terms follow Google Cloud / Google API Services terms linked from the Google Cloud Console.

Alternatives to 4WP Drive

Top alternatives