Is it turned on, indeed.
The main fact is that if I will curl -v Customize your workspace | Slack (this is not the actual webhook) I will get:
< HTTP/1.1 400 Bad Request
< date: Tue, 21 Mar 2023 20:38:07 GMT
< server: Apache
< x-powered-by: HHVM/4.153.1
< x-frame-options: SAMEORIGIN
< access-control-allow-origin: *
< referrer-policy: no-referrer
< x-slack-backend: r
< x-slack-unique-id: ZBoVr99uM2AkHMR8Xp7QkwAAADk
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< vary: Accept-Encoding
< content-type: text/html
< x-envoy-upstream-service-time: 105
< x-backend: main_normal main_canary_with_overflow main_control_with_overflow
< x-server: slack-www-hhvm-main-iad-yfnp
< x-slack-shared-secret-outcome: no-match
< via: envoy-www-iad-wlub, envoy-edge-fra-wqnb
< x-edge-backend: envoy-www
< x-slack-edge-shared-secret-outcome: no-match
< transfer-encoding: chunked
<
- Connection #0 to host hooks.slack.com left intact
invalid_payload