Forum Discussion
JohnRogers3
Qrew Trainee
I would say a decent amount of effort. The thing about Quickbase is it does not allow you to see the payload from an API response. So you need to have a server, or a middleman software to manipulate responses between Quickbase and priority ERP.
The things that are simple that Quickbase can do. You can use a webhook to hit an endpoint using XML or JSON to send data. (you will not get response, EX: if your first step in the API is to receive an auth token)
You can allow a 3rd party to post into your APP with a userToken/appToken and field_ID numbers and your Quickbase domain URL.
The things that are simple that Quickbase can do. You can use a webhook to hit an endpoint using XML or JSON to send data. (you will not get response, EX: if your first step in the API is to receive an auth token)
You can allow a 3rd party to post into your APP with a userToken/appToken and field_ID numbers and your Quickbase domain URL.
JohnRogers3
6 years agoQrew Trainee
Because there are very few limitations that Dan knows better than I, that allow responses through URL response. Without that, you cannot access a payload that shows a response to filter without a middleman (Zapier or your own server).
Quickbase Webhook will take an action and send data based on the action.
Most APIs require an auth step, usually known as a Bearer token response, to resend the API with an authorized action.
The native Quickbase webhook cannot receive the response to .parse() to place into a bearer token. So Zapier handles this.
I can get into more detail if you need, email me JRogers@zoisolar.com
Quickbase Webhook will take an action and send data based on the action.
Most APIs require an auth step, usually known as a Bearer token response, to resend the API with an authorized action.
The native Quickbase webhook cannot receive the response to .parse() to place into a bearer token. So Zapier handles this.
I can get into more detail if you need, email me JRogers@zoisolar.com