Description
HTML to Google Docs Node for n8n
This is an n8n community node that allows you to upload HTML content directly to Google Docs. With this node, you can automate the creation of Google Docs documents from HTML content in your n8n workflows.
Features
- Convert HTML content to Google Docs format
- Create new Google Docs documents programmatically
- Support for rich HTML formatting (headings, lists, links, etc.)
- Authentication via Google OAuth2
Installation
Follow the installation guide in the n8n community nodes documentation.
Alternatively, you can install the node directly from npm:
npm install n8n-nodes-htmltogoogledocs
Operations
This node allows you to:
- Upload HTML content to Google Docs
- Create new Google Docs documents with HTML content
Credentials
To use this node, you need to authenticate with Google Drive using OAuth2.
Prerequisites
- You need a Google account
- Enable the Google Drive API in your Google Cloud Console
- Create OAuth2 credentials (Client ID and Client Secret)
Setup
- In n8n, go to Settings > Credentials
- Click on "Add Credential"
- Select "Google Drive OAuth2 API" (predefined credential)
- Click on "Connect my account" and follow the OAuth flow
Compatibility
This node is compatible with n8n version 0.1.0 and above.
Usage
- Add the HTML to Google Docs node to your workflow
- Configure the credentials by selecting your Google Drive OAuth2 account
- Enter the document name for your new Google Doc
- Provide the HTML content you want to upload
- Execute the workflow
The node will create a new Google Doc with your HTML content converted to Google Docs format.
Resources
Release Process
This project uses semantic-release to automate the release process. All commits must follow the Conventional Commits specification.
Commit Message Format
Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
The header is mandatory and the scope of the header is optional.
Types
feat: A new featurefix: A bug fixperf: A code change that improves performancerevert: Reverts a previous commitdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor: A code change that neither fixes a bug nor adds a featuretest: Adding missing tests or correcting existing testsbuild: Changes that affect the build system or external dependenciesci: Changes to our CI configuration files and scriptschore: Other changes that don't modify src or test files
Release Automation
Releases are automatically created when changes are merged to the master branch. The semantic-release tool analyzes commits and determines the next version number based on the commit types:
featcommits will trigger a minor version bumpfixcommits will trigger a patch version bumpBREAKING CHANGEin the commit body will trigger a major version bump
