ErichWehrmann
Quickbase Staff
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Sending form encoded data vie Webhooks
Did some research and discovered that this was indeed possible. The payload type need to be RAW, the Content Type header need to be included with a value of 'application/x-www-form-urlencoded' and the data attributes are put in the body as key value/value pairs and separated with ampersands (&). @Kirk Trachy published a video demo: https://www.youtube.com/watch?v=zO9Qs-IeoRA&feature=youtu.be ------------------------------ Erich Wehrmann ------------------------------Sending form encoded data vie Webhooks
Was looking into integration with the Twilio API and it appears they only accept form encoded data in the post body. Has anyone had success creating a table Webhook that properly sends a form encoded (x-www-form-urlencoded) body via a webhook? ------------------------------ Erich Wehrmann ------------------------------Re: is it possible to create a quick base action or a automation for the creating the history record
Quick Base Automations give you the ability to utilize the old/previous value of a changed record. When you have the Values from Other Records menu up, scroll down to the record from trigger (old values) section to grab the old value of "80" to put into your new record. ------------------------------ Erich Wehrmann ------------------------------Re: Quickbase Attachment from Egnyte File Sharing
Hi Syaeful, The 'New Record in Quick Base' trigger only returns the Record ID as a parameter, it doesn't contain the complete payload of data from the newly added record. You can add a 'Find Record in Quick Base' action and set that up to search for the Record ID that matches the Record ID from the newly created record in the 'New Record in Quick Base' trigger. The 'Find Record in Quick Base' step will give you the file from the file attachment field that you can then use to upload to Egnyte. ------------------------------ Erich Wehrmann ------------------------------Quick Base Apps for Dev Ops
When you start to design and build apps in Quick Base one thing you quickly learn is how rapidly you can build user interfaces (UIs) for collecting data (Quick Base Forms). As a long time QB builder and integration developer I’ve learned that the speed at which I could build front end UIs and capture data into a table is truly unmatched by any other software platform I’ve worked with. In a previous Dev Ops role, I discovered that I can leverage Quick Base’s speed and flexibility for many projects that I would not have originally thought to build on a No Code platform. Data elements that are bound to form elements, ability to use HTML and JS, data validation, and advanced rules capabilities with native forms are some of the features and properties of the platform that I appreciate for rapidly building UIs. Recently I had to create a way to manage access to an Azure Virtual Machine (VM) and after a little thought about this might work, I built an app! Here’s the use case: Create a VM in Azure that is accessible by a group of engineers. To save cost the VM should be off when not in use. Usage of the VM should be tracked to justify cost. Engineers should not have access to the VM via Azure portal. After doing a little research I learned that I could use API calls or timers to turn the VM on or off. I also needed a database table to track the access requests. For a quick and simple UI, a data table, and an API integration my next step was obvious…build an app! Within a couple hours I had a Quick Base app with 3 tables, a webhook, a workflow in MS Flow, and notifications to end user. The engineer wanting to access the VM now goes into the Quick Base app and creates a new request. That new request record triggers a webhook to MS Flow that will check to see if the VM is running on and start it if needed. Once the VM is running the engineer is sent an email that it is ready. The Quick Base application also contains documentation and support materials for using the Azure VM. Each evening the VM is automatically turned off save cost as there is no overnight engineering shifts. Creating the request in Quick Base takes a few seconds but the app is able to collect the time and date of access, the engineer requesting use, and some additional attributes about intended use which all might provide additional insight at a later date. I hope this example helps spurs some creative new apps! If it does, please share them with me! Erich Wehrmann Best Practices ConsultantRe: QB App to API and Vice Versa
Hi Vijay, You will need a separate tool to integrate QB with JIRA. There are many options for this such as: an integration platform like Workato or Informatica, a workflow tool like Zapier or MS Flow, or writing your own custom code and publishing it to a sever. Hope that helps.Re: cURL from quickbase
When making a call to the QB API, the data needs to be in the proper format for that method. Depending on which method you are using this format can be URL paraments, XML or CSV. If you are retrieving JSON data from another source you will need to transform this data to the proper format. If you are attempting to add or update records in bulk, you should put your data into CSV format and use the API_ImportFromCSV method.
