08/07/26 Release Notes (core)
Release date: 8th July 2026
New Features
Implementation Agent: Connector Building
We’ve completed the next phase of the Implementation Agent, which can now build connectors directly within Patchworks.
This allows users to move from API requirements to a working connector much faster, reducing manual setup and helping accelerate new integrations. The agent can interpret connector requirements, create the structure, and support the build process end to end.
AI Token Purchases
Users can now purchase additional AI tokens.
Teams can top up their AI usage when needed without contacting support or waiting for manual processing. This makes it easier to keep using AI-powered features as demand grows across Flow Builder, Implementation Agent, and other AI tools
Endpoint Collection Importer
The Endpoint Collection Importer has been significantly upgraded to cut down the manual setup involved in bringing collections into Patchworks:
Authentication is now handled upfront during import, and you can resume the import process after setting your auth details
Endpoints can be imported into an existing connector - either overwriting all endpoints, or adding only new ones by unique name
Query parameters from the URL are automatically brought in as optional URL parameters
Entity types are inferred from the endpoint URL (for example, an
/orderendpoint defaults to the Order entity)OpenAPI files are now supported alongside Postman collections, removing the need to convert before uploading
Large collections over 4.5 MB can now be uploaded and processed reliably, with configurable thresholds for pushing imports to a background job
Improvements
AI Studio - Role-Based Access
Access to AI Studio is now controlled by a dedicated permission (use ai-studio) in the Role Builder, replacing the previous feature flag. Administrators can grant or restrict AI Studio access on a per-role basis.
Flow Builder - Blueprint Tool
The Flow Builder agent can now search the marketplace for Blueprints that match your requirements and install them directly, helping you start from a proven template rather than building from scratch.
Flow Builder - Script Building Support
The Flow Builder agent can now build and use custom scripts as part of flow construction, covering both custom script steps and custom script transforms.
Flow Builder - Data Pool Creation
The Flow Builder agent can now create data pools, enabling deduplication and data management as part of automated flow building.
Flow Builder - Clearer Handling of Empty Agent Responses
When the AI agent returns an empty response - for example, due to a downstream API outage - the platform now displays a clear error or warning message rather than appearing to break.
Date Transform - Formatting Guidance
The date format transform (and other transforms with custom format inputs) now includes a tooltip explaining the date formatting syntax, giving you clear guidance without needing to leave the page.
Audit Logs - Allowance Updates Recorded
Changes to company connector allowances are now captured in the Platform audit logs, ensuring a complete history of allowance modifications.
Flows Table - Responsive Layout
The Flows table now renders correctly at smaller browser widths (around 950px and below).
Flow Folders - Collapsed State Preserved After Drag
Dragging a flow into a folder no longer causes all other folders to expand. Folder states are now preserved after a drag-and-drop operation.
Flows - Accurate “Latest Run” Times
The “Latest Run” column on the Flows table now displays correct and accurate run times.
Bug Fixes
Fix: Routes Always Following the First Route
Resolved an issue where all routes in the Flow Builder followed the logic of the first route rather than their own individual conditions.
Fix: Route Not Progressing with “Follow First Matching Route”
Fixed a bug where flows with multiple conditions would not progress through a route even when the filter criteria were met and “Follow first matching route” was selected. The flow now correctly evaluates and follows the first matching route.
Fix: Empty Payloads Removing Meta Fields
Fixed a bug where using a connector with the “Expect an empty response” option removed meta fields from the payload. Meta fields are now preserved whether or not a payload is returned, so downstream steps can still access stored IDs and values.
For questions about this release, please contact the Patchworks support team or refer to the product documentation.
Last updated
Was this helpful?