Expression use in Oauth2 generic Client credentials


I’ve stumbled upon unexpected (at least for me) n8n behavior.
I’m using latest and greatest [email protected] (additionally the situation is the same with [email protected])
I’ve created new generic Oauth2 credentials (Grant Type = Client Credentials) and want to use Expressions to provide some dynamic values.

Everything seems to be OK till I successfully run the workflow. After that the credential change to values that were used during the workflow run and the Expressions are gone :frowning:

The behavior is unexpected for me because with Header or Oauth2 credentials (Grant Type = Authorization Code) generic credentials this doesn’t happen

Is this a bug or a feature?

Hey @Rugia, this seems unexpected to me. I’ll add it to our backlog for a closer look by the product and engineering team, sorry for the trouble.

1 Like