Okta Certified Workflows - Specialty · Part I

Workflows Overview

27% of Part I — the exam's largest single knowledge area alongside Building Flows.

Workflows Overview

Sub-topic 2: Understand Types of Flows

7 sub-topics · this deck covers sub-topic 2 of 7

The Task

"Parent and helper flows are the two primary types of flows that you can run on the Workflows platform."

The exam names five flow shapes to know cold: App Event, Scheduled, API Endpoint, and Delegated flows are all parent flows — the caller. A Helper flow (previously called a "child flow") is the other primary category — it only runs when a parent calls it.

Parent Flow Type 1 — Application Event Flows

Triggered when an action takes place in Okta or a third-party application — a user added to an app in Okta, a new Salesforce customer, a new Google Sheets row. "Many application events, including those from Okta, can be triggered in response to an incoming webhook." The external system makes an HTTP call to Workflows the instant the event occurs, and that call triggers the flow.

Parent Flow Type 2 — Scheduled Flows

Runs on a specified schedule — once an hour, 5pm on Fridays, 9am on the first of the month. You change the schedule via the clock icon on the event card, and "the schedule only goes into effect after the flow has been turned on." Every scheduled flow card outputs a Current Time (ISO UTC) and an Execution ID unique to that instance.

Parent Flow Type 3 — API Endpoint Flows

Triggered by changes at an external source, and unlike app-event flows, these can be triggered at any time — the external client calls the endpoint and receives the flow's output directly. Security is the key differentiator, covered fully in Sub-topic 5: OAuth 2.0, a client token, or none at all (public service).

Parent Flow Type 4 — Delegated Flows

"Delegating a workflow is an option to have a flow that an Okta admin can view and run directly from the Okta Admin Console." An admin can run it only when: the flow uses a Delegated Flow event card, a custom admin role exists with a resource set containing that flow, the role has the Run delegated flow permission, and the role is assigned to one or more admins. It lets you grant a narrow automation capability without granting full Workflows access.

Helper Flows (Formerly "Child Flows")

"Helper flows were previously known as child flows. The functionality for such flows remains unchanged."

A helper flow is called from any parent flow to perform a repeated action, such as querying a list. It's inactive until called, then becomes active and runs. Helper flows simplify complex flows — especially those using List functions, a common set of repeated tasks, or centralized error handling.

The Gotcha — Folder View and Naming

Watch the legacy naming: exam questions or older UI text may still say "child flow" — Okta's own docs flag this explicitly as a rename with no functional change. The Folder view lets you sort flows by type, active status, name, author, creation date, or last-edited date — useful for locating which flows are parents vs. helpers in a busy folder.

The Connection

This taxonomy underlies everything else in the module. Sub-topic 4 (Workflow Elements) explains that every flow — regardless of type — starts with an event card, and Sub-topic 5 drills into the three security models specific to API Endpoint flows. Sub-topic 6 (Execution Limits) shows that flow type also determines eligibility for low-latency mode — API Endpoint, Okta-event, webhook, and Delegated flows all start there by default.

The Angle — What Trips People Up

→ Forgetting a Scheduled flow doesn't run until it's turned on — the schedule itself doesn't activate anything by existing.

→ Confusing "Delegated flow" (an admin-run flow surfaced in the Admin Console) with "Helper flow" (an internal sub-routine called by another flow) — they solve completely different problems.

→ Assuming any application event needs polling — many are pushed via incoming webhook the instant the event fires, not pulled on an interval.

One Line To Remember

Four parent flow types — App Event (webhook-triggered), Scheduled (runs on an interval, must be turned on), API Endpoint (callable anytime, three security models), and Delegated (admin-run from the Admin Console via a custom role) — plus Helper flows, which only run when called by a parent and were formerly called "child flows."

Sources: help.okta.com — Parent flows and other flow types (ext-control-method-callable); Delegated flows (ext-about-delegated-flows); Build a delegated flow (ext-http-method-delegated)

Next: Sub-topic 3 →