# Use Case how-to
In order to submit customer data from Patchworks to ZAP-POST, you need to ensure you have a campaign created and a design published. See our [ZAP-POST User Guide](/zap-post-web-app/zap-post-user-guide/zapp/using-the-zapp.md) for a detailed walk through.
For this use case example, we'll be using a Klaviyo shape to find where our recipient data is coming from.
1. From the Patchworks home page, click on **Process Flows**
2. Click on **Create New Flow**
3. Name your flow, give it a description and select the Production Flow slider
4. Build your flow, selecting any connectors and relevant shapes
5. Once you've added the shape that data is being ingested from, you'll need to add a **Map shape**
6. You need to amend the Map shape settings to map the fields from one connector to another, in this instance, Klaviyo to ZAP-POST. Click on the Map shape settings icon
7. Select your **Source Endpoint** and your **Target Endpoint**
6. Click **Generate Automatic Mapping**, you can amend the mapping results or set them up manually
7. Click **Save**
8. Add a ZAP-POST Connector shape
9. When adding either a POST Submission or a POST Records shape, you'll notice 3 variables
Campaign ID - this is a required field and can be found in the ZAP-POST app.\
Sceduled Send Date ID - this is optional and can be left blank\
Only Valid Records - this is optional and defaults to true
For more information on these variables, see our [API Documentation](https://apidocumentation.zappost.com/)
10. Once saved, you can **initialise your flow**
11. To **confirm** your submission, log into the ZAP\~POST app
12. Click **Processing** in the top Nav
13. You should see your submission in the table
---
# 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://userguide.zappost.com/zap-integrations/third-party-integrations/patchworks/use-case-how-to.md?ask=
```
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.