-
Notifications
You must be signed in to change notification settings - Fork 37
Description
Description of the problem being solved
Related to #474 -- having the Workflow's User ID will allow custom function creators to invite the workflow into a channel so that the workflow can take subsequent actions on the call, like invite users. Right now, if the custom function is to create a channel (and that's it), then the standard workflow actions such as invite users will fail because the workflow is not in the channel.
The Workflow's Bot ID cannot be used to invite it into the channel, so it has to be the User ID which is only found by getting a workspace/Grid export making it un-scalable for reusable custom functions (different workflows, different User IDs).
Alternative solutions
Allow standard functions to use non-workflow tokens that are inherited from the acting user.
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.