Skip to main content Skip to complementary content

Slack

The Slack connector in Qlik Application Automation can be used to create channels, send messages to Slack channels and invite users to channels. You can use the connector to perform alerting in Slack based on actions occurring in Qlik Cloud, such as Slack integration with task chains.

Qlik Cloud Government noteNot supported in Qlik Cloud Government.

Connecting Slack to Qlik Application Automation

Connectors in Qlik Application Automation can be authenticated from the Connections page and from the Connection tab of a block that you add to the canvas. For more information, see Authenticating connectors.

To add Qlik Application Automation to Slack, click the Add to Slack button on the Qlik Application Automation page on Slack Marketplace.

Deleting the connection

To delete your connection, go to the Connections tab, select the Slack connection you wan to delete and click on the More menu and click delete.

You can also delete the connection from within the automation that uses it. Open the automation, select a Slack block and click on the Connection tab. Select the relevant connection and click delete.

To delete connections, you need to be the creator of the connection, or have role that gives you sufficient permissions to do so.

Unlinking the connection

To unlink the connection, open the Qlik Application Automation configuration page on Slack, scroll down to the bottom of the page, and click on Remove app.

Settings menu

Unliking connection to Qlik Application Automation on Slack Marketplace

Available blocks

You can use the following blocks to automate workflows:

  • Archive channel

  • Create channel

  • Get user by email

  • Get user by ID

  • Get user by presence

  • Invite users to channel

  • List all users

  • List channels

  • Send binary file

  • Send ephemeral message

  • Send message

  • Send message with attachment

  • Send message with blocks

  • Send text-based file

  • Upload file to channel

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!