Skip to content
Proud to collaborate with Microsoft for Startups

network.connectivity.plan ​

Plan cross-cloud connectivity between AWS, GCP, and Cloudflare

Plan cross-cloud connectivity between AWS, GCP, and Cloudflare.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-network
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—UUID of the organization
intent_namestringNo—Optional human-readable connectivity intent name
connectivity_typestringNo—auto
sourcejsonYes—Source domain: provider, region, cidr_blocks, and optional references
targetjsonYes—Target domain: provider, region, cidr_blocks, and optional references
allowed_cidrslistNo—Optional explicit routable prefixes
allowed_serviceslistNo—Optional allowed service or port descriptors
private_dnsbooleanNo—Whether private DNS or resolver forwarding should be planned
public_trafficbooleanNo—Whether the intent includes public edge traffic steering
require_redundancybooleanNo—Whether redundant tunnels/circuits should be planned
actorstringNo—Caller initiating the plan

Output Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes——
intent_namestringNo——
connectivity_typestringYes——
architecturestringYes——
readinessstringYes——
supportedbooleanYes——
blockerslistYes——
warningslistYes——
sourcejsonYes——
targetjsonYes——
provider_serviceslistYes——
required_artifactsjsonYes——
route_planjsonYes——
dns_planjsonYes——
traffic_policyjsonYes——
verification_planjsonYes——
apply_availablebooleanYes——
teardown_availablebooleanYes——
next_workflowslistYes——
planned_atstringYes——
failed_atstringNo——
failure_reasonstringNo—Engine-stamped human-readable failure reason
failed_at_statestringNo—Engine-stamped state when the workflow failed
failed_stepstringNo—Engine-stamped step name (DAG path)
failed_layerintegerNo—Engine-stamped layer index (DAG path)
errorstringNo—Engine-stamped exception message
error_typestringNo—Engine-stamped exception class name

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—plan—
failedNoYesNo——
plannedNoYesYes——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedplanplanned—
* (any state)failfailed—

Outcomes ​

OutcomeTypeDescriptionState Data Keys
plannedSUCCESSConnectivity plan was producedreadiness, architecture
failedFAILUREConnectivity planning failedfailure_reason

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "network.connectivity.plan",
  "initial_data": {
    "organization_uuid": "value",
    "source": "value",
    "target": "value"
  }
}