okta-workflows

n8n community node for the Okta management API (Users, Groups, Applications) with SSWS token and OAuth2 private-key-JWT auth.

Package Information

Released: 1 mo ago
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.2
Author: martin1967

Available Nodes

Documentation generating…

Okta Workflows icon
Okta Workflows
Work with the Okta management API (Users, Groups, Applications)

Documentation

n8n-nodes-okta-workflows

n8n community node for the Okta management API, styled after Okta Workflows "cards": each
operation lets you pick exactly which fields to read or write.

Built for n8n CE 1.117.3+ on Node 22. MVP scope: Users, Groups, Applications.

Features

  • Two auth methods:
    • API Token (SSWS) — domain + token.
    • OAuth2 Private Key (recommended) — client-credentials with a private-key JWT (client_assertion),
      domain, client ID, scopes, and a PEM private key. Access tokens are cached until expiry.
  • Field selection — read operations expose an Output Fields picker (dot-paths like profile.email);
    leave empty to return the full record. User create/update use a Profile Fields card whose attribute
    list is loaded live from your Okta user schema.
  • Cursor pagination — "Return All" follows Okta's link header.

Operations

Resource Operations
User Create, Get, Get Many (q / filter / search), Update, Deactivate, Delete
Group Create, Get, Get Many, Update, Delete, Add Member, Remove Member, List Members
Application Get, Get Many, List Assigned Users, List Assigned Groups

Local install

npm install
npm run build

# make it visible to a self-hosted n8n instance
mkdir -p ~/.n8n/custom
cd ~/.n8n/custom && npm link n8n-nodes-okta-workflows
# (or) npm i /Users/marat/n8n-okta-cards  from inside ~/.n8n/custom

# restart n8n

Alternatively point n8n at this folder via N8N_CUSTOM_EXTENSIONS=/Users/marat/n8n-okta-cards.

OAuth2 private-key setup in Okta

  1. Create an API Services app (or an OIDC app with client-credentials grant).
  2. Grant it Admin API scopes (okta.users.read, okta.groups.manage, ...).
  3. Add a public key (JWKS) to the app; keep the matching private key (PEM) for the credential.
  4. Ensure the app is assigned an admin role with the needed permissions.

Notes / roadmap

  • resourceMapper (full column-mapping UI) can replace the current Profile Fields card later.
  • JWK (instead of PEM) private keys and additional resources can be generated from Okta's OpenAPI spec.

Discussion