okta-workflows-connectors

Documents ten quirks of Okta and Microsoft Entra ID connectors in Okta Workflows.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-connectors-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okta-workflows-connectors
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/okta-workflows/skills/okta-workflows-connectors
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-connectors-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Okta Workflows connector cards behave differently from the raw APIs they wrap, causing silent failures, incomplete search results, and unexpected record caps that are hard to diagnose without documented workarounds. ## Core Features & Use Cases - Okta connector quirks: Covers exact-eq-only Search Groups, APP_GROUP vs OKTA_GROUP type semantics, keyword-based Search Group Rule matching, and connector-specific rate limits (30 concurrent, 6,000/min, DynamicScale multipliers). - Entra ID connector quirks: Covers delegated-permissions-only auth, reauthorization breakage, the three record caps (4,000 groups / 900 members / 4,000 users), silent failures on mail-enabled security and distribution groups, and the 2-level List Contact Folder cap. - Use Case: When an Okta Workflows flow returns only 900 group members instead of the expected full set, consult this Skill to learn the Search Group Members card cap and switch to Stream Matching Records. ## Quick Start Ask why the Okta Workflows Azure AD Search Group Members card returns only 900 records and how to retrieve the full membership.

Frequently Asked Questions about okta-workflows-connectors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Okta Workflows Search Group Members return only 900 records?

The Azure AD Search Group Members card caps results at 900 records, documented as "First 900 Matching Records". To retrieve more, use the Stream Matching Records option instead of the fixed result set.

How do I filter Entra-imported groups in Okta Workflows Search Groups?

Filter on Type = APP_GROUP, which marks groups imported from apps like Active Directory. Because the card uses exact eq matching, use Custom Search Criteria or the Custom API Action card for partial matches.

Does the Okta Workflows Entra connector support app-only permissions?

No, the Azure AD connector uses delegated permissions tied to a signed-in admin or user account, with no app-only or service-principal option. Use a dedicated service account for the connection.

Why do mail-enabled security groups fail in Okta Workflows?

The Microsoft Graph API treats mail-enabled security and distribution groups as read-only, so write cards like Update Group or Add User to Group silently fail. Manage O365/unified groups instead, or use the on-premises PowerShell template.

What are the Okta connector rate limits in Okta Workflows?

The built-in Okta connector allows 30 concurrent requests, 15 concurrent GET/READ per-user requests, and 6,000 requests per minute, none of which appear in the rate-limits dashboard. DynamicScale multipliers raise the concurrent ceiling up to 150 at 50x.