Hello, everyone,
I was wondering why the watch items action for SharePoint list doesn’t have immediately as a trigger option.
Thanks
Hello, everyone,
I was wondering why the watch items action for SharePoint list doesn’t have immediately as a trigger option.
Thanks
Hello @Peter_Chen,
Instant triggers require webhooks, which Sharepoint either doesn’t support, or Make’s module needs to be updated if it’s supported.
What you have here is the only option remaining, which is a polling trigger.
If you are good with APIs then you can look into whether Sharepoint supports webhooks.
If you manage to create a webhook subscription, then you can start your scenario with a Custom Webhook Module then supply the address it gives you as the webhook address when setting up the subscription in SharePoint.
If I poll every minute, is it going to run up my cost (use up my runs)? Unfortunately, I am not good with APIs as I am a beginner.
Thanks for fast response.
Yes each time it runs and finds nothing new will use 1 op.
This is also known as a ‘Check Run’.
You can filter out Check Runs from your scenario run history so that you are able to focus on runs that did find some data to work with.
Yes, Sharepoint does not support webhooks.
For more information, see Sharepoint API documentation.
samliew – request private consultation
Join the Make Fans Discord server to chat with other makers!
Looks like SharePoint does support webhooks, but it works like some Google webhooks in that it doesn’t give you much data in the payload.
The notification doesn’t include any information about the changes that triggered it. Your application is expected to use the GetChanges API on the list to query the collection of changes from the change log and store the change token value for any subsequent calls when the application is notified.
To make it just a little bit more complicated, when you create the subscription, you need to validate it by sending a response.
So one scenario (or Custom App) would need to create the webhook using HTTP followed by Webhook Response.
Then another scenario using a Webhook Trigger would receive the change notification from SharePoint then use GetChanges API to get the actual changes.