So there is a lot of code which is going to have to happen. Let me try to simplify, but I will say ahead of time you will need a developer to make this happen. (Yes CRM = QuickBase sorry)
QuickBase Webhook -> QuickBase Code Page
QuickBase Code Page (will need javascript knowledge, JSON, XML, AJAX, depending on route you chose)
Code Page takes data from webhook and does whichever POST you want, EditRecord, NewRecord, etc. (Is this pre existing data on your server, are you adding data, are you finding data?)
Code Page to run javascript needs the Image Onload Technique which I believe Dan created to (if you google iol Quickbase technique you will find it)
Once received at the endpoints you posted to (javascript inside codepage formats data, then Ajax call or whatever call you pick posts the data) You set up a trigger that will be hit from your QuickBase post. I find CheckBox's the easiest to use as API/webhook triggers
Then basically you mirror previous steps but send new data to Quickbase with editRecord, NewRecord, whatever you're trying to do.
________________________
Lots of steps, lots of code, lengthly process, you will 100% need a developer to do.
With Zapier, this is why I recommend it, you do not need a developer.
Zapier catches your webhook from QuickBase, it lets you pick pre-made actions, it does 80% of the coding for you other Than the raw data which was the example I showed above,
{
"imnamingthisvariablehere": "[quickbasefield]",
"anothervarisbleimnaminghere": "[quickbasefield]",
"triggerMyServerResponse": "True"
}
So the question to ask is, is it worth it to pay for Zapier, or pay for a developer. Most QuickBase developers who have the knowledge to do internal API calls are very expensive hourly.
If I had to do this setup for my company I currently work for, exactly what you are trying to do. It would take me probably an entire week. Hope this helps.