Word

Microsoft integration · 4 node(s).

00Overview

Microsoft Word Online document operations

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Word

Word signs in with a Microsoft account you connect to Flomation — there is no API key or secret to paste. Connect the account once and every Word node picks it up automatically. Two optional fields let you steer it:

Field	Type		Details
Microsoft Account (email)	`string`
Microsoft OAuth Credential	`credential`		${credentials.MICROSOFT_ONEDRIVE}

Connect the Microsoft account to your Flomation user once — the same grant covers every Microsoft node, so you do not repeat it per flow. The optional Microsoft OAuth Credential field never shows a token: it references a managed credential (e.g. ${credentials.GOOGLE_DRIVE}), not an environment secret. Leave both fields blank and the node just uses your connected account.

02Create

Create Document

microsoft/word/create · Action

Create a new empty Word document in OneDrive

Field	Type		Details
Filename	`string`	Required	document.docx
Folder Path	`string`

Returns: tool_result, item_id, web_url, success, error

03Get

Get Document Metadata

microsoft/word/get_metadata · Action

Retrieve metadata for a Word document in OneDrive

Field	Type		Details
Document Item ID	`string`	Required

Returns: tool_result, name, size, created_at, modified_at, created_by, modified_by, web_url, mime_type, document, success, error

04Read

Read Document

microsoft/word/read · Action

Download a Word document as HTML or PDF from OneDrive

Field	Type		Details
Document Item ID	`string`	Required
Output Format	`string`		tml — choices: HTML, PDF

Returns: tool_result, content, title, web_url, success, error

05Replace

Replace Text

microsoft/word/replace_text · Action

Find and replace text in a Word document (via HTML conversion)

Field	Type
Document Item ID	`string`	Required
Search Text	`string`	Required
Replace With	`string`	Required

Returns: tool_result, content, replacements, success, error

06Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

Word actions locate a document by its OneDrive Item ID rather than by filename, so capture the Item ID returned by Create Document (or a OneDrive lookup) before wiring up the Read, Replace Text, or metadata nodes.
Create Document produces an empty file and does not accept body content, so any text must be added in a later step.
Reading a document as PDF returns the file as encoded binary rather than readable text; choose the HTML format when a downstream step needs to search or parse the document body.
Replace Text works against an HTML conversion of the document and returns the edited result as HTML in its output, so intricate formatting, tracked changes, and embedded objects may not survive and matching applies only to the visible text.
Replace Text reports how many substitutions it made, so check the replacement count to confirm the search text was actually found before relying on the result.