Make it possible to store and pass user identity to third-party services
In scenarios where the workflow is a long-running process, initially triggered by user interaction but running without a current logged-in user, make it possible to cache and forward user auth tokens so that operations can be carried out using the user's identity.
For example, in a service in which a user uploads a text file which is then transformed into a PDF and stored in a DropBox account, make it possible to store the output PDF in the user's personal DropBox by authenticating as that user (without taking their DropBox user name or password from them - having them sign in when they trigger the workflow).
Great suggestion, thanks for reaching out. We’ll consider this in due course.