Workflow Editor | Cine Power Planner

Tools

Organize

Merge PDF
Split PDF
Extract Pages
Delete Pages
Organize PDF
Rotate PDF
Reverse Pages

Edit

Edit PDF
Add Watermark
Page Numbers
Header Footer
Sign PDF
Crop PDF
Bookmark
Form Filler

Convert

JPG To PDF
Image To PDF
PDF To JPG
PDF To PNG
Word To PDF
PDF To DOCX
OCR PDF

Optimize

Compress PDF
Linearize PDF
Repair PDF
Fix Page Size

Secure

Encrypt PDF
Decrypt PDF
Flatten PDF
Sanitize PDF
Remove Metadata
Change Permissions
React Flow mini map

No Steps Yet

Drag tools from the sidebar onto the canvas, or start from a template to build your PDF pipeline.

About Workflow Editor

The Workflow Editor lets you assemble several PDF operations into a named pipeline by dragging steps into order. Saved workflows can be reloaded and run against new documents, so a routine that takes six manual steps becomes one.

Every step in a pipeline runs locally, exactly as it does when used on its own. Saved workflows store settings only, never documents.

How to use Workflow Editor

  1. Create a workflow, or start from one of the supplied templates.
  2. Drag operations into the pipeline and set each one's options.
  3. Order the steps deliberately — the output of each becomes the input of the next.
  4. Save the workflow under a clear name, then run it against a document.

On a production

Every Friday the same job: combine the week's timesheets, stamp page numbers, add a footer and compress the result. Done by hand it is six operations and a chance to forget one. Saved as a pipeline it is a single run, identical every week, by whoever happens to be free.

Frequently asked questions

Does step order change the result?
Very much so. Compressing before adding page numbers gives a different output than the reverse, because each step operates on whatever the previous one produced.
Where are saved workflows kept?
In this browser on this device. They are not synced between machines, so a pipeline built on a laptop will not appear on a different computer.
Can a workflow run over several documents?
A saved pipeline is applied per document, so run it against each file in turn. Building the pipeline once is where the time is saved, not in batching the run itself.