I've used zapier.com to accomplish similar tasks. Essentially, zapier is a point-and-click integration engine that connects any two web-accessible apps that both have APIs. For some apps, including Quick Base, they pre-built some typical intergations. For your purposes you would probably build a "zap" with these "tasks" (zapier lingo for an integration with these steps):
- Every 15 minutes, zapier queries Quick Base to see if there is a new row (record) in your table.
- A webhook Get queries your external app with URL that contains fields from the Quick Base record.
- A filter continues only if the webhook was successful.
- A webhook makes a call to your table in Quick Base, with a=api_editrecord and field-values written from data found in step 2
- Optionally, you might use another filter as the final "task" to check whether the Quick Base api response exactly matches "No error"
One limitation is that zapier limits the number of zaps per 15-minute interval to about 100. Post a reply here if you'd like some ideas for working around this problem.
Finally, a totally different strategy would be to copy (some portion of) your order data into a Quick Base table using "connected data" ... To get an idea how this might work, start creating a new table "using connected data" and see if any of the options might work (e.g., your relevant order data gets dumped periodically to a CSV file somewhere.) Again, write back here if this seems more promising than zapier.
