File Connector API improvements now available

Hi everyone,

Following up on our previous announcement about upcoming File Connector API enhancements, we're happy to share that the improvements are now being rolled out to production next week.

The release includes several new capabilities designed to make file synchronization easier and more efficient:

Full sync

You can now perform a full synchronization, where all previously uploaded files are removed before the new file set is processed. This feature is already available in production.

Incremental sync with delete support

In addition to adding and updating files, incremental synchronizations now support deleting previously uploaded files. This makes it possible to keep your knowledge source fully synchronized using a single sync operation.

Abort sync

Administrators can now abort an ongoing synchronization before indexing starts, providing greater control over the synchronization process.

Support for filenames with spaces

Files containing spaces in their filenames are now supported and will no longer be rejected during upload.

Bulk upload support

You can now upload multiple files at once using a ZIP file, reducing the number of API calls required for large content updates.

These enhancements are intended to simplify integration scenarios and improve synchronization performance for customers managing larger content repositories.

For implementation details, please refer to our documentation and FAQ:

FAQ: How to sync knowledge sources using File Connector APIs? - Genesys Cloud Resource Center

As always, we welcome your feedback and questions in the comments below.

Thank you,
Zsolt

------------------------------
Zsolt Fodor
Senior Product Manager, Knowledge Fabric
------------------------------

Hi Zsolt,

Thanks for sharing these improvements. The bulk upload and incremental sync with delete support look particularly useful for managing larger knowledge sources.

From a troubleshooting and support perspective, I'm curious about error handling during bulk synchronization. If a ZIP contains multiple files and only one or a few files fail validation or processing, will the entire synchronization fail, or will the valid files continue to be processed?

Also, will administrators be able to identify the specific files that failed and the reason for the failure from the sync results or logs?

I think this visibility would be especially helpful when troubleshooting larger content updates.

Thanks!

------------------------------
Mcel Turalba | Genesys
Support Product Engineer
------------------------------