push data from web captioner to google sheets via webhooks built using apps script.
the problem – playing with webcaptioner.com which lets you specify a webhook url. i was experimenting with adding captions to a google doc in realtime but apps script couldn’t keep up dropping ~20% of the captions sent via the hook
Sourabh Choraria kindly helped me solve an issue I was having passing data from webcaptioner.com to Google Sheets. Click through to the source link for the full explanation from Sourabh, but in essence the problem was I was losing data because I wasn’t using the LockService.
In the meantime webcaptioner.com have also updated there channel webhooks so you can set a data chuck size so if you are looking to capture a transcript in Google Docs you can use the following published as a container bound web app:
Get stats for your current active sheet & the entire spreadsheet in one place using workbook statistics – a g suite editor add-on built using google apps script.
A handy Google Sheets add-on from Sourabh Choraria that can give you an Excel like summary of the Google Sheet you are working on that can display information like the number of: filled cells, formulas, charts and more. This post is also worth reading if you are interested in tips for the Add-on publication processes, highlighting some of the pitfalls you can avoid. The code for the Add-on is also open source making it possible to reuse in your own Apps Script projects.
Most conversations around solutions or automations created using Apps Script eventually get to a point where being able to address concerns around its reliability, security and scalability becomes a challenge — more so if compared to having similar applications being built on other platforms (say: AWS, GCP, Firebase etc.).
In this post, we’ll see how to navigate our way through said constructs by addressing parts of these problems and also explore ways in which we can bake some solutions right from the get-go!
In this post Sourabh Choraria provides some very useful answers for common questions organisations have when using Google Apps Script as part of their infrastructure. Points covered in this post include: managing concurrent executions; being able to securely store, access & manage API keys, tokens; and considerations around quotas.
make use of firebase’s pre-built ui to authenticate users on our google apps script web app
Sometimes with Google Apps Script web apps you need a way to authenticate the user whilst also publishing the web app to run under a specific account. Sourabh Choraria details how Firebase can be setup allowing you to authenticate users with their Google account.
send a follow-up email to all undecided participants of a meeting that you’ve scheduled via google calendar using apps script.
here’s a piece of code that you could schedule for every morning (preferably before your official work hours start) to be triggered, such that the script could iterate through every single meeting event that you’ve scheduled (i.e. where you’re the “organiser”) for the day and send an email to all those invitees who’ve neither accepted nor declined (even excluding the maybe’d ones too) to said invites.
Nice post from Sourabh Choraria which covers interacting and using data from your Google Calendar.
With everyone talking about omnichannel communication, @schoraria911 tells you how you create a smooth information flow between your helpdesk and phone system (@Exotel) to ensure a seamless customer experience
Always nice to see other companies promote the use of Google Apps Script with their service. In this post regular Pulse contributor Sourabh Choraria demonstrates how Apps Script can be used to configure the Exotel communications service.