> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/process-flows/about-process-flows.md).

# About process flows

## Introduction

**Process flows** are our next-generation tool for building powerful data flows between connector [instances](/product-documentation/connectors-and-instances/working-with-instances.md) in an intuitive, visual way. This is where you define if, when, what, and how data is synced.

<details>

<summary><img src="/files/V40ECzWtJLwZuafWihzT" alt="" data-size="line"> <strong>Hang on - we use Patchworks services - isn't that the same thing?</strong></summary>

If you registered for a Patchworks account before July 2023, you'll be familiar with using [services](/product-documentation/patchworks-services/working-with-services/accessing-services.md) to sync data between systems.

Process flows include all the functionality of services and much more. You can continue to use services but if you'd like to try [process flows](#process-flows), please contact your Customer Success Manager, or reach out to <customersuccess@wearepatchworks.com>

</details>

A **process flow** is built by adding automated [shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes.md) onto a [canvas](/product-documentation/process-flows/building-process-flows/the-process-flow-canvas.md). Every [shape](/product-documentation/process-flows/building-process-flows/process-flow-shapes.md) is automated to perform a specific task, based on information that you provide - you simply drop a shape onto the [canvas](/product-documentation/process-flows/building-process-flows/the-process-flow-canvas.md) and then define your required settings and relationships.

Process flows can be defined to run on automated schedules however, for testing and troubleshooting purposes, you can also run a flow manually for instant feedback on each step, and real-time logs - for example:

<div align="left"><figure><img src="/files/eaO0jIMWRv2e0SHMIdiQ" alt=""><figcaption></figcaption></figure></div>

<details>

<summary><img src="/files/JOYoP4EdSu7WJ3CMdAAS" alt="" data-size="line"> Show me</summary>

![](/files/bYsIZo4PJG9S1EWCuERG)

</details>

## In this section

* [Connectors & instances](/product-documentation/connectors-and-instances/connectors-and-instances-introduction.md). How to install connectors and add instances, ready for use when you build process flows.
* [Building process flows](/product-documentation/process-flows/building-process-flows.md). How to add a new process flow, then work with the canvas and shapes to build your required data flows.
* [Managing process flows](/product-documentation/process-flows/managing-process-flows.md). How to manage existing process flows.
* [Error reporting & exception handling](/product-documentation/process-flows/error-reporting-and-exception-handling.md). Process flows include a transparent logging feature, so you can monitor/troubleshoot progress both in real-time and retrospectively, via run logs.