> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-integrations/third-party-integrations/patchworks/use-case-how-to/custom-fields.md).

# Custom Fields

You have the ability to add custom fields to your ZAP-POST campaigns, these fields allow you to choose data specific for your campaigns and customer data to be displayed on your Direct Mail campaigns. For more help on setting up custom fields, see our [detailed documentation](https://userguide.zappost.com/zap-post-user-guide/zapp/using-the-zapp/campaigns#custom-field-setup).

To add custom fields to your Patchworks Integration:

1. In Patchworks, navigate to **Connectors & Instances**
2. Click **settings**

<figure><img src="/files/HSNVo4nB2wXlAWhDBT7h" alt=""><figcaption></figcaption></figure>

3. Select **Endpoints** (you'll want to edit the POST Submissions and POST Records endpoints)
4. Click on **Schema** and then **Edit**

<figure><img src="/files/mpchf5F35aBn2XrwjntC" alt=""><figcaption></figcaption></figure>

5. Paste the below into the Schema&#x20;

```json
{
      "customerid": "Value",
      "email": "Value",
      "salutation": "Value",
      "firstname": "Value",
      "surname": "Value",
      "address1": "Value",
      "address2": "Value",
      "address3": "Value",
      "city": "Value",
      "postcode": "Value",
      "country": "Value",
      "currency": "Value",
      "language": "Value",
      "customdata:" {
        "customfield1": "Value"
      }
}
```

{% hint style="warning" %}
Change the **customfield1** name to match the custom field **label** you created in the ZAP-POST app.&#x20;
{% endhint %}

<figure><img src="/files/qsORt7LbWXlJKwq3mv2n" alt=""><figcaption></figcaption></figure>

6. Click **Save Schema** then **Save and go back**
7. On your flow, you'll need to **map** which data should populate your new **custom field**
8. On your mapping step, click on the **settings** icon

<figure><img src="/files/YFR3LyMPh9u38peMPQvK" alt=""><figcaption></figcaption></figure>

9. Click **Add Mapping Rule**
10. For the left field, select the field where the data is coming from
11. For the right field, the Payload should be **customdata.customfield1**

<figure><img src="/files/5eYaqEJxEjBRrCxyKraB" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Change the customfield1 name to match the custom field **label** you created in the ZAP-POST app, for example, customdata.dateofbirth
{% endhint %}

12. Click **Accept** then **Save**
13. You're all set!


---

# 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:

```
GET https://userguide.zappost.com/zap-integrations/third-party-integrations/patchworks/use-case-how-to/custom-fields.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.