This article is originally published at https://www.tidyverse.org/blog/
You can install it from CRAN with:
The main goal of version 2.0.0 is to improve the ergonomics around auth. There is less need for fussy code around configuring an OAuth client and it’s easier to use gmailr in a non-interactive or deployed setting. There is also a major advance in the process of replacing legacy functions with versions that have a
gm_ prefix. The legacy functions still exist, but are now hard deprecated. Finally, gmailr no longer re-exports
%>%, the magrittr pipe, now that we have
|> in base R.
You can see a full list of changes in the release notes.
😬 Ouch! These name collisions are exactly why gmailr added a universal
gm_ prefix to all of its functions starting in v1.0.0. One day in the not-too-distant future we can remove the troublesome legacy functions.
The Gmail API is more challenging to wrap, in terms of auth, than the APIs for Sheets, Drive, or BigQuery. That’s because the scopes (think: “permissions”) needed for the Gmail API are regarded as extremely sensitive, as well they should be. If a bad actor gains the ability to read and send email as you, that is considerably more damaging than them being able to modify your spreadsheets (which is also bad, to be sure, but considerably less bad). Email is particularly important, because most other services allow you to reset your password via email; if someone gets access to your email, they can quickly use that to access every other service you have a log in for.
The heightened security around the Gmail API means that a wrapper package like gmailr can’t make auth “just work” as easily we can in other packages, such as googledrive. In particular, R users who want to use gmailr absolutely must provide their own OAuth client. In other packages, we can make this optional.
gmailr v2.0.0 includes new features and documentation to reduce the pain around the OAuth client as much as possible:
Set up an OAuth client is a new article with detailed instructions for creating and configuring an OAuth client. You might even say this provides an excruciating level of detail, but this process has proven to be tricky for many users.
There is now a default location for the JSON file that represents the OAuth client. It’s the location returned by
rappdirs::user_data_dir("gmailr"). If you put the JSON file there, gmailr will find it automagically.
rappdirs::user_data_dir("gmailr") |> list.files() #>  "client_secret_xxx-yyy.apps.googleusercontent.com.json" gm_default_oauth_client() #>  "/Users/jenny/Library/Application Support/gmailr/client_secret_xxx-yyy.apps.googleusercontent.com.json"
gm_default_oauth_client()is the new function that implements this new feature as well as pre-existing support for providing this path via an environment variable.
> library(gmailr) > > # 😲 OMG no more need to call gm_auth_configure() here! 🎉 > > gm_threads() The gmailr package is requesting access to your Google account. Enter '1' to start a new auth process or select a pre-authorized account. 1: Send me to the browser for a new auth process. 2: [email protected] Selection: 2
Conversely, if you happen to be providing an explicit user or service account token,
gm_auth(path =, subject =)1 no longer error if the OAuth client is not configured.
The Gmail API is primarily intended for use on behalf of a regular Google user account. The gmailr package is designed to guide an interactive R user through a process in which they authenticate themselves to Google and authorize Gmail activities initiated from R. This is sometimes referred to as the “OAuth dance”.2
But what about settings where there is no interactive user sitting around to do this dance, i.e. when gmailr-using code is deployed to a remote server or otherwise runs unattended? For most Google APIs, the standard advice is “use a service account”. But the Gmail API is special. To use a service account with the Gmail API basically requires that the service account has been delegated domain-wide authority. This is tricky for at least two reasons. First, this is only possible within a Google Workspace, i.e. it’s not available to personal Google accounts. Second, most Google Workspace admins will refuse to do this, for security reasons.
Therefore, if you want to deploy a data product that uses gmailr, it’s extremely likely that you really do need to use a user token. This workflow has gotten dramatically easier in gmailr v2.0.0:
- Deploy a token is a new article describing how to capture a token interactively, then use it later, non-interactively.
gm_token_read()is a new matched pair of functions that facilitate writing an obfuscated token to disk then reloading that token in a deployed data product or in CI.
- gmailr ships with
example code that uses this technique in a small Shiny app that sends email from a specific user account. See the contents of
system.file("deployed-token-demo", package = "gmailr").
The heart of this approach is to first capture a token in an interactive session:
gm_auth("[email protected]", cache = FALSE) # interactive OAuth dance in the browser happens HERE gm_token_write( path = ".secrets/gmailr-token.rds", key = "SUPER_SECRET_ENCRYPTION_KEY" )
then reload it in a subsequent non-interactive session:
Unfortunately, there is considerable overlap between some obvious function names in an email-related package (e.g. “body”, “date”, “message”) and pre-existing functions in base R (e.g.
message()). From very early on, gmailr exported several functions with regrettable name collisions, as evidenced at the beginning of this post when we called
In version 1.0.0 (released 2019-08-30), the process of addressing this problem kicked off. At that time, gmailr adopted a universal
gm_ prefix for its functions and soft deprecated the legacy functions. Here’s an indicative sample of the function replacements:
In version 2.0.0, the legacy functions are hard deprecated and you should expect them to be removed in the next release of gmailr. I don’t expect there to be much (any?) surviving usage of these functions, but it’s definitely time to eliminate any remaining usage.
gmailr is designed to be very pipe friendly and it leads to very natural code that builds up a message from its parts:
msg <- gm_mime() |> gm_to("[email protected]") |> gm_from("[email protected]") |> gm_subject("Hello, world!") |> gm_text_body("I come in peace.")
gmailr predates the introduction of the native pipe, in R 4.1, and therefore, historically, it has re-exported
%>%, the magrittr pipe, for user convenience. The magrittr pipe also featured heavily in gmailr’s documentation.
In the v2.0.0 release, I’ve removed the magrittr dependency and now use the native pipe operator
|> in all documentation (gmailr never used the pipe internally). The purrr package pioneered this maneuver, within the tidyverse, and gmailr uses the same techniques to resolve the tension between the new usage of the base pipe and the tidyverse policy of supporting older R versions. You can learn more about the pipe transition in the blog post
Differences between the base R and magrittr pipes.
A big thank you to all those who have contributed to gmailr since the v1.0.0 release:
@absuag, @aeburger, @andresxmv, @batpigandme, @beib, @careercoachme, @chuagh74, @cstangor, @EeethB, @enricodata, @FJCC, @hadley, @HadyShaaban, @ismayc, @j450h1, @janebunr, @jcheng5, @JeffreyCHoover, @jennybc, @jimhester, @jonmichael-caldwell, @jreid88, @Karlheinzniebuhr, @kputschko, @KryeKuzhinieri, @laurenmarietta, @lwjohnst86, @maelle, @majazaloznik, @maticabgd, @MCOtto, @meheszlev, @Mr-Hadoop-Hotshot, @Niekuba, @norcalbiostat, @Patrikios, @pschloss, @pythiantech, @randy3k, @ratnexa, @sanjmeh, @sdisav, @sommerhd-royals, @statnmap, @tariuk, @tvroylandt, @vinaybugz, and @VincentGuyader.
The full OAuth dance is not necessary in subsequent R sessions, though, by default gmailr is very conservative and asks for permission to use and refresh an existing token. This is, of course, configurable. ↩︎
Please visit source website for post related comments.