Is it possible to make multiple API calls (same API) from a webhook ? I am trying to overcome the issue of a max of 5 webhooks per table.
I don't think conditional statement will not help in my case.
Forum Discussion
Just some info about WebHooks: they are not really "a thing" in the sense of a standard or a technology. It is more of a marketing buzz word for a bundle of features related to detection of events and triggering of network requests across domains. You will not find a W3C standard for WebHooks - it does not exist.
That said, WebHooks are considered to be a server-to-server communication that occur when a server-side event triggers the WebHook.to execute a network request (normally a POST). In general the communication is between two different domains but QuickBase has allowed you to create a WebHook that detects an events such as {new, edit, delete} record and an API call back to QuickBase's own server. This is somewhat unusual because normally this type of service is implement in a product feature not called a WebHook or through a product's API. Also, in some implementations of WebHooks there is limited feedback, minimal logging, or rate limiting which makes the execution of the WebHook somewhat unreliable.(but very low probability unless you are exceeding some limit). Finally, WebHooks only respond to those events the provider chooses to detect - in the case of QuickBase this is only {new, edit and delete} records event (there is no "view record" event).
However, using script you can detect a vastly wider universe of client-side events - everything from a mouse movement to the clicking on a button as well as record related events. So as a final thought, if you can't accomplish what you want with QuickBase using a WebHook targeted back to QuickBase, you probably can accomplish what you want using script.
That said, WebHooks are considered to be a server-to-server communication that occur when a server-side event triggers the WebHook.to execute a network request (normally a POST). In general the communication is between two different domains but QuickBase has allowed you to create a WebHook that detects an events such as {new, edit, delete} record and an API call back to QuickBase's own server. This is somewhat unusual because normally this type of service is implement in a product feature not called a WebHook or through a product's API. Also, in some implementations of WebHooks there is limited feedback, minimal logging, or rate limiting which makes the execution of the WebHook somewhat unreliable.(but very low probability unless you are exceeding some limit). Finally, WebHooks only respond to those events the provider chooses to detect - in the case of QuickBase this is only {new, edit and delete} records event (there is no "view record" event).
However, using script you can detect a vastly wider universe of client-side events - everything from a mouse movement to the clicking on a button as well as record related events. So as a final thought, if you can't accomplish what you want with QuickBase using a WebHook targeted back to QuickBase, you probably can accomplish what you want using script.