I use integromat for most of my backend but Iāve hired an engineer to help me out @mubeeniftikhar so we are ready to figure out how to solve my various use cases:
how to use an integromat scenario that produces an agent ID and TestFlow ID ā¦. And push that to the Agent sheet, matching against Agent ID (row id) and writing the tfid into ācurrent tfidā
programmatically set columns in the TestFlow table to clear all or some values
writing button presses between agent and user so that the button in the customer app appears 15-300 seconds faster (even in a glide table)
mmm, and I could insert my Facial Recognition scans directly into Glide. Been waiting for this for monthsā¦
Although, just thinking about it - in my case I need to be able to do an āupsertā - so if I canāt search rows via the API, then it may not meet my use case.
Writing into Glide directly from another system is up there with āFind All Usesā, āXC columnsā, Plugins, and a working data editor in the bottom left. OK, having fun with the last thing!
The GS-Glide round trip can be 15-300 seconds, which leads to a terrible user experience for some types of apps. But with this bit of magic code, the world becomes beautiful (until the next thing we come up with
OK - Thanks to @mubeeniftikhar (who works for me at Covessa we have made a ton of progress. He will write up how things properly work soon, but I thought I would share work to date beforehand.
In the Data Editor, right click and see if you have a āShow API Keyā option from a table on the left
works with Glide Tables (GT) and Google Sheets (GS)
You have the option to copy the code for:
Add Row
Delete Row
Set Columns (in a row)
You find a row with the Row ID (look at the bottom of the codeā¦ you might have renamed the column)
You will see that Glide has remembered the old column names and maybe even order you had weeks ago when you started building the app - but no panic, the current column name (and therefore use you are making of it) is written too (I have āDateā:āInc/ Agentā for my agent increment, for example)
We are using Integromat so we started with a simple Set Variables module to set variables to test, then pushed in these values to test in an experiment app to see if they work.
Your JSON needs to be formatted as Beautify otherwise it will not work
you need to put the values you want to write in into quotation marks""
There will be some other things to take note of - but in the meantime here is a short video to walk you through magic
Is that 3 seconds in the builder, or 3 seconds in the client apps?
As I understand it, the change is pushed via the API to the Glide back end, but it then needs to sync to each client app - correct?
Although thinking about it, the builder is in some ways just another client. So if it syncs from the backend to the builder in 3 seconds, then itās probably a reasonable expectation that the clients would get it in a similar time frame?
yes and I worked out a magic trick to process lots of rows at the same time.
There is no āsearch rowsāā¦
So instead you do:
in the Glide table, work out what your search criteria might be (in my case TestFlow rowā¦ if agent inc existsā¦ at 2amā¦ this means we need to reset data in the entire rowā¦ so maybe 50 - 200 rows in a 6K+ table currently)
from the ITE- if true, then put in the TFID (rowID) of the Row
then make a joined list - of all the TFID rows that match
then have a button with a Glide Webhook (I am using these more - initiate in integromat, then you do not need to be as careful with the parameters)
the webhook sends a single parameter - ActiveTFIDs - a long string with a comma separator (for now)
Then I set a variableā¦ and then split the variable with an iterator (did not want to work without one) ā¦
and then stored each TFID (Row ID) as a row in an Integromat Data Store (only one parameter - TFID and the key is the TFID too)
then an HTTP POST call - with a beautify formatted JSON list - to emptyystring the values I want to clear
then a tidy up - delete the row in the Data Store, and send a Discord message at the end to the support team to say the work is now done
And - after two hours this morning - we have now worked out how to use the new Glide API to work on hundreds of rows at the same time
Next trickā¦ I have to think through how to populate my TFID data store automaticallyā¦ and then run the scenario at 2am.
Unsure right now @V88 ā we want everyone to have access but there is the potential for abuse and high costs on our side. Weāre still learning about it and figuring out how best to offer it more broadly.
I understand that @Ian but this could remove one of the last remaining reasons to use Google Sheets rather than Glide Sheets? Surely a positive across the platform? Anyway, great news that itās working!
so we are ready to figure out how to solve my various use cases:
