> 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/prebuilt-process-flows/the-anatomy-of-a-prebuilt-process-flow.md).

# The anatomy of a prebuilt process flow

## Introduction

A prebuilt process can include any number/combination of the following components:

| Resource                                                                                                                                          | Notes                                                                                                                                                                                                                                                                                                                                                    |
| ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Connectors](/product-documentation/connectors-and-instances/connectors-and-instances-introduction.md)                                            | <p>All connectors used in process flows are installed, without instances. <br><br>If the process flow which includes a connector that you have already installed from the <a href="/pages/gO9cKXIn2PKE6IPQWXi3">connector marketplace</a>, a fresh copy of that connector is added alongside the existing one. You can then decide which one to use.</p> |
| [Custom scripts](/product-documentation/developer-hub/custom-scripting.md)                                                                        | All scripts defined in process flow [script shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/script-shape.md) are installed and deployed, ready for use.                                                                                                                                          |
| [Cross-reference lookups](/product-documentation/process-flows/cross-reference-lookups.md)                                                        | All cross-reference lookups defined as process flow [map shape field transformations](/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/map-shape.md) are installed and ready for use.                                                                                                                     |
| [De-dupe data pools](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape.md#data-pools) | Any data pools defined in process flow [de-dupe shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape.md) are added. These are 'clean' data pools (i.e. with no associated data), ready for use.                                                                                         |
| [Caches and cache keys](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache.md)                 | Any caches and cache keys defined in process flow [add to cache shapes](/product-documentation/process-flows/building-process-flows/process-flow-shapes/advanced-shapes/cache/add-to-cache-shape.md) are added. These are 'clean' caches (i.e. with no associated data), ready for use.                                                                  |

## Viewing the contents of a prebuilt process flow

As you browse the [process flows marketplace](/product-documentation/marketplace/marketplace-process-flows.md), you'll see that each process flow is displayed with a visual summary of what's included - for example:

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

{% hint style="info" %}
For more information about this summary please see [The Patchworks marketplace](/product-documentation/marketplace/marketplace-process-flows.md).
{% endhint %}

To see a read-only view of a process flow before it's installed, [find the required process flow in the marketplace](/product-documentation/marketplace/marketplace-process-flows.md) and click the associated **view** button:&#x20;

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

&#x20;The process flow is displayed in read-only mode, with a breakdown of its components:

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://doc.wearepatchworks.com/product-documentation/process-flows/prebuilt-process-flows/the-anatomy-of-a-prebuilt-process-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.