You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a webhook configured to trigger on Create, Update, and Delete.
Every time I publish a document, it triggers.
I am triggering webhooks too often and hitting rate limits with the service receiving the webhooks.
Describe the solution you'd like
I would like to edit a batch of documents in the content studio and then click "Publish" once to publish all those drafts together, thus --hopefully-- triggering a single webhook event.
Describe alternatives you've considered
My current workaround is to disable my webhooks when updating many documents. This is not ideal, especially because I have no way of disabling them problematically (#8242).
The text was updated successfully, but these errors were encountered:
Hello @mtilda ! I'm sorry to hear about the less-than-ideal experience. You may be interested to hear that our upcoming Content Releases feature will indeed allow you to add a number of changes across different documents to a release and schedule them all to go out at once.
This feature will be entering public beta very soon! Please be sure to follow along in our community to know when it will be available for you to try!
Is your feature request related to a problem? Please describe.
I have a webhook configured to trigger on Create, Update, and Delete.
Every time I publish a document, it triggers.
I am triggering webhooks too often and hitting rate limits with the service receiving the webhooks.
Describe the solution you'd like
I would like to edit a batch of documents in the content studio and then click "Publish" once to publish all those drafts together, thus --hopefully-- triggering a single webhook event.
Describe alternatives you've considered
My current workaround is to disable my webhooks when updating many documents. This is not ideal, especially because I have no way of disabling them problematically (#8242).
The text was updated successfully, but these errors were encountered: