Skip to main content

Workflow recipes for common jobs

Each recipe starts from a template, changes one or two blocks, and saves the result as a workflow of your own. They use only blocks the API accepts today; each block is in the node reference.

How each recipe is made​

Take the template's graph, apply the recipe's change, save it under your slug, then test it. A test run delivers nothing. The commands below make the first recipe; for another, put its template, name and slug in place of pass-yield, Passes under 20 GB and under-minimum.

API=https://api.constellation.space
H="x-api-key: $CONSTELLATION_API_KEY"

# 1. The template's graph, under a name of your own
curl -sS -H "$H" "$API/predictions/workflows?templates=true" \
| jq '.workflows[] | select(.slug == "pass-yield") | {name: "Passes under 20 GB", graph}' > workflow.json

# 2. The recipe's change (below), then save it as your workflow's next version
jq -f change.jq workflow.json > changed.json
curl --fail-with-body -sS -X PUT -H "$H" -H "content-type: application/json" \
"$API/predictions/workflows/under-minimum" -d @changed.json

# 3. A test run over a past day
curl --fail-with-body -sS -X POST -H "$H" -H "content-type: application/json" "$API/predictions" \
-d '{"workflow": "under-minimum", "from": "2026-11-08T00:00:00Z", "to": "2026-11-09T00:00:00Z", "deliver": false}'

Read the run with GET /predictions?run_id= until its status is done; see Long runs.

Flag passes under a contract minimum​

From pass-yield. A threshold after expected_gb keeps only the passes whose low case is under 20 GB, so every output carries just those. change.jq:

.graph.nodes += [{"id": "under_min", "kind": "condition", "ref": "threshold",
"params": {"column": "expected_gb", "quantile": "p10", "op": "<", "value": 20}}]
| .graph.edges |= map(if .from.node == "expected_gb" then .from = {"node": "under_min", "port": "true"} else . end)
| .graph.edges += [{"id": "expected_gb-under_min", "from": {"node": "expected_gb", "port": "rows"},
"to": {"node": "under_min", "port": "rows"}}]

Use "quantile": "p50" to compare the expected value instead. A pass that could not be priced never matches.

Hold rain-fade swaps for approval​

From rain-fade-swap. A policy step in approve mode between at_risk and the outputs holds every swap until someone sends it to your mission control system (MCS) or declines it. Running it needs Operator. Holding swaps for a decision and sending them needs Operator + Act; on Operator a run sends no swap and keeps each as what Act would have done. See From trial to sending.

.graph.nodes += [{"id": "approve", "kind": "transform", "ref": "policy", "params": {"mode": "approve"}}]
| .graph.edges |= map(if .from.node == "at_risk" then .from = {"node": "approve", "port": "rows"} else . end)
| .graph.edges += [{"id": "at_risk-approve", "from": {"node": "at_risk", "port": "true"},
"to": {"node": "approve", "port": "rows"}}]

To match your provider's cancellation cut-off, also set the swap node's cancel_lead_s, in seconds before the pass starts.

Plan MODCOD for one ground station​

From modcod-plan. Name that ground station's antennas on the input; the same works for satellite_ids, which Explore needs when your fleet has more than 2 satellites.

(.graph.nodes[] | select(.id == "passes") | .params.antenna_ids) = ["ant-1", "ant-2"]

Each item's series is the pass's MODCOD schedule, one entry per change.

Daily capacity per ground station​

From antenna-capacity, which needs the Network plan. sum_by totals per antenna; change it to total per ground station:

(.graph.nodes[] | select(.id == "sum_by") | .params.by) = "ground_station"

Each item is one ground station on one UTC day, with its passes, sellable minutes and expected GB.

Send pass yield to a webhook​

In the builder, with no API calls. Connect a webhook first, then open your pass-yield workflow, tick the webhook under Deliver to, and Publish. The new output sends the same columns as the API output. Each run that delivers then posts its items to your endpoint, signed. Webhooks need Operator.

Next: no fleet yet? Load the demo fleet and run the first recipe on it.