N
@pedroknup Thanks - yes it does work now, just connected to a registry and send a test message :-) However, we switched to a webhook strategy for the prototype, as we had to get something off the ground. But nice to know that it is back up.
What is not comforting though, is that this API change was not implemented in pybytes before google changed it? Usually google warns me when they make breaking changes in their services (such as cloud functions). I expect that that it was "only" the API for setting up the connection that was changed, not any already running integrations - so no business consequences... But what about the future – may I let my client's business rely on the Pybytes-Google integration?
Again, thanks for fixing the issue at hand and following up.