Improved “Search by name” in Ziflow’s Dashboard

We have enhanced the "Search by name" functionality within the Dashboard to be more flexible and return more relevant results. Previously, the search only returned results where the proof name contained the exact string of terms you entered. Search for “campaign 2024”, and the results would be restricted to only include proofs with “campaign 2024” in the name, in that order.

With this release, the search now applies an "AND" logic between your search terms. For example, searching for "campaign 2024" will now return all proofs that include both "campaign" and "2024" in their name. It will also find partial word results.

This change mirrors the behavior of our Global Search (accessible by clicking “Search” in the left-hand nav bar), and should make it significantly easier and faster for you to locate specific proofs directly from your Dashboard.

Ziflow Connect: “Application fields on a proof” now defaults to “Show”

We’ve streamlined the setup process for new Ziflow Connect integrations by removing an extra manual step. 

Previously, when connecting a new external application via Ziflow Connect, the "Application fields on a proof" setting was toggled to “Don’t show” by default. This meant you had to manually go into the application settings and change this to “Show” if you wanted to use these fields during proof creation.

With this release, the "Application fields on a proof" setting will now automatically default to Show for any net-new application connection made. By eliminating this unnecessary step, we are reducing friction and helping your team accelerate the adoption and use of new integrations.

Note: This default change only applies to net-new application connections. Reconnecting an existing application or making a secondary connection will not force a change to this setting.

Wrike integration: Copy/Paste subtask IDs and URLs into application fields

We've improved our integration with Wrike to fully support customers who align Ziflow proofs with Wrike subtasks. Previously, when creating a proof, the ability to copy/paste a Wrike task ID or URL to link the two only functioned correctly for top-level tasks (level 1). The same was true for searching for the task name via the drop-down menu: only top-level tasks would be returned.

With this release, we've extended this capability. You can now seamlessly link a proof to any Wrike subtask either by pasting its ID or URL or searching by name, ensuring this functionality works consistently across all levels of your Wrike hierarchy (level 1+x).

To connect Wrike, see Integrate with Wrike.

Ziflow API: Update a single stage on a proof without unexpected deletions

We've introduced an update to our API to give users more precise control when making changes to individual stages on a proof. Previously, when using a PUT command to update a stage on a proof, you were required to include the Stage IDs for all existing stages on the proof in the API call. If you omitted a Stage ID, the system would incorrectly delete that stage from the proof's workflow.

With this release, we are adding a dedicated endpoint to make it easier to update a single stage. The absence of other Stage IDs in your API call will no longer force the deletion of those stages, ensuring your updates only affect the intended stage.

This enhancement provides a more robust and reliable way for advanced users to manage individual stage attributes, such as deadlines or owners, on proofs with complex, multi-stage workflows. 

For more information, see Update an existing proof.

Single Sign On: User Role information now available in SCIM “GET” requests

We've enhanced our SCIM API endpoint to return a user's assigned role, building upon the existing capability to pass roles during user creation (introduced in November of 2025). 

This update extends the GET users endpoints with a customAttributes object. The API will now return the user's assigned role. Possible values include: ZIFLOW_USER, ZIFLOW_MANAGER, ZIFLOW_LITE_USER, ZIFLOW_ADMIN, and ZIFLOW_BILLING_ADMIN.

While creating users with specific roles via SCIM is an important first step, being able to retrieve that role information is foundational for full user lifecycle management. This work advances our goal of enabling your team to not just create, but also manage and update user roles directly via the SCIM protocol.

For more information, see the SCIM section of the Ziflow API.

PDF comments: Improved visibility for unsupported Adobe markups

We've enhanced our ability to import embedded feedback from Adobe PDF documents (currently in public preview), particularly for “callout style” comments. 

Previously, Ziflow would render these unsupported markups as a solid rectangle, using the markup's background color, with the comment text placed in the comment section. The resulting annotation would not be difficult to read in the Proof Viewer, with the solid rectangle obscuring the content beneath it.

With this release, we will still display the rectangle, but it will be hollowed out and display the markup border color from the original Adobe PDF, ensuring the annotation is visible without obscuring the underlying asset. This change ensures that imported feedback, regardless of the original PDF markup type, is easy to recognize and review in the Proof Viewer.

ReviewAI (in public preview): Proof Brief text and Custom Property data now used alongside Checklist AI-prompt descriptions

We’ve significantly enhanced ReviewAI's capability to verify checklist checks by providing it with richer context directly from your proofs. Previously, ReviewAI only used the text from the individual checklist item descriptions (the AI prompt) as the basis for verifying the asset against the criteria for each check.

With this release, ReviewAI now utilizes a broader range of contextual data from the proof to inform its checks:

• The entire text of the Proof Brief can now be referenced by ReviewAI, in addition to the individual checklist item prompts.
• Custom Property information is also sent to the AI for use as context. This includes the Custom property name, Property ID, Description (Hint), and Value.

By incorporating both the Proof Brief text and Custom Property data, ReviewAI is equipped with a richer contextual framework. This allows you to create checks that directly reference information in the Proof Brief or custom fields, helping the AI frame what it should be looking for more precisely and enabling checklist items to reference this supportive data.

ReviewAI remains in public preview, and is available to Enterprise customers as a paid add-on. This feature may have a sizable effect on how you create checklists for ReviewAI moving forward. To learn more about this paid add-on and how it can benefit your team, please reach out to your Customer Success Manager.

Update to monday.com flow templates

Ziflow has an added a new flow to the monday.com template suite. The new flow, Monday - Change, remove, add item on Ziflow Proofs board, handles syncing proofs between monday.com and Ziflow. With the Monday - Change, remove, add item on Ziflow Proofs board flow you can:

• Add proofs from Ziflow that predate your monday.com integration
• Delete, change, or add proofs in Ziflow and have the updates automatically sync to monday.com

For instructions on how to update to add this new flow, see Update monday.com flow templates.