claude-code - 💡(How to fix) Fix Allow CCR scheduled agents to reach third-party APIs (api.sproutsocial.com) [1 comments, 2 participants]

Scheduled remote agents (CCR) cannot make outbound network connections to third-party APIs. When a trigger fires, the sandbox blocks all requests to external hosts — in this case, api.sproutsocial.com. The agent runs, fails silently or posts an error to Slack, and no data is retrieved. This makes scheduled triggers non-functional for any workflow that depends on external API data.

TL;DR

Adding api.sproutsocial.com to the CCR network allowlist is likely the most straightforward fix to enable scheduled remote agents to make outbound connections to this specific third-party API.

Guidance

• Identify the current network allowlist configuration for CCR to understand how external connections are managed.
• Determine if there's an existing mechanism to add domains to the allowlist, either globally or at the trigger/environment level.
• Consider implementing a configurable setting to allow users to specify trusted external domains when creating a trigger, enhancing security and flexibility.
• Evaluate the feasibility of integrating a feature similar to MCP connectors for managing external API connections.

Example

No specific code example can be provided without more details on the CCR's configuration and implementation.

Notes

The proposed solution assumes that the issue is solely due to the absence of api.sproutsocial.com from the allowlist. Other network or security configurations might also impact the ability to connect to external APIs.

Recommendation

Apply workaround: Temporarily add api.sproutsocial.com to the CCR network allowlist to verify if this resolves the issue, while working towards a more permanent and configurable solution.