Okta Workflows - Preview release notes

Current release

Preview release of Okta Workflows 2023.05.2 began deployment on May 24, 2023.

Jira Service Desk connector

The Jira Service Desk connector is now called the Jira Service Management connector to reflect the changed name for this product. There are no changes in functionality for existing Jira Service Desk cards.

Freshservice connector update

Freshservice announced the deprecation of username and password authentication as of May 31, 2023. After this date, any connections created using the Authorize By Credentials option on the Freshservice connector will stop working. To avoid errors in their Freshservice workflows, users should migrate their connections to use the Authorize By API Key option. See Deprecation of username and password-based basic authentication for API v2.

Workflows templates

The following Okta Workflows templates are now available:

  • Invalidate anomalous Slack sessions

  • Sync Okta group membership with Office 365 unified groups

  • Encourage stronger MFA adoption

  • Activate and deactivate accounts with notifications in Microsoft Teams

The following Okta Workflows templates have been updated:

  • Generate unique Okta username with user import inline hooks: updates the template description.

  • Manage Okta group membership based on profile attributes: updates the Pluck function card to use Profile.Name as the key name, instead of Name.

The following Okta Workflows templates are no longer available:

  • Generate unique Okta usernames

  • Modernize your access request management with Okta and Slack

See Available Workflows templates.

Fixes in Okta Workflows


On the Custom API action card for Jira Service Desk, if the Relative URL didn't begin with a leading slash / character, the card returned an error.


The Office 365 Admin Search User card failed when searching for email addresses that contained an apostrophe.


In the Flow History view, workflow executions were sorted by the completion time instead of the start time.


Creating a connection in the Kandji connector failed if the domain authentication input value started with an h, t, p, or s character.