Aspose Cloud

Convert Word documents, PDFs, spreadsheets, and presentations between formats and merge Word files through the Aspose Cloud document APIs. Agents drop format conversion into any flow, turning inbound DOCX into PDF or XLSX into CSV without a desktop app.

5 actions OAuth available

Aspose Cloud website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A signed statement of work is requested for a new client engagement

The agent pulls the master agreement, the pricing schedule, and the client-specific terms from document storage

Merge Word Documents appends the schedules to the base agreement in contract order

Convert Word Document renders the merged packet as a single PDF

The account owner reviews the assembled packet, checking that the right schedules made it in and the order is correct

The approved PDF routes to the e-signature platform

The engagement channel gets the packet link and the signature request status

What This Integration Enables

Aspose Cloud is document conversion as a stateless API call: the file goes in from FlowRunner storage, the converted result comes back to FlowRunner storage, and nothing lingers in a third-party bucket in between. There is no storage account to provision on the Aspose side and no cleanup job to forget. That statelessness is the point for teams with document-handling obligations, and it makes conversion a step you drop into a flow rather than a system you operate. - Convert Word documents, PDFs, spreadsheets, and presentations between formats: DOCX to PDF, PDF to editable XLSX, PPTX to PNG previews - Merge several Word documents into one file, the assembly step behind contract packets and generated reports - Normalize inbound attachments to a single archival format at intake - Turn PDFs into structured data formats so downstream steps can actually read them The format coverage is broad on purpose: DOC, DOCX, RTF, and ODT on the Word side; DOCX, XLSX, HTML, EPUB, and image formats out of PDF; JSON out of spreadsheets so downstream agent steps can read the data without a parsing layer; SVG and image renders out of presentations for previews and portals. One connector covers the intake formats a business actually receives. The conversions are reversible in the sense that the source file still exists. What is not reversible is what the output does next, which is why FlowRunner puts the [human-in-the-loop](/concepts/human-in-the-loop) checkpoint between assembly and delivery.

Without FlowRunner

Contract assembly by copy-paste Someone opens four Word files, pastes them together, fixes the numbering, and hopes

Format mismatch at every handoff Finance wants XLSX, legal wants PDF, the client sent ODT, and a person translates between them

Attachments in whatever arrived The archive holds a mix of docx, ppt, and pdf, and half of it will not open cleanly in five years

With FlowRunner

Packets assembled in order, every time Agents merge the base document and its schedules in a defined sequence, then render one PDF

Conversion inline in the flow PDF to XLSX, DOCX to PDF, PPTX to images, done in the step where the file is needed

One archival format at intake Everything entering the record normalizes to PDF the moment it arrives

Use Case Scenarios

The order packet that assembles itself

A [Shopify](/integrations/shopify) order for a configured product fires the flow. The agent selects the correct terms document and product schedule, calls Merge Word Documents to append them to the base agreement, then Convert Word Document to produce the PDF. The packet routes to [Dropbox Sign](/integrations/dropbox-sign) for signature only after the account owner has confirmed the assembly, and the signed copy archives to [Google Drive](/integrations/google-drive). What used to be an hour of careful copy-paste per deal becomes a review click, and the schedules never fall out of order because the merge sequence is defined once, in the flow.

Supplier PDFs become rows

A supplier emails price lists as PDF. The agent runs Convert PDF Document targeting XLSX, then pushes the extracted table into [Google Sheets](/integrations/google-sheets) with Add Rows. Purchasing compares this week's prices against last week's without anyone retyping a table, and the original PDF stays attached to the record for audit. When a conversion comes back structurally odd, merged cells where columns should be, the row count off from the usual, the agent flags that supplier's file for a manual look instead of loading suspect data.

Board materials, one format, on time

Contributors submit sections as DOCX, XLSX, and PPTX. The agent converts each to PDF with the matching action, Convert Word Document, Convert Spreadsheet, Convert Presentation, then merges the Word-based sections with Merge Word Documents before the final render. The assembled deck posts to [Slack](/integrations/slack) for the chief of staff to review, and the approved version distributes to the board portal, and nobody spent the night before the meeting fighting export menus.

Human-in-Loop Highlight

Merge Word Documents is where this connector stops being a utility and starts carrying legal weight: it assembles the exact document a client will sign. Append the schedules in the wrong order, pull last quarter's pricing exhibit, or miss an amendment, and the error does not surface until the signed copy comes back, at which point it is a contract problem, not a file problem. So FlowRunner agents treat the merged output as a draft by default. The agent assembles the packet, renders the PDF with Convert Word Document, and posts it to the account owner with the list of source documents it merged and their order. A person confirms the assembly is right, then the packet moves to signature. Machine speed on the assembly, human eyes before anything binding leaves the building.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Document Conversion

Convert Word Document Converts a Word document (DOC, DOCX, RTF, ODT) to PDF, HTML, TXT, or an image. Source comes from a FlowRunner file URL, the result saves back to FlowRunner storage with a downloadable URL, and no Aspose cloud storage is used in between.
Convert PDF Document Converts a PDF to DOCX, XLSX, HTML, EPUB, or an image format. The step that turns a locked document back into something editable or machine-readable.
Convert Spreadsheet Converts spreadsheets (XLSX, XLS, CSV, ODS) to PDF, CSV, HTML, or JSON via Aspose Cells. JSON output makes spreadsheet contents consumable by any downstream agent step.
Convert Presentation Converts a PowerPoint presentation (PPTX, PPT, ODP) to PDF, HTML, or images including SVG via Aspose Slides. Used for previews, archives, and distribution formats.

Document Assembly

Merge Word Documents Appends one or more Word documents to a base document, producing a single merged file through the stateless append-online endpoint. The contract-packet assembler, and the operation this page's human gate reviews before anything goes out for signature.

Frequently Asked Questions

What can FlowRunner do with Aspose Cloud?

FlowRunner agents can run Convert Word Document, Convert PDF Document, and Convert Spreadsheet in Aspose Cloud, plus 2 more actions.

Does connecting Aspose Cloud to FlowRunner require OAuth?

Yes. Aspose Cloud connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Aspose Cloud trigger a FlowRunner workflow automatically?

Aspose Cloud doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Aspose Cloud

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us