Trade a Gmail sign-in code for its tokens

Trade the code Google's sign-in page handed back for the connection's access and refresh tokens, kept sealed in the vault

One token request to Google (the google-account descriptor's acquire.token_url, client_auth form, PKCE): the code, the callback address and the PKCE verifier go in a form body with the Google sign-in app's id and secret, placed from the vault only as the request leaves. The reply's access_token, refresh_token and id_token are kept in the vault as the new connection's own fields (reply_holds_values) before the reply is read, so no token is ever in a run's answer or journal; a field already held is never replaced and then nothing is sent. Run by tool:connect-an-account-by-signing-in-to-the-service at the sign-in callback.

What it asks for

Nothing: your AI starts it with your words.

Use it from your AI

Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this tool by what it does and runs it.

Say to your AI: “Use Trillion to trade the code Google's sign-in page handed back for the connection's access and refresh tokens, kept sealed in the vault”