> ## Documentation Index
> Fetch the complete documentation index at: https://docs.overlap.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Use nodes to decide how a workflow starts, what happens to the content, and where the finished result goes

## What nodes are

A **node** is one step in your workflow.

You add nodes to the workflow canvas, connect them in order, and Overlap runs that path from input to output. A simple workflow might start with a source like YouTube or RSS, pass through clip-selection and editing nodes, and finish with an export like social posting or email.

<Info>
  You may still see older `clipping agent` language in some parts of the product. In the current docs, we use `workflow` for the automation and `node` for each step inside it.
</Info>

## Where to add nodes

Open **Workflows** from the left sidebar and click **New** to open the builder.

The current builder is organized into three stages:

1. **Trigger**
2. **Editing**
3. **Export**

Each stage has a searchable node panel on the left. Start with the empty builder, then click **Manual Trigger** to place the first node on the canvas and move into **Editing** to keep building. You can also use **Double Click** anywhere on the canvas to add a new node, or choose **Explore Templates** if you want to start from a prebuilt flow.

<Frame>
  <img src="https://mintcdn.com/overlap-1436d2b7/0Zo5m2TduKsLCQhp/images/generated/beta-workflows-create-framed.png?fit=max&auto=format&n=0Zo5m2TduKsLCQhp&q=85&s=ca1bfa80ebcb53cc1317f2129ddfcd56" alt="Empty workflow builder" width="2192" height="1323" data-path="images/generated/beta-workflows-create-framed.png" />
</Frame>

<Frame>
  <img src="https://mintcdn.com/overlap-1436d2b7/0Zo5m2TduKsLCQhp/images/generated/beta-workflows-create-with-node-framed.png?fit=max&auto=format&n=0Zo5m2TduKsLCQhp&q=85&s=3dc1104c4a4f6d8686ba4fb0e35df100" alt="Workflow builder with a trigger node added" width="2192" height="1323" data-path="images/generated/beta-workflows-create-with-node-framed.png" />
</Frame>

## Trigger nodes

Trigger nodes decide what starts the workflow.

In the current builder, the **Trigger** stage includes options such as:

* **Manual Trigger**
* **Audio Livestream**
* **New Dropbox Video**
* **New YouTube Video**
* **RSS Feed**

Choose the trigger that matches how new content should enter the workflow. Use **Manual Trigger** when you want to launch runs yourself. Use one of the source-based triggers when you want Overlap to listen for new content automatically.

## Editing nodes

Editing nodes shape the clip after the workflow has a source.

This is where you tell Overlap what moments to find, how the video should look, and what should be added before export. Common editing nodes documented in this section include:

* [Find Clips](/nodes/findclips)
* [Add Subtitles](/nodes/subtitles)
* [Remove Fluff](/nodes/remove-fluff)
* [Remove Filler Words](/nodes/filler-words)
* [Remove Curse Words](/nodes/remove-curse-words)
* [Smart Zoom](/nodes/smart-zoom)
* [Reframe](/nodes/reframe)
* [Split](/nodes/split)
* [Watermarks, Outros, etc.](/nodes/branding)
* [Add Title Overlay](/nodes/title-overlay)
* [Audiogram](/nodes/audiogram)
* [Add Music](/nodes/add-music)
* [Delay](/nodes/delay)

Think of the **Editing** stage as the part of the workflow where you build your processing chain. You can keep it minimal, or combine multiple editing nodes when you want more control over the final result.

## Export nodes

Export nodes decide what Overlap does with the finished output.

In the current builder, the **Export** stage includes options such as:

* **Email**
* **Post to Social**

Use export nodes at the end of the flow so the workflow has a clear outcome after processing is complete.

<Frame>
  <img src="https://mintcdn.com/overlap-1436d2b7/0Zo5m2TduKsLCQhp/images/generated/beta-nodes-export-framed.png?fit=max&auto=format&n=0Zo5m2TduKsLCQhp&q=85&s=86318e43a29c900b00fc20d060d81728" alt="Export nodes in the workflow builder" width="2192" height="1323" data-path="images/generated/beta-nodes-export-framed.png" />
</Frame>

## A common node flow

One practical way to think about nodes is:

* A trigger brings content into the workflow
* Editing nodes decide what clips get created and how they look
* An export node sends the finished result somewhere useful

For example, a workflow might look like:

* **New YouTube Video** -> **Find Clips** -> **Add Title Overlay** -> **Add Subtitles** -> **Post to Social**
* **New YouTube Video** -> **Find Clips** -> **Remove Fluff** -> **Add Subtitles** -> **Post to Social**
* **Manual Trigger** -> **Find Clips** -> **Split** -> different editing or export branches
* **Manual Trigger** -> **Remove Filler Words** -> **Remove Curse Words** -> **Smart Zoom** -> **Add Subtitles** -> **Email**
* **RSS Feed** -> **Find Clips** -> **Watermarks, Outros, etc.** -> **Email**

## Keep exploring

<CardGroup cols={3}>
  <Card title="Trigger Nodes" icon="rocket-launch" color="#ff2700" href="/nodes/youtube">
    Start a workflow from YouTube, RSS, Dropbox, audio livestreams, or a manual run.
  </Card>

  <Card title="Find Clips" icon="face-viewfinder" color="#ff2700" href="/nodes/findclips">
    Guide Overlap toward the moments you want it to surface from each source.
  </Card>

  <Card title="Action Nodes" icon="person-running-fast" color="#ff2700" href="/nodes/subtitles">
    Add subtitles, branding, reframing, and other finishing steps before export.
  </Card>
</CardGroup>