Okta Certified Workflows - Specialty · Part II

Create Groups

26% of Part II — group lifecycle from connection to membership.

Create Groups

Task 2: Create Groups

4 tasks · this deck covers task 2 of 4

The Task

"Create groups"

With the connection authorized (Task 1), the actual group object gets created with the Create Group action card from the Okta connector: "Create a new Okta group in Okta."

The Gotcha — Universal Directory Requirement

"To use the Create Group action card, make sure to enable the Group Profiles for Universal Directory feature for your Okta org. Otherwise, the card will return a Failed to load error and no input or output fields will be added."

This is the single most testable fact on this card — without that feature enabled, the card doesn't just fail at runtime, it fails to even load its fields in the editor.

Inputs

Group Name — Text, required. 1–255 characters.
Description — Text, optional. 0–1024 characters.
Custom Properties — Object, required (dynamically generated fields).

Name is the only input with a hard minimum length; Description is fully optional down to zero characters.

Outputs

ID (Text) — unique group ID
Created / Last Updated / Last Membership Updated (Date & Time)
Object Class (List of Text) — group's profile class
Type (Text) — how the group's profile and membership are managed
Profile: Name, Description (Text)
Links (Object) — discoverable related resources
Custom Properties (Object)

The returned ID is what downstream cards — like Add New User to Group in Task 4 — need as their Group ID input.

The Connection — Scopes

Per the docs: "See Action cards for the list of required OAuth scopes for this card." The Create Group card needs its own scope granted on the connection from Task 1 — it isn't automatically covered by having authorized the connector generically.

The Angle — What Trips People Up

Watch for this in your own sandbox run:

→ Building a Create Group flow in an org without Group Profiles for Universal Directory enabled, then debugging a "Failed to load" error that's actually an org-feature gap, not a flow bug.

→ Forgetting the group scope on the connection even though the connector itself is already authorized for other cards.

One Line To Remember

Create Group needs Group Profiles for Universal Directory enabled on the org, or the card fails to load its own fields. Name is required (1–255 chars), Description is optional (0–1024 chars). The output ID feeds Task 4's Add User to Group card.

Sources: help.okta.com — Create Group action card (type=wf&id=ext-okta-method-creategroup)

Next: Task 3 →