
Okta
Octa
I tried using the original connector for the automation flow in Okta Workflows
Introduction
Okta Workflows is a feature that allows you to automate various tasks without using scripts or code.
(Reference article: What exactly is Okta Workflows...I'll explain!)
Okta Workflows has a useful feature called "connectors" that allows you to easily integrate with external applications. Connectors are published in the Collaborative Applications Catalog hosted by Okta Workflows and are available to any Okta user.
This time, we would like to introduce "Connector Builder", which allows you to create original connectors and use them easily!
What is Connector Builder?
Connector Builder is a feature that allows you to use original connectors in Okta Workflows.
With Connector Builder, you can develop original connectors with no code on the same screen as Okta Workflows and publish them for use by all users of Okta Workflows. Users can use the developed original connector in the same way as a normal connector.
When you use the card of the original connector, the action set in advance on the Connector Builder management screen is executed.

Connector Builder Use Cases
Connector Builder makes it easy to make API calls to external applications.
For example, you can create and publish connectors for applications that don't have connectors in Okta Workflows so that third parties can easily send API calls.
Comparison with API Connector
Similar to Connector Builder, there is also API Connector, a feature of Okta Workflows for working with applications that don't have connectors.
Let's compare them item by item.
Connector Builder | API Connector | |
Ease of creation when creating | △ complicated |
○ easy |
Customizability | ○ Wide range of customization |
△ Narrow range of customization |
Ease of use when using | ◎ Easy to use, just like any other connector Okta offers |
△ It is necessary to use it while checking the API specifications |
Usage image | Created by the system provider and used by the system user | Used by system users when creating their own flows |
As you can see in the table above, Connector Builders are harder to create than API Connectors, but are more customizable when created and easier to use.
The difference in features is due to the different usage images of the two. Connector Builder has cases where the creator and user are different, and API Connector is used when creating your company's flow.
Connector Builder is easy to use, even if you're not an Okta Workflows-savvy admin. Also, when using it, there is no need to check the API documentation of the external application side to be linked, and it can be used seamlessly like a normal connector provided by Okta.
Configuring Connector Builder
Set what action to take when executing the card of the original connector on the Connector Builder management screen. As with the Workflows management screen, cards with various functions can be used, and settings can be made easily with drag-and-drop.
Example) Create a MobileIron connector and set the action to be executed when the Create User card is used

Summary
By using the Connector Builder feature introduced this time, you can publish your original connector to Okta's application catalog.
If you are interested in this blog, please contact Macnica.
Inquiry/Document request
In charge of Macnica Okta Co., Ltd.
- TEL:045-476-2010
- E-mail:okta@macnica.co.jp
Weekdays: 9:00-17:00