Cloud routines cannot access graph.facebook.com (Meta Ads API blocked by egress proxy)
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Problem
Cloud-based routines (scheduled runs on claude.ai/code) cannot reach
graph.facebook.com. The egress proxy returns 403 Forbidden on CONNECT,
blocking all Meta Graph API calls.
Environment
- Claude Code Web (cloud routine, not local CLI)
- Routine type: Daily scheduled
- Proxy error: "gateway answered 403 to CONNECT (policy denial)"
Use case
Daily Meta Ads reporting automation that calls:
https://graph.facebook.com/v21.0/{campaign_id}/insights
Expected behavior
Cloud routines should be able to reach graph.facebook.com, or users
should have a way to add domains to the egress allowlist.
Workaround
None available within the current UI. Running manually or locally only.
Proposed Solution
Cloud routines should be able to reach external APIs like graph.facebook.com.
Ideal experience:
- Users should have a way to add trusted domains to the egress allowlist
for their cloud routines (e.g., in routine settings or environment config)
- OR graph.facebook.com (Meta Graph API) should be included in the default
allowlist, since Meta Ads automation is a very common use case
Currently there is no workaround available in the UI — routines silently
"complete" but all API calls fail, making scheduled automation useless for
any Meta Ads reporting workflow.
Alternative Solutions
_No response_
Priority
Critical - Blocking my work
Feature Category
Configuration and settings
Use Case Example
Daily Meta Ads reporting routine scheduled at 9:00 BRT. The routine calls
graph.facebook.com/v21.0/{campaign_id}/insights to fetch ad performance data.
All calls fail silently with proxy 403, and the routine marks itself as
"Concluído" even though no data was retrieved.
Additional Context
_No response_