← Course Home
Okta Certified Workflows - Specialty · Part I

Building Flows

43% of Part I — the exam's largest section, split across 4 modules.

Building Flows · Module 4

Sub-topic: Helper Flows

this deck covers 1 of 3 sub-topics in this module

↑ Module 4 Overview

The Scenario

"Work with helper flows as subroutines with a return value and as a processor for a streaming card"

"Helper flows allow for more efficient management and running of parent flows, such as an application event-driven or API Endpoint flow." Note the renamed terminology: "a child flow is now referred to as a helper flow" — the functionality is unchanged.

Three Reasons To Use One

→ Reuse — move a repeated series of steps into one flow, called from multiple places via Call Flow or Call Flow Async.

→ Per-item processing — run steps against each item in a list using For Each, or transform a list into a new one using Map.

→ Decomposition — break a large flow into smaller, manageable parts.

As a Subroutine

A helper flow can define custom Inputs matching the type of item it will process, run functions that perform a task on each item, and end with a Return (found in the Control category) that hands a value back to the caller. This is the "subroutine with a return value" pattern from the exam objective.

Worked Example

The docs walk through converting an object into a list of key/value objects — a common pattern for cloud APIs that expect a propertyname/propertyvalue pair prefixed with custom:. A helper flow accepting a key, value, and constant prefix, called via object.map, converts:

{"this":"that","up":"down","left":"right"}

into a list of objects, each with propertyname/propertyvalue keys (e.g. propertyname: "custom:this", propertyvalue: "that").

Built-In Outputs

Index — 0-based position in the list (set by For Each / Map)
Caller — id, name, execution_id, method of the calling flow/step (null id/execution_id if run manually — useful for debugging)
Error — raw error object (message, statusCode, execution) when called for error handling
Execution ID — unique ID of this flow instance

One Line To Remember

Helper flows (formerly "child flows") act as callable subroutines — reusable via Call Flow/Call Flow Async, per-item processors for For Each/Map, and streaming-card processors — with a Return output and built-in Index/Caller/Error/Execution ID fields; Caller's id and execution_id come back null when the flow is run manually, which is your tell for manual-vs-automated debugging.

Source: help.okta.com — Helper flows (ext-about-helper-flows)