Genesys Cloud - Developer Community!

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Double check that you have followed everything in steps 4 and 5.

https://help.mypurecloud.com/articles/configure-google-cloud-platform/

If that doesn't fix it for you, probably best to open a support ticket so we can dig into this issue.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

I checked Google documents on the V1 functions API, and did not see any indication that the API was deprecated. V2 Function look like they are only invokable via defined events. I don't know that those can be externally invoked at all. V1 is all we currently support.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Hi Gregory, thanks for support.
Regarding the Google documentation Cloud Functions V1 are still there - but you can't create new ones in new projects. So V1 is more or less useless and customers are highly adviced to migrate to V2.

See my links below.

Google Cloud Run Functions (V2) are much more powerfull and of course can be called from external. This works fine from Genesys (normal REST data action) if the Google Cloud Run Function is set to "public" access without IAM restriction. But setting this IAM access system active, the Genesys "Google Data Action" integration fails with its authentication method. It still works with Postman - but you can see, that the auth-process has changed.

So if Genesys doesn't support Google Cloud Run Functions V2 customers using GCF are stucked.... or I'm missing something?

Kind regards
Marcel

Here the links

No creation of V1 possible:

https://cloud.google.com/functions/1stgendocs/console-quickstart-1st-gen

https://cloud.google.com/run/docs/functions/comparison

I checked Google documents on the V1 functions API, and did not see any indication that the API was deprecated. V2 Function look like they are only invokable via defined events. I don't know that those can be externally invoked at all. V1 is all we currently support.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Hi Gregory, thanks for support.
Regarding the Google documentation Cloud Functions V1 are still there - but you can't create new ones in new projects. So V1 is more or less useless and customers are highly adviced to migrate to V2.

See my links below.

Google Cloud Run Functions (V2) are much more powerfull and of course can be called from external. This works fine from Genesys (normal REST data action) if the Google Cloud Run Function is set to "public" access without IAM restriction. But setting this IAM access system active, the Genesys "Google Data Action" integration fails with its authentication method. It still works with Postman - but you can see, that the auth-process has changed.

So if Genesys doesn't support Google Cloud Run Functions V2 customers using GCF are stucked.... or I'm missing something?

Kind regards
Marcel

Here the links

No creation of V1 possible:

https://cloud.google.com/functions/1stgendocs/console-quickstart-1st-gen

https://cloud.google.com/run/docs/functions/comparison

I checked Google documents on the V1 functions API, and did not see any indication that the API was deprecated. V2 Function look like they are only invokable via defined events. I don't know that those can be externally invoked at all. V1 is all we currently support.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Hi Marcel,

Thank you for the documentation that had the note about being supported only in existing projects. I was out on vacation when you posted. I am catching up with the rest of the team this week on where we stand with V2 support.

--Greg

Hi Gregory, thanks for support.
Regarding the Google documentation Cloud Functions V1 are still there - but you can't create new ones in new projects. So V1 is more or less useless and customers are highly adviced to migrate to V2.

See my links below.

Google Cloud Run Functions (V2) are much more powerfull and of course can be called from external. This works fine from Genesys (normal REST data action) if the Google Cloud Run Function is set to "public" access without IAM restriction. But setting this IAM access system active, the Genesys "Google Data Action" integration fails with its authentication method. It still works with Postman - but you can see, that the auth-process has changed.

So if Genesys doesn't support Google Cloud Run Functions V2 customers using GCF are stucked.... or I'm missing something?

Kind regards
Marcel

Here the links

No creation of V1 possible:

https://cloud.google.com/functions/1stgendocs/console-quickstart-1st-gen

https://cloud.google.com/run/docs/functions/comparison

I checked Google documents on the V1 functions API, and did not see any indication that the API was deprecated. V2 Function look like they are only invokable via defined events. I don't know that those can be externally invoked at all. V1 is all we currently support.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)): 

Hi - any update for V2 support?

Hi Marcel,

Thank you for the documentation that had the note about being supported only in existing projects. I was out on vacation when you posted. I am catching up with the rest of the team this week on where we stand with V2 support.

--Greg

Hi Gregory, thanks for support.
Regarding the Google documentation Cloud Functions V1 are still there - but you can't create new ones in new projects. So V1 is more or less useless and customers are highly adviced to migrate to V2.

See my links below.

Google Cloud Run Functions (V2) are much more powerfull and of course can be called from external. This works fine from Genesys (normal REST data action) if the Google Cloud Run Function is set to "public" access without IAM restriction. But setting this IAM access system active, the Genesys "Google Data Action" integration fails with its authentication method. It still works with Postman - but you can see, that the auth-process has changed.

So if Genesys doesn't support Google Cloud Run Functions V2 customers using GCF are stucked.... or I'm missing something?

Kind regards
Marcel

Here the links

No creation of V1 possible:

https://cloud.google.com/functions/1stgendocs/console-quickstart-1st-gen

https://cloud.google.com/run/docs/functions/comparison

I checked Google documents on the V1 functions API, and did not see any indication that the API was deprecated. V2 Function look like they are only invokable via defined events. I don't know that those can be externally invoked at all. V1 is all we currently support.

Hi,

we are using the integration "Google Data Actions" to execute Google Cloud Run Functions (the new V2) because all databases are at google.

But when we set the Google Cloud Function from "public" to IAM-controlled we get always a 401.

Credentials and Roles (Cloud Run Invoker) are not the problem - we tested the functions in Postman and used the correct data from the key.json file.

My feeling: The Genesys Google Data Actions integration has problems with the Auth and/or the new V2 functions (V1 are no longer available).

This cloud be in line with the only available documentation covering V1 functions (Google Cloud Functions - without Run  About the Google data actions integration - Genesys Cloud Resource Center

:-)):