I have set up an automation which is triggered from a webhook.
depending on the content of the request it will process different datasets. These different datasets may, in some cases, require the use of a web connection. I thought I’d be able to control the access via the token, however, it seems that the user who triggered the automation is not the one running the workspace and therefore has no bearing over access to a given connection.
Any ideas on how I can make it so the token controls the access?
I was thinking about instead using a workspace before the automation to list the available connections for that user and then pass that along to the automation.
Page 1 / 1
OK well I’ve figured out that you can get the headers of a request within the automation. So I am able to use the token from the header and fetch the list of connections that token has access to using the rest api. I will just pass that list along to the job and make sure that I can only use connections from the allowed list
Matt, this is a brilliant way to leverage Flow’s REST API - thank you for sharing your solution with the rest of us!