In this article, you'll find a list of our most impactful new features and enhancements that we have released this month.

Don't worry, for more significant enhancements, you can still check out our blog, as well as read our newsletter. If you have questions about these items, don't hesitate to contact our support team.

With this release, Comment Reactions can now trigger automated flows, giving admins even more flexibility in creating a repeatable workflow. Just like using Comment labels to act as a trigger, admins can use Comment Reactions in the same way, including settings to specify either a Comment or Reply, either a specific Reaction type or any Reaction, and other adjustments to more precisely calibrate the flow itself.

This is particularly valuable if your process includes the call-and-response interactions that Labels (used by your designers), and Reactions (used by your reviewers) can provide. So, once feedback is completed (labeled as “Done”) and those updates have been confirmed (reacted upon as “Verified”) in Ziflow Viewer, a workflow can automatically bring the review to the next phase.

The Ziflow Viewer displays “pins” within an asset that correspond to comments left behind, helping reviewers gain precision with the feedback they offer to designers. But in the past, it was impossible to know which of the elements that the pins corresponded to were already addressed during a round of edits.

With this release, we’ve changed the way the comment pin appears within an asset when the comment that corresponds to it has been marked as resolved. For all resolved comments, a small “check” will appear alongside the number of the pin, providing an easy visual indication that this aspect of the requested edits has been completed by the designers. This is especially valuable for teams with multiple designers working on the same proof, helping to prevent repetitive work and redundant edits simply by letting other designers know that a change has already been made.

Ziflow Connect gives you the ability to create seamless connections with almost any software solution through our API, with many of these connections built using our Webhooks functionality, which leverages representational state transfer (or “REST”) architecture.

Traditionally, the RESTful coding style utilizes two primary commands: "POST" (or "PUT") and "GET". However, with newer APIs, two additional commands have emerged: "PATCH" and "DELETE". With this week’s release, these commands have been added to the settings for the Webhook Zibot, unlocking even more API-based capabilities.

This update helps Ziflow expand the integration possibilities with various SaaS applications that have built APIs with more modern RESTful codebases. For example, platforms like Notion can now be connected to Ziflow via a Webhook Zibot, helping to streamline collaboration within your creative tech stack.