Calling GCP Cloud Function using GCP Function and HTTP Trigger


My 2nd Gen GCP Cloud Function has a url, not a url…
I am unable to configure the node since it insists on a url.

Is there a known workaround for this?
I have tried to build the equivalent url for the function based on the pattern of the url (using region, project-id and function name) but it finds no endpoint.


I just tested this and verified the issue you are running into. We’re working on a fix and should hopefully have it out next week. Thanks for bringing this to our attention.

In the meantime, you could use an HTTP Node to invoke the function.

1 Like

Thanks Dylan.
Appreciate greatly the confirmation and response.

It’s the Token key in JSON format security functionality I was really wanting from the GCP Function Node…
That has been very solid approach for use with BigQuery calls.

I have been able to get the HTTP node to fire using “Authorization : bearer XXXX…” header arguments, using a token copied from a gcloud console… but - as I understand it - that is not good practice and those tokens are temporary.

(I am definitely no expert on authorisation… and it’s been a steep learning curve in GCP with different mechanism in different circumstances etc…).


Thankyou, Dylan… this now works!