-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[QUERY] Ability to use built-in Lists workflow steps #329
Comments
Hi @mcsescott - Yes, confirming that we do plan to add support for built-in Slack workflow steps to be able to be used in coded workflows. |
@srajiang is there any ETA on Slack Lists support in workflows? |
Update here: I am working on getting these released! I am hitting some errors testing them in coded workflows, so I just want to make sure they work properly before releasing. Unless I hit an unexpected pitfall, these will be available in the upcoming deno-sdk release - soon! |
Another update here: this has proved more challenging than expected. There are some workflow-builder assumptions built into these steps that will take more effort to tackle and make them generic enough for use in code. Plus, the steps don't seem very developer-centric as is: there is no 'create list' step, for example. Will revisit in the future. Apologies for this. If you have strong feelings about the need for these steps in code, please let your voice be heard by emailing [email protected] and submitting that as a feature request. |
Thanks. I’ve found some workarounds for the things I am attempting to do. Keep up the good fight! |
With the recent GA release of Slack Lists (yay!), I'd like to build some custom functions with Lists.
I do know that it will take a while for true Lists API methods to be released, but are there abilities for this Deno SDK to use the built-in Slack workflow steps (Add to List, Update a List, etc.) when building a coded workflow? I did a quick search in the code and didn't immediately see anything.
The text was updated successfully, but these errors were encountered: