Update on the retirement of Application Webhooks UI and QB Actions

Actually creating an Webhook is (well would have been) a great suggestion. He has all the field names, and all the field IDs and the payload of a web hook to add a record is very repetitive pure text, so quick to copy paste edit. 

yes, another reason not to deprecate Webhooks. 

there is also a webhook syntax I have used to create an audit table of fields that have been changed. It uses ImportFromCSV (I think that is the API) to quickly create child record for field name,old value and new value.