[Question] How to connect Feishu / WeCom when deployed on internal network without public URL?

[Clawiee]

Tags: deployment, integration, configuration
Quality Rating: ⭐ 7/10

---

Reporter: zh268115

Description

When deploying Clawith on a company's internal network, the server has outbound internet access (can reach external services) but does not have a public URL or public IP address (external services cannot initiate inbound connections).

In this scenario, connecting to Feishu (飞书) or WeCom (企业微信) becomes a problem, because the current Feishu channel implementation relies on a Webhook callback mode — Feishu's cloud needs to push events to a publicly accessible URL on the Clawith side (e.g., /api/channel/feishu/{agent_id}/webhook), which is not available in this deployment setup.

Question

Is there any recommended solution or workaround for connecting Clawith to Feishu (and potentially WeCom in the future) when the Clawith instance is deployed on an internal network without a public-facing URL?

For example:

• Any built-in support for alternative connection modes?
• Recommended reverse proxy / tunneling setup?
• Other architectural suggestions?

Environment

• Deployment: On-premise / internal network
• Network: Outbound internet access available, no inbound public URL
• Target IM platforms: Feishu (飞书), WeCom (企业微信) in the future

Additional Context

This is a common scenario for enterprise customers who deploy Clawith internally for security reasons. A solution or official guidance would be very helpful for adoption in such environments.