Document Sets are a standard SharePoint content type and their creation is technically an item creation operation (folder item with a specific content type). In enterprise SharePoint environments, Document Sets are widely used as business records containers and process entry points.
Currently, K2/Nintex does not provide a native trigger when a Document Set or Folder is created in a document library. This creates a functional gap compared to expected SharePoint behavior and also compared to previous Nintex for SharePoint on-premises capabilities.
This feature would allow workflows to start immediately when a Document Set or Folder is created, without requiring workarounds such as polling, metadata update triggers, or custom event integrations.
This is especially important for organizations that:
Use Document Sets as process containers
Need immediate workflow start on record/container creation
Are migrating from legacy Nintex for SharePoint solutions where this behavior was available
Currently, the lack of this trigger increases implementation complexity and forces customers to build custom integrations outside of the platform.
Adding native support for:
With the deprecation of SP Add-In support and the move to Webhooks for SharePoint online events, looking at the MSFT documentation, I don't see an event that SharePoint would allow K2 to hook into for Document Sets. When looking at the guidance for migrating from SharePoint Add-In-based remote event receivers to Webhooks, it isn't listed as a webhook event that Microsoft exposes.
ItemAdded
ItemUpdated
ItemDeleted
ItemCheckedOut
ItemCheckedIn
ItemUncheckedOut
ItemAttachmentAdded
ItemAttachmentDeleted
ItemFileMoved
ItemVersionDeleted
ItemFileConverted
Good idea, though. I scanned the Document Set documentation and didn't see any mention of events or triggers. š¢ If Microsoft doesn't expose it, then K2 will never be able to consume it.
Also for Document Set Edit trigger