Currently when choosing the “Content Delivery API Cache Tags” trigger entity, you can only choose “Invalidate” as event. This setting will trigger the Webhook on any modification of a record (saving, publishing,…) and therefore causes an API call to the defined API endpoint. This can generate costs.
It would be nice if there would be more options for events, like for other entities, to specifically choose when the Webhook will be triggered. (only on Publish for example…)
Use case example: When using Next.js and it’s preview mode and we have a Draft/Publish Model it’s not necessary that the Webhook calls the defined API endpoint on every update/save of the record. Only on a publish it should revalidate the cache of the frontend.
See: Slack