Deprecated: Return type of I::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 62

Deprecated: Return type of I::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 91

Deprecated: Return type of I::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 71

Deprecated: Return type of I::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 101

Deprecated: Return type of I::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/i.php on line 53

Deprecated: Return type of Collection::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/public/kirby/toolkit/lib/collection.php on line 80

Deprecated: parse_str(): Passing null to parameter #1 ($string) of type string is deprecated in /home/public/kirby/toolkit/lib/url.php on line 135
One Tap Less | Gmail and x-callback-url

Gmail and x-callback-url

Google is known for not having a good documentation when it comes to x-callback-url. Fiddling to update the library, I found an example of x-callback-url support for Google Maps in a Chinese blog. It worked and I could test a few more terms to introduce you to its x-callback-url parameters. Noticing a pattern on Google apps, I decided to investigate for Gmail's support on our dear protocol. I found it.

I still remember when Tom Scogland found the url scheme for Gmail. I used to keep my email accounts there back in the day and despite my aversion to Google and most of its products, it is undeniable that Gmail is an outstanding effort in the email world.

The url scheme for Gmail reported by Tom is as follows:

 googlegmail:///co?subject=<subject text>&body=<body text>

There are a few other parameters you can use beyond subject and body, such as to, cc and bcc to define your receivers. To use x-callback-url with Gmail you must change the parameters slightly. This is how it looks:

googlegmail-x-callback://x-callback-url/co?subject=<subject text>&body=<body text>&to=<receiver email>&x-success=<encoded callback action>

Yep. Just like we changed the Google Maps. This is how a Launch Center Pro action would look like:

googlegmail-x-callback://x-callback-url/co?subject=[prompt:Subject]&body=[prompt-return:Body]&to=[prompt-list::To]&x-success={{launchpro://}}

You can install this action here. Call this action on LCP, provide the prompts and launch, you'll be taken to Gmail's compose window with the fields correctly filled out. After you send the email you'll be taken back to Launch Center Pro.

I don't use Gmail anymore, maybe you neither, but there's always someone close to us using the service and I hope this helps you drag them into this rabbit hole of automation.