Skip to main content
OfficeIMO Docs Search documentation/

Workflow Finder

Edit on GitHub

Choose an OfficeIMO or PSWriteOffice workflow by the input you have and the artifact you need.

Start with the job, not the package name. Each route below links to the smallest useful package set, a runnable pattern, and the evidence available for the generated result.

Build and deliver

Starting pointResultRecommended route
Application objects or a DataTableXLSX reportOfficeIMO.Excel, or Export-OfficeExcel from PowerShell
Template plus business dataDOCX report or contractOfficeIMO.Word, or the PSWriteOffice Word commands
Structured report modelPDFOfficeIMO.Pdf for native authoring; add a focused converter for Word, HTML, RTF, or OpenDocument input
Brand brief and metricsPPTX presentationOfficeIMO.PowerPoint designer and template APIs
Topology or inventoryVSDX plus image previewOfficeIMO.Visio diagram builders
SQL queryExcel or CSV, optionally written back to SQLDbaClientX and PSWriteOffice reporting

PowerShell users can start with the PSWriteOffice recipe gallery for Excel, Word/PDF, native PDF, Markdown, CSV, Reader, and PowerPoint patterns.

Convert and publish

InputUseful outputsGuide
HTML or MHTMLImages, PDF, Word, Markdown, RTFRender and convert HTML
OneNote .one, .onetoc2, or .onepkgImages, HTML, Markdown, PDF, Reader resultsExport and convert OneNote
RTFRTF edits, Word, Markdown, HTML, PDF, Reader resultsRTF workflows
OpenDocument ODT, ODS, or ODPOffice formats, PDF, inspection resultsOpenDocument workflows
PowerPointSlide images, PDF, content extractionPowerPoint image export

Extract, index, and validate

Use the OfficeIMO.Reader documentation when the destination is a normalized extraction model rather than another document. Install selective Reader adapters for a service with a known format set, or OfficeIMO.Reader.All for a host that deliberately accepts the complete adapter family.

For generated output, keep validation close to the workflow:

  • Validate DOCX, XLSX, PPTX, VSDX, and package relationships before delivery.
  • Inspect conversion diagnostics instead of assuming every source feature maps losslessly.
  • Apply bounded reader profiles to uploaded or otherwise untrusted documents.
  • Keep a representative output artifact or visual baseline when layout matters.

See the generated output gallery for real previews tied to examples and tests.