[QUERY] Workflow triggered from a canvas is asking to select channel. How can I avoid this?

[djmgit]

Question

We use a list of several slack workflow automation from slack channel and slack channel canvas. The channel id from which these workflows are triggered is something which we always need. Till now the channel id of the channel from which the workflow was being triggered would be available via ```Schema.slack.types.channel_id`` which is propagated to workflow as an input from trigger. Recently what I am seeing is, on triggering a workflow a modal appears where the user has to again chose the channel name. This is totally redundant and its slowing users down. We use these workflows for extremely time critical use cases, this sudden random redundant step is a total bummer for us. Is there an option by which I can make the workflow use the id of the channel from which it was triggered? This is a very critical issue for our organization.

Environment

"deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.15.0/",
"deno-slack-api/": "https://deno.land/x/deno_slack_api@2.8.0/"

deno 1.44.4 (release, aarch64-apple-darwin)
v8 12.6.228.9
typescript 5.4.5

ProductName: macOS
ProductVersion: 15.3.2
BuildVersion: 24D81
Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6020

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.

[djmgit]

Hi, it would be really helpful if someone from Slack could take a look at it 😅
cc: @filmaj

[filmaj]

I'm no longer at Slack, sorry

[djmgit]

I believe its a bug in Canvas. When I post the same link as message in the channel and trigger it, it does not ask for channel. But it asks for channel when triggered from canvas.

[zimeg]

👋 Hi @djmgit - I apologize for a slower than ideal response here but I think you're finding the root cause that canvases might not have an associated channel ID.

For my own understanding, are these standalone canvases or tabbed as part of a specific channel?

[djmgit]

@zimeg these canvas are created via the conversation_canvas_create API. Workflows on canvas worked even a week back the day I posted this issue. It never asked for channel explicitly.

Anyways we are moving away from canvas. We really had big plans with canvas but it has been a huge pain. Workflows do not render properly on canvas. No support for layout. Random design changes from slack, earlier it was a left pane, then it came to top navbar with canvas label, now its just an icon which is difficult to find. I dont think Slack has any near plans to fix canvas issues and it feels canvas is Slack's bottom most priority right now.