member badge
Bhaskin Janvier Hizon
Customers with strict firewall and allowlist requirements need ClickUp webhook traffic to come from a dedicated or customer-specific static outbound IP, or a stable reserved IP range.
Today, ClickUp can provide the current source IPs for a workspace environment, but those IPs are not dedicated or reserved for a single customer. For some enterprise security teams, that does not meet their requirement.
This request is for ClickUp webhook delivery to support:
  • A dedicated or customer-specific static outbound IP, or a stable reserved IP range network-level allowlisting of ClickUp webhook traffic signature verification as an additional security layer
Business impact:
  • This blocks customers with strict security requirements from approving webhook-based integrations.
Customer example:
  • Rhyme needs to restrict inbound webhook traffic using static IP allowlisting and use signature verification as a second layer, but the current shared workspace source IPs may not satisfy their security review.