Okta Workflows release notes (2025)

2025.01.2

Event cards added to Okta connector

The following event cards have been added to the Okta connector:

See the Okta connector.

Fixes in Okta Workflows

  • OKTA-663824

    Flow names with underscores or hyphens aren't permitted in Connector Builder but the validation pop-up incorrectly indicated that a name containing these characters was valid.

  • OKTA-816135

    For a Tables Search Rows card configured with a Where Expression filter, if the admin clicked Choose fields, the card lost the values of the fields specified in the filter.

  • OKTA-830211

    The Usage link in the user info dropdown menu pointed to the legacy Usage page, rather than redirecting the admin to the new usage dashboard on the Workflows Console Home page.

  • OKTA-853393

    The Save Flow dialog didn't appear if the admin created a flow and clicked the back button in their browser.

  • OKTA-856042

    When a user enabled mapping for a flow, the mapping lines between input and output fields were only visible when the user hovered over a field, instead of also being available when the user clicked the field.

2025.01.1

Workday connector supports other user domains

The Workday connector now supports the use of any Workday domain for connections, including the .myworkday.com domain.

See Authorization.

CrowdStrike connector now available

The CrowdStrike connector is now available in Okta Workflows with the following cards:

See the CrowdStrike connector.

Fixes in Okta Workflows

  • OKTA-816321

    The If/Else function card didn't show the mapping references for the Input and Output fields even when Show Mapping was activated.

  • OKTA-817024

    When an admin dragged the output field from the individual cards within a Branching function card to the main Outputs field, the function card set the Outputs field to the type of individual card output that was last dropped.

  • OKTA-850679

    Some cards returned intermittent 500 - Node Error: recv error messages.

2025.01.0

Okta Workflows Console home page updated

This release introduces significant updates to the Okta Workflows Console landing page. These improvements to the Home page are intended for new Okta Workflows users, so admins can learn about flows and start creating their own flows quickly. This includes elevating introductory materials and highlighting relevant templates.

With the New Flow button, admins can now create flows directly from the Home page.

See Workflows Console.

OAuth 2.0 security to invoke API endpoints

Okta Workflows users can now securely invoke API endpoints using OAuth 2.0 protocols and their Okta org authorization server. In comparison with the existing token authorization option, this feature is more secure while also being easier to implement.

Add the okta.workflows.invoke.manage scope to any new or existing app integration to make it eligible to invoke your API endpoint.

See Invoke a flow with an API endpoint.

Salesforce connector for Okta for Government High

The Salesforce connector is now available in Okta for Government High orgs.

Fixes in Okta Workflows

  • OKTA-747948

    The Object Split function card accepted a List of Objects type for the Object input field when it should only accept an Object type.