# 2025 05 14 release notes (core)

## Release summary <a href="#release-summary" id="release-summary"></a>

This page summarises items scheduled for the following release to the Patchworks Core Production environment.&#x20;

| Release version | Release date        |
| --------------- | ------------------- |
| v2025-05-14     | 14th May 2025 (a.m) |

New features, updates, and enhancements of note are summarised by product area, below:

* ​[Process flows](#process-flows)
* [Connector builder](#connector-builder)

## Process flows <a href="#process-flows" id="process-flows"></a>

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="edbc33cea7f34e16b3a205c7a65c3172">New</span></td><td><p><strong>AI for custom scripts</strong><br>You can now ask AI to help create a custom script! Simply tell AI what you're trying to achieve and let it take care of the rest. </p><p></p><p>Our AI integration knows about expected keys and value types (payload, variables, meta, etc.), so generated scripts should be in a form that's ready to use in process flows. <br><br>Every company profile can make up to 5 requests per day, free of charge - if you'd like to increase your allowance, a <a href="../../getting-started/core-subscription-tiers">subscription tier bolt-on</a> can be purchased. Your allowance usage and conversation history can be accessed from a new <a href="../../developer-hub/custom-scripting/creating-and-testing-custom-scripts/creating-a-script-with-ai/ai-conversation-history">AI conversation history</a> page.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FCEX1kQxTmFyyKdXYNllW%2Ficon%20page%20grey.png?alt=media&#x26;token=25a0882d-c182-4bd8-ab67-4ec1a367e88f" alt="" data-size="line"> <a href="../../developer-hub/custom-scripting/creating-and-testing-custom-scripts/creating-a-script-with-ai">Creating a script with AI</a></p></td><td>CPT-1768</td></tr><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><strong>Track data shape</strong><br>A new <code>use custom value</code> option is available. When variable syntax is defined here, the raw variable value is tracked (rather than retrieved from incoming payloads as when a <code>field path</code> is used). <br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FCEX1kQxTmFyyKdXYNllW%2Ficon%20page%20grey.png?alt=media&#x26;token=25a0882d-c182-4bd8-ab67-4ec1a367e88f" alt="" data-size="line"> <a href="../../../process-flows/building-process-flows/process-flow-shapes/standard-shapes/track-data-shape#custom-values">Track data shape</a></td><td>CPT-3947</td></tr><tr><td><span data-option="9a29ee576f43448f9b1623baca59c3db">Bug</span></td><td><strong>De-dupe shape</strong><br>Fixed an issue where only the first 50 data pools were displayed for selection in the de-dupe shape.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FCEX1kQxTmFyyKdXYNllW%2Ficon%20page%20grey.png?alt=media&#x26;token=25a0882d-c182-4bd8-ab67-4ec1a367e88f" alt="" data-size="line"> <a href="../../process-flows/building-process-flows/process-flow-shapes/advanced-shapes/de-dupe-shape">De-dupe shape</a>   </td><td>CPT-4201</td></tr></tbody></table>

## Connector builder

<table><thead><tr><th width="180">Type<select><option value="edbc33cea7f34e16b3a205c7a65c3172" label="New" color="blue"></option><option value="d8457d8925c74fab90fa132d141b764b" label="Change" color="blue"></option><option value="030babd6286a4fe19214da74af9afb98" label="Enhancement" color="blue"></option><option value="9a29ee576f43448f9b1623baca59c3db" label="Bug" color="blue"></option><option value="L09Gy6z2y7VD" label="Breaking change" color="blue"></option></select></th><th width="426">Summary</th><th>Ref #</th></tr></thead><tbody><tr><td><span data-option="030babd6286a4fe19214da74af9afb98">Enhancement</span></td><td><p><strong>Disable automatic headers for endpoints</strong><br>Sometimes, depending on the endpoint configuration, Patchworks adds request headers automatically. This can be for different reasons - perhaps there's a specific requirement for an authentication method, or a <code>content-type</code> for a request body setting.  </p><p></p><p>When configuring a connector endpoint, the <code>header</code> tab now includes a <code>disable automatic headers</code> option. When this option is toggled <code>on</code>, automatic headers are NOT sent when requests are made. This applies to ALL automatic headers.<br><br><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FCEX1kQxTmFyyKdXYNllW%2Ficon%20page%20grey.png?alt=media&#x26;token=25a0882d-c182-4bd8-ab67-4ec1a367e88f" alt="" data-size="line"> <a href="../../developer-hub/connector-builder/building-your-own-connector/4-endpoints/endpoint-options/header">Endpoint header options</a></p></td><td>CPT-TBC</td></tr></tbody></table>
