in progress Create Google Meet and copy to clipboard

[davidwebca]

This workflow simply opens a URL to https://meet.google.com/new and waits for the URL to change and then copies it. It is the best way without workaround to open a new Google Meet that follows the redirect, copies into the clipboard and that being regardless of the preferred browser of the user, as long as that browser supports cmd + l to focus on the address bar and cmd + c to copy the then selected URL.

 

Github: https://github.com/davidwebca/alfred-create-google-meet

 

[vitor]

Thank you for the submission, but this relies on GUI automation which is error prone. All it would take would be for the browser to take a bit longer to come to the front or for the user to have remapped ⌘L and it suddenly breaks. Firefox is the only major browser which cannot get the current tab’s URL via AppleScript, so that should be the approach.

[davidwebca]

Thanks for your feedback. I’ve already looked into all of this and I wanted to include all and any browsers (even others than Safari, Chrome, Edge and Firefox). Nonetheless, there are different method calls to get the URL in AppleScript in all browsers anyway. 

The browser taking longer to come to the front shouldn’t be relevant, the Apple Script waits for the requested app to come to the front before continuing its execution. It then periodically checks for the URL to change until it’s done so it will resume executing regardless of the time it takes. 

The only other universal approach was to spin a puppeteer instance in node and fetch the https://meet.google.com/new URL to follow the redirect (impossible only with curl because it’s a client-side redirect *sigh*) but that alone requires a lot of power / ram and would make the process insanely laggy. 

[vitor]

13 minutes ago, davidwebca said:

there are different method calls to get the URL in AppleScript in all browsers anyway.

 

There’s only a difference between Webkit and Chromium browsers. There are Automation Tasks for that. Firefox doesn’t have proper AppleScript support.

 

13 minutes ago, davidwebca said:

but that alone requires a lot of power / ram and would make the process insanely laggy.

 

Yes, that would be far from ideal.

 

In the end, as it is it cannot go in because GUI automation is unreliable and this depends entirely on it. That would mean no Firefox support, though. It’s OK if you want to keep this approach; nothing changes regarding your ability to continue to share the workflow via GitHub, but it does mean it cannot go in the Gallery.

 

Edited June 23 by vitor