Qlik Automate: Send Message To Slack Channel as an action

[AfeefaTk]

This article walks through Send Message To Slack Channel as an action, a Qlik Automate template that is now available in the template gallery.

This template is a good starting point if you want to:

• Trigger a Slack notification directly from the Qlik Answers Assistant, an agent built on Qlik MCP, or a button on a sheet in Qlik Sense application, without writing any custom integration code.
• Accept just a channel name and a message at runtime, instead of hardcoding values inside the automation.
• Automatically resolve a channel name into the channel ID that Slack's API actually requires, for both public and private channels.
• Get back a clear, human-readable success or failure result, including Slack's own error details when something goes wrong.
• Reuse the same pattern as a base for sending action-driven alerts through other communication platforms, like email or Microsoft Teams

The template is available in the template picker. Go to Add new > New automation > Search templates, search for Send Message To Slack Channel as an action, and select Use template.

You will find a version of this automation attached to this article: "Send-Message-To Slack-Channel-as-an-action.json".

Content

• What this template does
• Before you start
• Step-by-step walkthrough
• Step 1: Start and Inputs
• Step 2: Slack - List Channels
• Step 3: Condition – Did List Channels fail?
• Step 4: Filter the list and set slackChannelId
• Step 5: Condition 2 - Was a matching channel found?
• Step 6: Slack - Send Message
• Step 7: Condition 3 – Was the message sent successfully?
• Why the run titles matter
• Customization ideas
• Tips for new users
• Troubleshooting
• Summary

What this template does

When this automation is called as an action, it does the following:

1. Collects a target Slack channel and a message through an Input block.
2. Pulls the full list of channels the connected Slack app can see, both public and private.
3. Looks up the channel ID that matches the channel name you provided.
4. Sends the message to that channel if a match was found.
5. Reports back a clear success or failure result and updates the run title so the outcome is visible at a glance in the automation run history.

Before you start

Before using this template, make sure you have:

• A Qlik Cloud tenant with permission to create and run automations.
• A Slack connection already configured and authenticated in your tenant.
• The exact channel name you want to send messages to, with the leading # optional

Step-by-step walkthrough

Step 1: Start and Inputs

This is the entry point of the automation.

How it works:

The Start block is set to manual run mode, but in practice, this automation is meant to be invoked as an action rather than run on a schedule. The Inputs block immediately following the Start block defines the two values every caller must provide:

• Slack message (textarea, required): the body of the message to send
• Slack channel (text, required): the channel to send it to

These two fields are effectively the contract for this automation. Whatever calls the automation (Qlik Answers Assistant, a Qlik MCP tool call, or a button on a Qlik Sense Application Sheet) has to supply both.

What you need to configure:

Nothing to get started. You can edit the field labels or help text, but keep both fields required since every later block depends on them.

Step 2: Slack - List Channels

How it works:

This block calls Slack's API to retrieve every public and private channel visible to your connection. It's needed because Slack's Send Message endpoint expects a channel ID, not a channel name; this block is the lookup table that makes that translation possible later in the flow.

What you need to configure:

• Connection: Make sure this block is connected to your Slack connection.
• Everything else is pre-set (the block already pulls both public_channel and private_channel types).

Step 3: Condition – Did List Channels fail?

How it works:

This condition checks whether the previous block returned an API error (an error response body or status).

Yes branch (List Channels failed):

The automation shows Slack's raw error response using an Output block and updates the run title to 'List Channels block failed with an error message' using an Update Run Title block.

No branch (List Channels succeeded):

The automation continues to the filter step to look up the channel.

What you need to configure:

Nothing. This condition is pre-built error handling.

Step 4: Filter the list and set slackChannelId

How it works:

This block filters the full channel list down to whichever entry's name exactly matches the channel name you provided, after stripping off a leading # (if you included one). The matching item (there should be at most one, since channel names are unique) is looped through, and its ID is written into a variable called slackChannelId. If nothing matches, slackChannelId stays empty, since it was initialized that way at the start of the run.

What you need to configure:

Nothing. This step runs automatically based on your "Slack channel" input.

Step 5: Condition 2 - Was a matching channel found?

How it works:

This condition checks whether slackChannelId ended up empty.

Yes branch (channel found):

The automation moves on to send the message.

No branch (channel not found):

The automation shows I can't find this channel... Please try again using an Output block, updates the run title with the same message using the Update Run Title block, and then ends without sending anything.

What you need to configure:

Nothing. This condition is pre-built.

Step 6: Slack - Send Message

How it works:

This block posts your message to the channel ID resolved in Step 4, using the text from the Slack message input. The message is sent with the display name Qlik Automate as a tool, so anyone reading it in Slack can tell at a glance it came from this automation rather than a person. A few optional Slack parameters in this block, like an icon or thread reply, are left blank by default and can be filled in for richer messages.

What you need to configure:

• Connection: Make sure this block is connected to your Slack connection.
• Everything else is wired automatically from earlier steps.

Step 7: Condition 3 – Was the message sent successfully?

How it works:

This condition checks the ok flag Slack returns from the Send Message endpoint.

Yes branch:

The automation shows 'Message was sent successfully ' and updates the run title to match.

No branch:

The automation shows Slack's raw error response body using an Output block and updates the run title to Send Message block failed with an error message using Update Run Title block, so you can see exactly why Slack rejected it.

What you need to configure:

Nothing. This condition is pre-built.

Why the run titles matter

Every outcome in this automation (a failed channel lookup, a channel that couldn't be found, a successful message send, or a failure) updates the automation run title to match. That means you can scan the automation's run history and immediately tell what happened in each run without opening a single run history, which is especially useful once this automation is being called repeatedly by an Assistant, MCP tool, or button rather than run by hand.

Customization ideas

You can adapt this automation to fit your own needs:

• Swap the destination: route notifications to a different destination platform, such as email, Microsoft Teams, or any other supported messaging connector instead of Slack. Depending on the connector you choose, you may need to adjust the Input block to provide the required parameters.
• Add more inputs: extend the Inputs form with fields like a thread reply ID, an emoji icon, etc., and then map them into the Send Message block's optional parameters.
• Simplify for a single channel: if this automation will only ever post to one channel, you can hardcode the channel ID and remove the Slack channel input text from the Input block / List Channels / Filter / Condition 2 branch entirely for a faster, simpler version.
• Add a fallback channel: instead of stopping when a channel can't be found, route the "Condition 2: No" branch to a default channel ID so the message always lands somewhere.

Tips for new users

• Test the automation with a channel name you know exists before wiring it up to a button, the Qlik Answers assistant, or an MCP tool.
• For List Channels and Send Message block to work, double-check that the Qlik's Slack app behind your connection has actually been invited to the channel; otherwise, it won't appear in the List Channels result, and you'll get the "can't find this channel" message even though the channel exists.
• Type only the channel name (for example, general); the leading # is optional and is removed automatically.
• Check the run history first. The run title alone tells you whether the channel was found, the message sent, or something failed; no need to open the output every time.

Troubleshooting

The automation fails with the following error messages:

"I can't find this channel... Please try again":

• Check the channel name for typos.
• Confirm Qlik's Slack app behind your connection has been added to the channel.

"List Channels block failed with an error message":

• This is most likely a connection issue; re-check or re-authenticate your Slack connection.
• The output shows a detailed error response from Slack. 

"Send Message block failed with an error message":

• The output shows a detailed error response from Slack.

Summary

This template gives you a ready-to-call building block for posting Slack messages as an action from anywhere in Qlik, the Qlik Answers Assistant, a Qlik MCP-connected agent, or a simple button on a Qlik Sense Application. By resolving channel names to IDs automatically and reporting a clear success or failure result at every step, it keeps the calling side simple: pass in a channel and a message, and get an outcome back. You can adapt it by changing the destination platform or swapping Slack out for email, Microsoft Teams, or adding richer message options.