Definitely doable, but not exactly quick and easy. You do it by doing all the token management on your own, rather than using the social login.
I actually just wrote up detailed instructions to handle the google oauth flow, over here: Google Calendar API use case
Rather than storing tokens in fields directly on the user table, you could just create a new data type with various fields and add a list of those to the user type.