I am new to Thunkable so still finding my feet but I have successfully built out 2 apps (so far) which we will deploy in our business (I am enjoying the process of using Thunkable )
- The first app allows customers orders ready for collection to be located in our holding bays. I use the Airtable API to either update an existing record, or create a new record by using a different call in Airtable .
Our operatives can then search by the customers order id or their postcode to show a list of orders ready for collection and direct them to the correct bay(s).
Finally we produce a confirmed collection with a photo using the camera which is then stored again in the Airtable record.
- The second app is used on a tablet in our reception to provide a customer interface for order id input. This changes the status of the Airtable record, alerts our staff and can be seen on App 1 above as the customer is on site.
One of our staff had an idea to incorporate a button in the confirmation email which is sent to the customer to allow them effectively bypass the reception interface by letting us know they had arrived from their email client.
Our warehouse software sends an email informing the customer their goods are ready for collection. I can dynamically append the url parameter to include the order id which can be passed to the browser upon clicking.
This order id matches the id I already use frequently in the above two apps .
I saw that Thunkable apps could be deployed as a Web App rather than specifically onto and IOS or Android device which gave me the idea to create a ‘webform’ using a Thunkable Web App. I knew that with most webforms you can prepopulate fields with UTM parameters, I was hoping to do something similar with Thunkable, however in this scenario I would use the parameter and store it as a variable,
In this app I could build out API call blocks similar to those I have already been using in the other apps to GET customer info from Airtable and then update the status using a PATCH call.
(BTW be able to build out interactive webforms in this way would be pretty cool…I could see a lot of uses for this, so having the ability to pass the parameters from the URL would be mandatory requirement )
So I’m not sure if you can help with a work around…