Resolve the 400 Bad Request error in Okta Workflows by using the Jamf Pro API connector to send Device Lock or Erase Device commands.

Update the output data type to match the expected input type to resolve an Okta Workflows card error and save the flow.

The Workflows API Connector supports custom OAuth 2.0 connections, but some unique vendor implementations may not be fully compatible.

This article describes how Okta Workflows supports using files and attachments in a flow.

Expand Microsoft Graph API access in Okta Workflows using the API Connector & OAuth 2.0 to connect Microsoft Graph API with custom scopes and refresh token.

This article explains how to create a Salesforce Contact for users who are not assigned to the Salesforce application using Okta Workflows.

This article discusses six ways to trigger a flow.

This document provides guidance on using the Okta Workflows Table Search Rows functionality with "OR" statements in a "Where" clause.  

When configuring Okta as an EAM for Microsoft Entra ID, the Microsoft user GUID must be translated to the Okta Application.

An employee is onboarding, and based on their department, an email should be sent to a group of people associated with that department.