Suggestion: Webhook filters (equivalent to automations) to reduce load?

Developer Talk Integrations
,
1

Your Setup:

  • SeaTable Enterprise
  • SeaTable Version 4.4.9

Describe the Problem/Error/Question:

I’m using webhooks and n8n to integrate Seatable with other systems. Works well, however Seatable creates quite some load on other systems, because the webhooks fire on each and every change in a base. Therefore, a receiving system like n8n has to filter the real triggers from the overall noise by looking at all the POSTed data in the webhook call. This is a) very load-intensive and b) ineffective.

First question: Am I overlooking something?

If not, here’s a suggestion: Seatable already has a fine-tuned filter mechanism in various places, namely the automations. Couldn’t a mechanism like this be added to the webhooks, so they trigger only on specific occasions? Or, alternatively, an action like “call URL / webhook” be integrated into the automations?

What I really like about the existing webhook is that they are already POSTing all the relevant information. If that could be retained, that would be great!

1 Like
2

Thanks for the long detailed suggestion. Currently we don’t have a plan to add webhook filters. We will record the request internally.

You are free to add a feature request in the “Feature Request” category.

3

Don’t post in the feature request category. use https://ideas.seatable.io instead.

4

Done! Started out as the question “am I missing something”, and turned into a suggestion along the way :slight_smile:

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.