Sorry for the late answer but the last days were specifically stressful and first had to think about your question a little bit more.
It sounds for me partly similar to how some authentications via OAuth work. Sadly nothing exists for that yet. Even though I think it is really important to support such authentication methods but sadly did not find time to work on it yet.
Is for example used by some trigger nodes to save webhook ids like here:
Anyway would not be the best thing to do as this data gets saved unencrypted with the workflow. As there is also no “destructor”, so there is also nothing that would delete it before it gets saved. Think currently there is no easy and clean way to do that. Something really has to get build for n8n first which adds support for that properly.
No problem! We all have many stuff to deal with!
Thanks for that detailed answer. For sure, oauth is a must have to help n8n growth.
For now, and that specific case, I’ll try to deal with it.
Perhaps as a first step, it would be fine to be able to set custom variables in the credentials object during the workflow. Theses custom variables would live only during its execution and get destroyed at the end (I don’t know if it’s technically feasible as I’m not yet confortable with all n8n concepts)