Is there a way I can avoid having to manually click “connect my account” after updating a credential ?
While the workflow automatically picks up the updated credential, the outlook node (in this example) won’t trigger due to the account having to be re-authenticated again (usually done by going to “credentials” and reconnecting manually as shown below).
I’d like to know if I can automate this confirmation process ?
Hi @Zak_G Welcome!
There is not very much you can do straight away as when you click Connect my Account it sends an HTTP request to your account and then the service like Microsoft or Google will actually ask you for permissions and approval, so most of the times you cannot automate it, but in some cases you can try using the HTTP node instead of native nodes with credentials predefined with generic auth, and then maybe you can achieve something closer to automating that.
I inspected the requests being sent when “Connect my account” is clicked, and the first one is a “patch” http request with the exact same params and body as the one in n8n api official docs, whether or not I click “continue” nothing is sent afterwards, the 2 “get” requests you see below are also triggered at the same time as the “patch” request, which again follows the same structure as n8n api docs.
I’ve tried your method of using an http request node with generic auth instead of a specific node w pre-defined creds, but I’m always prompted to confirm, otherwise it won’t work…
If I had to guess it’s prolly a “security feature” enforced by Microsoft, where it forces you to manually approve any new apps or whatever, which is stupid may I add, cause I already granted admin consent on all necessary permissions from the Azure portal and explicitly granted permissions to the app, so prompting individual users under the same tenant to manually confirm is just redundant, why bother with “admin” consent if you’re just gonna ask every user to confirm…so yeah, redundant Microsoft BS.
I’m frustrated af. nonetheless, thank you for the suggestion.
