Document format conversion

Encodian converts files between formats, such as turning a Word document or web page into a PDF, as a step inside a Microsoft 365 workflow. A Beam agent starts this conversion once a document reaches an approved stage, such as final sign-off, and saves the converted file back to the same record so downstream steps don't wait on someone converting it by hand. A conversion that fails, or a source file that comes through corrupted or password protected, is flagged for a person to check rather than retried blindly. The agent doesn't change the source document itself, only the converted copy it produces.

Document merging and assembly

Encodian can combine several files, a cover page, a body document, and an appendix for example, into one output as part of a Microsoft 365 flow. A Beam agent assembles the approved set of files for a given record, following the order and template the team has already set, and attaches the combined document back to that record once assembly finishes. Where a required file is missing or a template doesn't match what's expected for that record type, the agent stops and flags it for a person rather than assembling an incomplete document. No file is removed from the source location during this step.

File metadata and text extraction

Encodian can pull metadata and text content out of a file, such as page count, author, or body text, for use elsewhere in a Microsoft 365 workflow. A Beam agent reads this extracted information once a document lands in the connected library and uses it to update fields on the matching record, such as marking a document's status or word count, following the mapping the account has approved. A file the tool can't read cleanly, or extracted content that looks incomplete against what's expected, is flagged for a person before those fields are updated. Nothing is inferred to fill a gap the extraction left.