Salesforce Slack-Dev-201 Exam - Topic 2 Question 5 Discussion

An incoming webhook is a simple mechanism for sending messages from an external system into a predefined Slack destination. When an incoming webhook URL is created, Slack associates that URL with a specific user and a specific channel. Current documentation states explicitly that the generated URL is tied to one channel. The webhook therefore works particularly well when an external service has a straightforward requirement such as sending alerts, notifications, or status information into one predetermined channel. The integration makes an HTTP POST containing a JSON message payload to the webhook URL. Option A conflicts with the fundamental behavior of a single incoming webhook URL. To support multiple destinations, separate webhook URLs or more flexible Web API methods may be required. Option D is also incorrect because incoming webhooks intentionally provide less destination flexibility than methods such as chat.postMessage. Slack specifically notes that an incoming webhook cannot override its configured destination channel, username, or icon through the message payload. Consequently, C accurately represents the architectural reason for selecting an incoming webhook. This maps to Design Your Workflows: Spotlight on Slack's APIs, particularly choosing between webhooks and Web API messaging methods.