A server-side request forgery (SSRF) issue exists in the Slack, Discord, and Crawler workflow nodes. These nodes use an unguarded HTTP client to send requests to URLs provided in user-created credentials via the `webhook url` or `flaresolverr url` variables. This bypasses the existing SSRF egress guard used by other nodes. Because the credential API only verifies that the URL is not empty, a registered user can configure a credential to point to internal addresses. This allows the backend to access loopback, private, link-local, or cloud-metadata endpoints and return the complete response body in the node output, resulting in a non-blind SSRF.