Blog Post
I'm not sure if that was already addressed but I want to add 2 more points missing in Pipelines.
But first I want to say that I'm really nerves about QuickBase ending Webhooks. I would suggest extending the life of Webhooks for a while after all the concerns addressed here are solved and implemented and given time to test.
And here are my 2 points beside the others I found discussed above.
- Pipeline is missing the %Action% marker (that's beside the supper important marker of %repeatOn% %repeatOff% )
- Pipeline by nature turns off by any updated in the flow. Which leads to 2 concerns.
- Missing triggers until it is turned on.
- Forgetting to turn it back on.
Webhooks are too important tool to pause on it own even for a split second.
I hope you will read my concerns and take in consideration.
Adding another point.
I see XML API was already addressed.
I want to add another point about and important feature missing from Pipelines.
In Webhooks the way to reference a filed is simple it can be done either by its field name or field id for example [3] or [record id#] this it true in the webhook designer and in the XML API. So, it makes it possible to dynamic create a webhook on the fly based on given criteria. On the other hand, in Pipeline the way a field is referenced is based on the output field and with a trunked version of the field name. Which makes it impossible to dynamically create a webhook call with wanted fields.