The following is a summary of questions and answers from the Okta Workflows community office hours on Thursday, October 31, 2024. I edit some questions for clarity.

New to Okta Workflows

The Getting Started with Okta Workflows page has all the resources to help you get started.

Community forum

Consider posting your questions in the Okta Workflows community forum for a faster response or if there are no open spots in the next office hours session.

Office hours questions and answers

I have an Okta workflow that creates a CSV file and sends it via multipart upload POST to an API endpoint. The API needs the file’s SHA256 hash to verify that the received file is complete and unmodified. What is the best way to have the Okta Workflow calculate the file’s hash? The hash card currently only accepts text inputs and does not accept file inputs. The file info card does not provide hash information.

Okta Workflows does not currently have a solution for this, it would be a feature request.

How do you set up email forwarding in Office 365?

You can create an email forward rule using the Create rule Graph API.

How do I set up a return value in a helper flow?

The How to Set Up Helper Flow Return Values in Workflows guide shows how to set up a return value in a helper flow.

Do you have any recommendations on how to query the best eight million deactivated Okta accounts and delete them?

We advise breaking the accounts into smaller groups since the returned limit is one million.

How do I integrate with SolarWinds Service Desk API?

Use the API Connector card to call the SolarWinds Service Desk API.

According to the Authentication section, an Admin will generate a token, which you must include in the request.

A sample request from Workflows look like this:

How to add a pause for approval step in a flow?

Okta Workflows has no built-in feature to wait for user input and resume execution.

A possible solution is to break the flow into two flows. The first flow runs and ends when user input is needed. The user provides input (delegated flow or Slack), and a second flow starts running.

Our email naming convention is first.lastname@domain.com, so a workflow calls Google and requests a list of users with the same first and last name email prefixes. However, when uploading 2-3 users simultaneously (in a CSV file and using the Okta – Create User event), the workflow runs all the new users in the same record. When they each make the API call to Google, they are all assigned the same next available email address. When the workflow ends, it creates a new account, and all users who were assigned the same email address now have the same Google account since they pass through Okta SSO to access the accounts. I want to build latency to ensure the records flow sequentially and not simultaneously.

The flow needs to perform post-change checks to ensure that the uniqueness constraint hasn’t been violated and take corrective action if it has. For instance, add error handling if assigning a username fails and assigning a subsequent username.

We don’t advise using timers or pausing the flow for a random number of seconds to prevent simultaneous runs since there is no guarantee that flows will not run simultaneously. Workflows has no control when the Okta core delivers events.

Get in touch

Email me if you have questions or sign up for our next office hours session.

Okta Workflows resources

🍫 Get help from Workflows specialists during weekly community office hours.

📺 Learn from Workflows videos.

🛟 Ask questions on the Okta Workflows community forum.

🙋🏻‍♀️ Get help from the community: join the #okta-workflows channel on MacAdmins Slack.