Ziflow Connect: diagnose failed flows with Zibot details modal

When a Ziflow Connect flow fails today, users are able to see a red failure indicator, but no explanation as to why the flow failed. This makes troubleshooting difficult for teams building and managing automations.

With this release, failed Ziflow Connect flows now include a detailed error view. Clicking into the Zibot details modal of a failed flow will now display the API response returned by the connected service. Depending on the integration, this may appear as raw response data or as a human-readable error message from the provider. This response is only visible to the owner of the flow, the admin who initially created it. For more information, see Troubleshoot failed flows.

While error responses may vary by integration, this update provides teams with direct visibility into what went wrong, making it faster and far less frustrating to diagnose and resolve automation issues.

Import Comments from PDFs (in public preview): display prompt in Proof Viewer

We’re introducing a new setting that allows Admins and reviewers to display a prompt to import comments embedded in uploaded PDFs. A new Account-level setting, "Show Prompt to Import Comments from Original PDF," allows Admins to enable a blue import prompt box for the entire account. If this is toggled off, the prompt is suppressed for all users in the Proof Viewer.

Reviewers can dismiss the prompt by clicking "Ignore" inside the blue box. This action hides the "Show prompt to import comments" setting in their individual Proof Viewer controls, ensuring they won't see it again unless they manually re-enable it. Note: Dismissing the prompt does not prevent users from importing comments at any time via the 3-dots menu in the Comments panel. For more information, see Turn on display import prompt.

This update provides Admins with the ability to allocate feature capabilities at a granular level, helping to maintain a consistent and predictable review experience for all teams. Importing comments from PDFs is a feature that’s still in public preview, and we would love to hear your feedback about these additional capabilities before it becomes generally available.

SharePoint integration: File name conflict resolution setting

When a file uploaded to SharePoint via a Ziflow Connect automation has the same name as an existing file in the destination folder, conflicts may arise, including API errors. 

With this release, a new “File name conflict behavior” dropdown setting is now available in the SharePoint Zibot configuration, giving you control over how to handle uploading a file to a folder where a file of the same name already exists. You can now choose one of three options in a dropdown menu:

• Rename (default): SharePoint will automatically add a numerical suffix (e.g., _1, _2) to the new file name
• Replace: Overwrites the existing file with the new one
• Fail: Stops the flow and flags an error if a file with the same name is found

This new functionality replicates standard operating system behavior for file management, providing greater control and predictability when managing files through your SharePoint automations. For more information, see SharePoint Zibot actions.

Ziflow API: New call-and-response endpoint for PDF report downloads

For customers with strict security protocols, receiving an external notification that a PDF proof report or PDF comments download is ready via API can sometimes fail, as security settings may prevent the customer's endpoint from receiving the direct "ready" notification.

We have introduced a new, polling-based API endpoint to facilitate reliable download delivery for these scenarios. This new endpoint allows your system to query the Ziflow API to check the status of a PDF report or comments download.

If the file is not yet ready, the API will respond with a status of “In_progress”. When the file is ready, the API will respond with “Finished”, followed by the direct download link. Files available for download have an expiration date; if this is the case, the API will respond with “Expired”.

This enhancement ensures that security-conscious teams can reliably integrate PDF report and comment delivery into their automated workflows. The call-and-response model provides a dependable mechanism for confirming file readiness before download.

For more information, see the Export comments and Export summary.