Word integration
Word is Microsoft's word-processing app, and the NoClick Word node manages the documents themselves rather than editing prose inside them. Through the Microsoft Graph API it can create, find, copy, move, rename, and delete .docx files, convert them to PDF or HTML, and handle sharing and version history. Use it to automate the document lifecycle around generated reports, contracts, and templates.
What you can automate with Word
Word operations
Document14
Document Permission5
Document Version3
Questions
Yes. The Word node can create a new blank document with optional initial text, or upload a complete .docx file you provide as base64. Both land in whatever OneDrive folder you specify, so generated reports can be filed exactly where you want them.
It can. The node converts a Word document to PDF and can return the result either as base64 content or as a download URL. It can also convert documents to HTML, which is useful when the content needs to appear inline somewhere.
The node can share a document with a specific person by email at read or write level, create anonymous or organization-scoped sharing links with optional expiry, and list, update, or remove existing permissions. You can also generate an embeddable preview link.
Yes. It can list the full version history of a document, fetch the details or content of a specific version, and restore a document to a previous version when a draft needs to be rolled back.
The node works at the document level rather than the paragraph level. It creates, uploads, converts, moves, copies, renames, and shares files, but it does not edit individual sentences inside an existing .docx. To produce new content, generate it upstream and supply it as the initial content or uploaded file.
