Workflows — plan actions

The two plan-building actions create (or reuse) a plan and then fill it. The other two actions — webhook and email — are on the Integrations page.

CREATE_OR_GET_PLAN

Creates a plan, or reuses a matching one, for the run. Common fields: name and description (both interpolated). The rest depends on planType.

RESTOCK

{
  "actionType": "CREATE_OR_GET_PLAN",
  "planType": "RESTOCK",
  "brandSource": { "kind": "static", "brandId": "<uuid>" },
  "collectionSource": { "kind": "static", "collectionId": "<uuid>" },
  "deadline": { "kind": "relative", "offsetDays": 30 }
}

brandSource and collectionSource are each { kind: "static", … } or { kind: "fromTrigger" } (resolve from the triggering entity). deadline is a date offset.

REBALANCE

{
  "planType": "REBALANCE",
  "outgoingShopId": "<uuid>",
  "ingoingShopId": "<uuid>",
  "collectionSource": { "kind": "fromTrigger" },
  "deadline": { "kind": "relative", "offsetDays": 14 }
}

outgoingShopId / ingoingShopId (source / destination) are required.

MARKDOWN

{
  "planType": "MARKDOWN",
  "season": "SS26",
  "startDate": { "kind": "relative", "offsetDays": 0 },
  "endDate": { "kind": "relative", "offsetDays": 30 },
  "collectionSource": { "kind": "fromTrigger" }
}

season, startDate, endDate are optional.

SUPPLIER_RETURN

{ "planType": "SUPPLIER_RETURN", "supplierId": "<uuid>", "sourceShopId": "<uuid>", "deadline": { "kind": "relative", "offsetDays": 21 } }

supplierId is the required discriminator for find-or-create; sourceShopId is optional.

SUPPLIER_EXCHANGE

{ "planType": "SUPPLIER_EXCHANGE", "supplierId": "<uuid>", "sourceShopId": "<uuid>", "destinationShopId": "<uuid>", "deadline": { "kind": "relative", "offsetDays": 21 } }

supplierId required; sourceShopId (RETURN side) and destinationShopId (RECEIVE side) optional.

Output: planId, planType, planName, isNew — available downstream as {{steps.<nodeId>.output.planId}} etc.

ADD_ITEMS_TO_PLAN

Adds items to the plan created by a CREATE_OR_GET_PLAN node. Common fields:

Field	Meaning
`sourcePlanNodeId`	The id of the create-plan node this fills.
`planType`	Must match the source plan.
`entityFilters`	Optional `{ includeTags, excludeTags }` to narrow which entities become items.
`maxItems`	Optional hard cap on how many items are added.

Scopes

Shop scope (shopScope): { kind: "all" }, { kind: "specific", shopIds: [...] }, or { kind: "fromTrigger" }. (Not used for rebalance — shops come from the plan header.)
Size scope (sizeScope): { kind: "all" } or { kind: "belowStockThreshold", threshold: <n> }.

Strategies

Quantity strategy (restock / rebalance / supplier)

{ "kind": "fixed", "quantity": 10 }
{ "kind": "fillToTarget", "target": 50 }
{ "kind": "scoreDriven" }

fixed — add a literal quantity per item.
fillToTarget — top each item up to target (only the delta is added).
scoreDriven — the data platform’s resolver reads the decision vector to set the quantity (no app-side parameters).

Matching strategy (REBALANCE only)

{ "kind": "fixed" }
{ "kind": "scoreDriven" }

scoreDriven routes to the rebalance matching resolver (surplus/deficit/transfer-urgency scores → bipartite matching of source to destination shops).

Discount strategy (MARKDOWN only)

{ "kind": "fixed", "percent": 30 }
{ "kind": "scoreDriven" }
{ "kind": "recommended", "fallbackPercent": 15, "maxDiscountPct": 70, "marginFloorPct": 0 }

fixed — apply a literal percent (0–100).
scoreDriven — the decision layer’s recommended-discount resolver.
recommended — decision-layer discount with three bounded knobs; defaults shown (fallbackPercent 15, maxDiscountPct 70, marginFloorPct 0).

Per-plan-type fields

Plan type	Item config
`RESTOCK`	`quantityStrategy`, `shopScope`, `sizeScope`
`REBALANCE`	`quantityStrategy`, `sizeScope`, `matchingStrategy` (no shop scope)
`MARKDOWN`	`discountStrategy`, `shopScope`, `sizeScope`
`SUPPLIER_RETURN`	`quantityStrategy`, `reasonCode` (applied to every item)
`SUPPLIER_EXCHANGE`	`side` (`RETURN`/`RECEIVE`), `quantityStrategy`

Output: addedCount, skippedCount — available as {{steps.<nodeId>.output.addedCount}}.

Items added by a workflow carry their decision-vector attribution into the plan’s activity log, and the same business rules apply as for manual edits.

API integration

API recipes

Platform & data model

Decision layer (reference)

Operations & infrastructure

Ingestion specs (reference)

Workflows (reference)

Tagging rules (reference)

Alerts (reference)

Workflows — plan actions

CREATE_OR_GET_PLAN

ADD_ITEMS_TO_PLAN

Scopes

Strategies

Per-plan-type fields

​CREATE_OR_GET_PLAN

​ADD_ITEMS_TO_PLAN

​Scopes

​Strategies

​Per-plan-type fields

CREATE_OR_GET_PLAN

ADD_ITEMS_TO_PLAN

Scopes

Strategies

Per-plan-type fields