# The process flow canvas

## Introduction

The **process flow canvas** is where you build and test your process flows in a smart, visual way. This is where you define if, when, what, and how data is synced.&#x20;

## Finding your way around the process flow canvas

The **process flow canvas** has four main elements - a [title](#the-process-flow-title), an [actions bar](#the-actions-bar), a [shapes area](#the-shapes-area), and a (hidden unless activated) [options panel](#the-options-panel):

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

### <img src="/files/T8T3YY133oe49Hhlw85X" alt="" data-size="line"> The process flow title bar

The process flow title bar shows the name of the process flow, as specified when it was created. The number above the title is the process flow id and the number below is the version number. To change this title, use the [settings option from the actions bar](#settings).

### <img src="/files/m3FS385CObnsLYSy1Mat" alt="" data-size="line"> The actions bar

Options in the actions bar are summarised below:

<table><thead><tr><th width="140.33333333333331">Option</th><th>Summart</th></tr></thead><tbody><tr><td><h4><img src="/files/qPYJmp5cP4LKjVPTB4wr" alt="" data-size="line"></h4></td><td><p><strong>Process flow settings</strong></p><p>Use this option to access <strong>settings</strong> for this process flow - these are used to manage settings for this process flow as a whole. For more information please see <a href="/pages/z6PdL9vs3J07w3LXGTw8">Process flow settings</a>. </p></td></tr><tr><td><h4><img src="/files/myPLz7D4VcWM4oQDvsdx" alt="" data-size="line"></h4></td><td><p><strong>Return to trigger</strong></p><p>If you're working on a longer process flow, use this option to quickly jump back to the start (i.e. back to the trigger shape).  </p></td></tr><tr><td><h4><img src="/files/YXUzsXhoAedmdESKS46J" alt="" data-size="line"></h4></td><td><h4>Initialise flow now</h4><p>Use this option to run the process flow immediately. For more information please see <a href="/pages/jhZRZQL15izh7dcNb7i9">Running a process flow manually</a>. </p></td></tr><tr><td><h4><img src="/files/NyD4JfFZFWjbIcsuVcEo" alt="" data-size="line"></h4></td><td><h4>Initialise flow with payload</h4><p>Use this option to provide a payload to be passed in before the process flow initialises. This is particularly useful if you want to test how a flow will run with expected data from a <a href="/pages/EVn1AesQJtjyoIw7p0HZ">Patchworks API request</a>.</p></td></tr><tr><td><img src="/files/PaG5WccvivtcHeJZAfQL" alt="" data-size="line"></td><td><h4>Stop the current run</h4><p>If a process flow is running, you can use this option to stop the current run. Stopping a run in this way triggers the flow to stop at its next step however, if an API call or script has already been triggered, the process flow will stop after these have completed. <br><br>With this in mind, it's important to check any target connections to clarify what (if any) updates have been made after a process flow has been stopped.</p></td></tr><tr><td><h4><img src="/files/jIrNlumE1N6VmCApW3OY" alt="" data-size="line"></h4></td><td><h4>Logs &#x26; payloads</h4><p>As a process flow runs, you can <a href="/pages/TNXwUbW0xLxu1LBHW23w#real-time-monitoring">view progress in real time</a>; you can also <a href="/pages/TNXwUbW0xLxu1LBHW23w#logs-and-payloads">check logs and view payloads</a> at any stage.</p></td></tr></tbody></table>

### <img src="/files/HNzpgvzsQMDd9UpknatD" alt="" data-size="line"> The shapes area&#x20;

The main 'shapes area' is where you build your process flow. Start by clicking the + sign associated with the [trigger shape](/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md), then choose the required shape for your next step, and [start building](/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows.md)!

<div align="left"><figure><img src="/files/DSU6FfhQ48ZK0WQza9Eb" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
We're adding new shapes all the time! For information about working with shapes, please see our [Process flow shapes](/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes.md) section.
{% endhint %}

### <img src="/files/udBsfHJrPngCHP3bg9mP" alt="" data-size="line"> The settings drawer

When you access [process flow settings](#settings) or to configure a shape in your flow, available settings are displayed in a panel on the right-hand side. For example, when we choose to access settings for a [trigger ](/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/process-flow-shapes/standard-shapes/trigger-shape.md)shape, available trigger options are displayed:

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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/~/changes/J8IbZkP6ASUZu2oBhGi2/process-flows/building-process-flows/the-process-flow-canvas.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
