Allow CCR scheduled agents to reach third-party APIs (api.sproutsocial.com)

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

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.

Proposed Solution

Add api.sproutsocial.com to the CCR network allowlist, either globally or as a configurable setting at the trigger or environment level. Ideally, users should be able to specify trusted external domains when creating a trigger — similar to how MCP connectors are attached — so the agent can reach only the APIs it needs.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_