Generate slack incoming webhook URL

To post a slack notification, that you need to generate an incoming webhook URL. To generate the URL, follow these steps: Incoming webhooks for Slack.

Configuring a slack destination

Before you configure Slack as a destination for Direct Messages, ensure you have created and configured a Slack app with a bot token scope of chat:write. Refer to the Slack API documentation for more information: (https://api.slack.com/quickstart#creating).

To configure a Slack destination, complete the following steps:

1. click Destinations in the Event Notifications instance.

2. Click Create to add a new destination.

3. Enter the following destination details in the Create destination dialog:

   • Name: Enter a name for your destination.
   • Description: Optionally, enter a description for your destination.
   • Type: Under Destination, select Slack from the list as your destination type.
   • Send messages: Choose one of the following options:
     • Using incoming webhooks: Provide the Slack Incoming Webhook URL.
     • Using direct messages: Provide the Bot User OAuth Token.

4. Click Create destination.

Configuring a slack subscription

To configure a slack subscription:

1. Using Incoming Webhooks
   • You can add an attachment color to individual Slack subscriptions based on a hex code. For example, use #0000FF to set the color to blue.
2. Using Direct Messages
   • You can provide a list of member IDs and channel IDs. If channel IDs are provided, the application is integrated into the specified channels.

How a default slack notification (without template) from Event Notifications looks

Event Notifications generates Slack notifications from the incoming payload. The template that Event Notifications uses to send to Slack looks like the following example:

{
  "blocks": [
    {
      "type": "rich_text",
      "elements": [
        {
          "type": "rich_text_section",
          "elements": [
            {
              "type": "text",
              "text": "{{ibmendefaultshort}}",
              "style": {
                "bold": true
              }
            }
          ]
        }
      ]
    },
    {
      "type": "section",
      "text": {
        "type": "plain_text",
        "text": "{{ibmendefaultlong}}",
        "emoji": true
      }
    },
    {
      "type": "divider"
    },
    {
      "type": "context",
      "elements": [
        {
          "type": "mrkdwn",
          "text": "```{{event_payload}}```"
        }
      ]
    }
    ]
}

Where:

• ibmendefaultshort is the default short payload that is provided in the incoming payload.
• ibmendefaultlong is the default long payload that is provided in the incoming payload.
• data is the data JSON provided in the incoming payload and formatted as JSON in the Slack notification.

For more information on how to create and use Slack notification templates, see Slack notification templates.

Testing a Slack destination configuration

You can test a Slack destination in the options menu next to the destination. You can test whether the provided configuration is correct with a single click.

For more information on testing a destination, see Testing Destinations.

Slack retry policy

When publishing a Slack notification, issues such as network errors and application glitches can cause the requests to fail. Event Notifications automatically retries failed requests to provide resiliency.

For detailed information about retry behavior, including retry attempts, delays, and timeout values, see Retry policy for destinations.