Webhooks events

  • From Nintex Automation (5.7) onwards there are two different apps for SharePoint. The legacy Nintex K2 for SharePoint: used for SharePoint on-premises and upgraded environments for SharePoint Online, and Nintex Automation for SharePoint: used on new installations for SharePoint Online.
  • Microsoft has announced the deprecation of the SharePoint Add-Ins model for SharePoint Online, effective 2 April 2026. We recommend migrating to Nintex Automation for SharePoint using the Nintex K2 for SharePoint SPFx migration tool to avoid potential disruptions.

For the product in SharePoint Online, the event receiver now functions using Webhooks. Webhooks is a modern web integration scheme to allow third party services to receive notifications when an event occurs in the source system. This allows the product to receive notifications instead of having to poll at regular intervals to find out if something has changed. Webhooks are not SharePoint specific and more web services are supporting Webhooks in general to allow system integration.

SharePoint delivers Webhook events asynchronously, which means workflows may start out of sequence or after a delay due to internal queuing. In most cases, events are processed within about one minute, but delays of up to five minutes are possible. In rare situations, delivery may take as long as 24 hours. These timing variations are inherent to SharePoint and are not within the product’s control.

Troubleshooting

The following Designer action is currently not supported:

SharePoint > Document Library:

  • Discard Document Check Out

SharePoint Online workflow events

If you have issues with Nintex Automation for SharePoint workflow events, make sure the Webhook URL for the list is subscribed by SharePoint and is publicly accessible:

  1. Navigate to Management.

  2. Execute the Get Webhook Subscriptions SmartObject method.

    • Categories > System > SharePoint 2013 Integration > SharePoint Integration Helper Methods > Methods > Get Webhooks Subscriptions.
  3. Enter the SharePoint Site URL and a List Title.
  4. Execute the method.
  5. Verify the NotificationURL result contains the K2 Server SharePoint Webhook Endpoint URL.

If the K2 Server SharePoint Webhook Endpoint URL does not exist:

  1. Edit your workflow, and rerun the Start Event configuration to re-subscribe the Webhook or Update URL.

  2. Re-deploy your workflow.

  3. Verify that the Webhook URL is accessible from public internet using the steps above. SharePoint validates this URL during the re-subscribe.

SharePoint Online workflows not starting

If your workflows are not starting, use the following steps:

  1. Open the Windows Event Viewer (you can search for Event Viewer from your Start menu).
  2. Expand Applications and Services Logs and select the K2 category.
  3. Check for K2 SharePoint Workflow Integration.
  4. The Information message's Source column shows when the SharePoint Webhook Endpoint is called.
  5. When SharePoint raises an event, the Webhooks endpoint will be processed.

Also check for errors in the:

See Known issue