Building custom scripts to process PDFs, extract data, and sync with external systems is time-consuming. The ConvertUniverse Visual Workflow Editor allows you to replace complex backend logic with an intuitive node-based builder.

In this guide, we'll cover the fundamental concepts of navigating the editor and building your first pipeline.

The Building Blocks: Nodes & Edges

Every workflow consists of two main components:

Nodes: These are individual blocks that perform a specific task (like fetching a file, converting a document, or sending a webhook).
Edges: The lines connecting nodes together. An edge represents the path that data will travel from one node's output to another node's input.

Anatomy of a Node

When you drag a node onto the canvas, click on it to open the Properties Panel on the right side of the screen. This panel is where you configure the specific behavior of the node.

Nodes typically have:

Inputs (Sockets on the left): Data coming into the node.
Outputs (Sockets on the right): Data produced by the node that can be passed downstream.
Configuration Fields: Static settings you define (e.g., selecting "PDF to Word" from a dropdown).

Creating Your First Workflow

Let's build a simple pipeline that takes an uploaded PDF and converts it into a Word document.

Start with a Trigger Node: Every workflow requires at least one starting point. Drag the File Upload (Trigger) node onto the canvas. This node will automatically execute the workflow whenever a file is uploaded to it.
Add an Action Node: Next, drag the Convert Document node onto the canvas.
Connect the Dots: Click and drag from the output dot on the right side of the Trigger node to the input dot on the left side of the Convert node. You have just told the engine to pass the uploaded file directly into the conversion engine.
Configure the Action: Click on the Convert Document node. In the right sidebar, set the target format to DOCX.

Running and Testing

Before deploying your workflow, use the Run button at the top of the editor to test it. When you click Run, you will be prompted to upload a test file for the Trigger node.

The execution engine will process the node live, and you can view the output in the Execution History panel to verify that the file was successfully converted!

[!TIP] Stuck on a blank canvas? Check out the Templates Gallery via the left sidebar to clone pre-built, production-ready workflows with one click.