Google chat get messages in space

Help me Build my Workflow
, , ,
1

Hey there, I am struggling a lot with simple things in n8n. I managed to setup google credentials via service account and could get available spaces. As the google chat node is missing a method for getting messages in a space, I wanted to call the API directly using HTTP Request node in conjunction with google chat node custom operation. I did hit the toggle to allow the credentials to be used for http requests. Once I did that, n8n complains about secretOrPrivateKey must be an asymmetric key when using RS256. Without the toggle at least getting the space works.
Can someone please assist setting this up to let me call the api?
Btw, saving google credentials always stuck at the testing stage because of an exception Cannot read properties of undefined (reading 'googleApiCredentialTest'). Seem to be a bug in the latest docker image.
Btw2, without toggling the permission to use the credential for http requests I receive an error from the google api Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.

It drives me crazy that all my plans to use n8n stuck at the integration of 3rdParty :frowning:

Please someone help me out^^

2

Hey @thomas.s

Sorry to hear that you face that much problem in just getting the messages in the space…

As you mentioned that you are able to authenticate yourself using service account…

I would say simple use this node and you’ll able to get all the messages in a space

and you can do all this directly using google chat node…

If you further still face any problem you can go through this tutorial.

3

Funny how easy a workaround can be. Thank you very much for sharing.
In meanwhile I implemented a custom node but this one is way simpler^^

Thanks a lot

1 Like
4

Hey @thomas.s, I’m so happy it worked for you!

Yup, it’s simpler than your setup, but I remember how much time it took me to figure out the same thing… hahaha.

Since you’ve found your solution, I’d appreciate it if you could take a moment and mark the post as the solution…this will help others who might be trying to solve the same problem in the future. :->

Happy flowgramming, my friend!

1 Like
5

FYI: A restriction is the endpoint is paginated, the very simple solution does not support this. It also doesn’t support sorting. So very large threads >100 messages will not be complete. Still a nice and simple solution.

In regards to marking as solved, I don’t see the option yet, likely due to me being new in this forum.