Currently, all 3rd party integrations rely on static credentials:
However, many integrations require standard OAuth 2.0 flows. This limitation makes it challenging to integrate the following examples:
Also generic actions like the HTTP Request step are similarly limited, requiring hardcoded credentials.
To solve these limitations, we might need to introduce a Credentials Vault concept to abstract this complexity (handling the token lifecycle and storage) away from individual workflow steps and allow credentials to be reused across integrations.
Currently, all 3rd party integrations rely on static credentials:
However, many integrations require standard OAuth 2.0 flows. This limitation makes it challenging to integrate the following examples:
client_idandclient_secretto get an access token.Also generic actions like the
HTTP Requeststep are similarly limited, requiring hardcoded credentials.To solve these limitations, we might need to introduce a Credentials Vault concept to abstract this complexity (handling the token lifecycle and storage) away from individual workflow steps and allow credentials to be reused across integrations.