The Workflow for ‘GetAvailableTimeSlots’ is run on the server vs. the on page element which runs client side. So this allows you to run the workflow in a Backend Workflow or to run it in a ‘loop’.
It performs the same function as the on page element and doesn’t create any data, it just reads and returns a list of available time slots. In most cases if you want to show on page availability for a single ‘Calendar/resource’ I would suggest the Element as it is quicker and updates each time a field within it is changed.
Some specific cases could be:
- You want to save time slots directly on a resource to make them more easily searchable, you would have an ‘update times’ backend workflow that updates the time slot list every time the Calendar/Resource is changed
- If you want to run a loop and look up availability of many Calendars/Resources at once (similar to what I have described in this thread topic when using the Orchestra plugin, but in a way that can work on a backend)
- You can setup an API that when it get’s pinged it returns the list of available times
