Enhancement Request: Option to Limit Webhook Triggers to Human Actions Only

Feature Ideas
1

Dear Baserow Team,

I am writing to propose an enhancement for the webhook functionality in Baserow. Currently, the webhooks are triggered by actions such as creation, modification, and deletion, including those performed via the API. In my use case, I find that this setup triggers an excessive number of webhooks, many of which are not necessary for my workflow.

I would like to suggest the introduction of an option within the webhook settings that allows users to specify that webhooks should only be triggered by human actions, excluding those made through the API. This feature would enable more precise control over webhook triggers, significantly reducing the number of unnecessary calls and enhancing the overall efficiency of using Baserow in various workflows.

I believe that this enhancement would be beneficial to many users who seek to have more tailored webhook triggers, especially in environments where both manual and API interactions occur frequently.

Thank you for considering this request. I am looking forward to potentially seeing this feature in future updates.

1 Like
2

Hello @Preview7282, I’ve discussed your feature idea with the team. We like the idea, and we are definitely planning to include this setting in Baserow. However, we currently don’t want to spend the development resources to enhance the way webhooks work, as we intend to start working on the automation builder module in about two months. As soon as we start with the new product, we will make sure to create an issue for this request. Thanks for bringing this up. :slightly_smiling_face:

3

Oh, this sounds interesting. I have a similar issue with webhooks triggering multiple times on updating a table manually (may have just been a glitch, seems ok now) but it would be great to have a little more control over the triggering. The ease of creating and using webhooks in BaseRow is one of the things I love about it. :slight_smile: