On joining Okta, Workflows and No-Code
Tags: devrel, nocode, career
Published: 2021-10-04 18:18:02

---
title: On joining Okta, Workflows and No-Code
published: true
date: 2021-10-01 22:53:43 UTC
tags: DevRel, NoCode, Career
canonical_url: https://maxkatz.org/2021/10/01/on-joining-okta-workflows-and-no-code/
---

This week I joined Okta as Workflows Builder Advocacy Lead.


{% twitter 1442980770683916288 %}

[Okta Workflows](https://help.okta.com/wf/en-us/Content/Topics/Workflows/workflows-main.htm) is an identity-centric no-code and automation solution. I will be helping build, scale, and help Workflows community be successful. I love the no-code space and I have been writing about [no-code on this blog](https://maxkatz.org/category/no-code/). I also love [developer relations and advocacy](https://maxkatz.org/category/devrel). When I saw an opportunity to work on no-code in the context of advocacy I jumped on it.

No-code gives people super powers. People can build without needing to ask developers to build it for them and they can build it quickly. Something that would take months before (waiting for developers) now can take days or even hours in some cases. When you can build a solution yourself and fast, that’s an awesome super power.

Okta’s goal is to connect everything, it helps connect users with apps. Okta provides cloud software that helps companies manage and secure user authentication into applications.

Okta’s core solution is powerful and will handle many provisioning (and de-provisioning) cases. For example when user is created at an organization, they would be provided with access to specific groups and applications.

But, with a surge of cloud applications (think Slack, Google Workspace, etc.) and remote work, companies need to go beyond out-of-the-box solutions and build custom, flexible and automated flows for granting access, revoking access, transferring user’s files, nudging inactive customers to take action and sending notifications.

Okta Workflows allows to build such flows using a no-code (visual) solution. This means people can build sophisticated flows without dedicated resources to build and maintain any custom code. Think of Okta Workflows as a no-code automation solution on top of Okta’s core offering.

I think another way to look at Workflows, it’s a [Zapier](http://zapier.com)-like solution for the identity and access space. For example, let’s say you want to want to read user information from a Google Sheets and create new users in Okta. You could do that with dedicated IT resources, and custom scripts. Someone would need to maintain the scripts and any notifications you want to make, you would need to reach out to IT again.

With Okta Workflows, you don’t need IT resources because you can do it yourself using a no-code visual solution. It’s easy and fast. Here is how a flow looks that would get users from a Google Sheets and create new users in Okta. The flow is scheduled to run periodically.

[![A flow to read users from Google Sheets and create a new user in Okta](https://katzmax.files.wordpress.com/2021/10/workflows-googlesheets.png?w=1024)](https://katzmax.files.wordpress.com/2021/10/workflows-googlesheets.png)<figcaption>A flow to read users from Google Sheets and create a new user in Okta.</figcaption>

The automation is built visually, without coding.

Workflows has a large number of connectors available out-of-the-box. You can quickly connect to any of these services in a flow:

[![A list of out-of-the-box connectors available in Workflows](https://katzmax.files.wordpress.com/2021/10/workflows-connectors.png?w=1024)](https://katzmax.files.wordpress.com/2021/10/workflows-connectors.png)<figcaption>A list of out-of-the-box connectors available in Workflows.</figcaption>

If a service you want to use is not listed, you can use a generic API Connector to connect to that service:

[![Workflows API Connector](https://katzmax.files.wordpress.com/2021/10/workflows-api-connector.png?w=558)](https://katzmax.files.wordpress.com/2021/10/workflows-api-connector.png)<figcaption>Workflows API Connector.</figcaption>

I love Okta’s mission to democrotize customer identify and access.

I also love the fact that Okta is an enterprise company and solving real problems and now offers a no-code automation solution to enable a lot more folks to build solutions, and faster. Many no-code companies start by targeting individual builders/creators and only later pivot to enterprise (once they realize it’s hard to make money on the consumer side).

As I learn more about Workflows, I will be sharing tutorials, videos and other education materials. I also would love to partner with other companies to run joint online events. Please reach out if you would like to collaborate!

If you want to start learning about Workflows now, I’d recommend to check out these [tutorials](https://help.okta.com/wf/en-us/Content/Topics/Workflows/Tutorials/tutorials-workflows-learn.htm).