Flow Schema

triggers

Exactly one trigger per flow definition. The key name is arbitrary but conventional names are used (e.g. Recurrence, manual, When_a_new_email_arrives).

See trigger-types.md for all trigger templates.

actions

Dictionary of action definitions keyed by unique action name. Key names may not contain spaces — use underscores.

Each action must include:

• type — action type identifier
• runAfter — map of upstream action names → status conditions array
• inputs — action-specific input configuration

See action-patterns-core.md, action-patterns-data.md, and action-patterns-connectors.md for templates.

Optional Action Properties

Beyond the required type, runAfter, and inputs, actions can include:

Designer Metadata

For existing connector actions, preserve metadata.operationMetadataId when you edit the definition. For new connector actions or Skills/HTTP response actions, add a stable GUID and keep it stable across updates. Do not regenerate these IDs on every deploy; the designer and some run-only surfaces use them to keep action identity consistent.

runtimeConfiguration Variants

Pagination (SharePoint Get Items with large lists):

Without this, Get Items silently caps at 256 results. Set minimumItemCount to the maximum rows you expect. Required for any SharePoint list over 256 items.

Concurrency (parallel Foreach):

Secure inputs/outputs (mask values in run history):

Use on actions that handle credentials, tokens, or PII. Masked values show as "<redacted>" in the flow run history UI and API responses.

Chunked transfer (large HTTP payloads):

Enable on HTTP actions sending or receiving bodies >100 KB (e.g. parent→child flow calls with large arrays).

runAfter Rules

The first action in a branch has "runAfter": {} (empty — runs after trigger).

Subsequent actions declare their dependency:

Multiple upstream dependencies:

Error-handling action (runs when upstream failed):

parameters (Flow-Level Input Parameters)

Optional. Define reusable values at the flow level:

Reference: @parameters('listName') in expression strings.

outputs

Rarely used in cloud flows. Leave as {} unless the flow is called as a child flow and needs to return values.

For child flows that return data:

Scoped Actions (Inside Scope Block)

Actions that need to be grouped for error handling or clarity:

Full Minimal Example