Okta Certified Workflows - Specialty · Part I

Building Flows

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

Building Flows · Module 1

Sub-topic: Establish Connections

this deck covers 2 of 2 sub-topics in this module

The Task

"Establish connections with the applications needed for your flow by completing required fields"

Once your Okta org is authenticated (previous deck), every other card in a flow still needs its own connection. "Using any event or action card in a flow requires a connection with the third-party app to which it belongs."

Folder-Level vs. Org-Level

Folder-level connections — usable only by flows within the folder where they were created
Org-level connections — usable by any flow within a folder, once added to it

You can create org-level connections on the Connections page, or folder-level ones from the Flows page's Connections tab. Either way, "connections can't be used until they are added to a folder."

Two Entry Points

→ From the Settings page: click New Connection, click the icon for the app, enter the required information (app-specific help via Need Help?).

→ From inside a flow: click New Flow, and when you add an event/action for an unauthorized app, the card itself prompts you to New Connection.

After a connection is authorized, you can reuse that app in any flow without reentering credentials — just select the connection and click Done.

Required Fields by Protocol

OAuth 2.0 — Name, Description, then review scopes on the Permissions tab (Use default scopes, or Customize scopes — required scopes can't be cleared)
Other protocols — Name, Description, plus whatever credentials the service needs: domain, API token, or an access key/secret pair

For OAuth 2.0 connections, click Create and Okta prompts you to sign in to the destination site if required.

Health & Maintenance

A red icon beside a connection name means it isn't working or is missing required options; a green check means it's healthy. From the Connections page's Actions menu you can Edit details, check Usage (which flows use it), Reauthorize (needed after a password/API key change on the destination side), or Delete connection.

The Angle — What Trips People Up

Watch for this in your own sandbox run:

→ Creating an org-level connection and expecting it to be usable immediately — it must still be added to a folder first.

→ Removing a non-required scope on an OAuth 2.0 connection because it "looked unused" — if a connector actually relies on it, the event/action cards stop functioning properly.

One Line To Remember

Every card needs a connection to its app. Connections are folder-level (usable only in that folder) or org-level (usable anywhere once added to a folder). OAuth 2.0 connections let you use default or customized scopes; other protocols just need the right credentials. Red/green icons show connection health, and Reauthorize is required after credential changes on the destination side.

Sources: help.okta.com — Connections (ext-applications-connections); Configure a connection (ext-configure-connection)

✓ Module 1 — 2 of 2 sub-topics complete