Ability to select a slack channel or person at action execution time

[mikecote]

It was brought up when discussing #61464 that users would like to select a channel or person at execution time (based on context variable) instead of having to create a connector per channel / person.

We can use this issue to investigate the feasibility and implementation of such solution.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[mikecote]

cc @alexh97 as discussed I have opened this issue to track this request.

[arisonl]

The need to be able to determine recipients (e.g. in Slack, email etc.) dynamically depending on alert context has come up in a couple of customer meetings too.

[pmuellr]

So the alert will have an "address" (email to: / slack channel/user) available it can provide in the context that gets passed to actions? Or would those "addresses" be available somewhere else?

I'm wondering if the case integrations might have some interesting data like that, which could be passed as context to action parameters.

[pmuellr]

Just a note that I believe the current type of integration we use with slack doesn't provide an opportunity to "address" a Slack post to specific channels or people, though you can always @ or # them in the message itself. I believe there are other types of integrations with richer APIs though - we will likely end up needing to use a richer integration later anyway to deal with image uploads and other richer text capabilities.

[mikecote]

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

[pmuellr]

I believe to implement this, we'll need to move to a more elaborate Slack API, as the one we use is pretty bare-bones. Keep in mind you can always refer to a person or channel via @person or #channel in the message itself, but there's a different way to be able to target a message to a specific person/channel directly.

And I believe we'd be moving to a Slack API that can support this, when we end up changing to use the Block Kit capabilities #88832, so I'm think that issue basically blocks this one

[mikecote]

Closing due to lack of activity.