Connector Builder submissions


Your Okta Workflows connector can be submitted to the Okta Integration Network (OIN) for review and publication. By publishing your connector to the OIN, you gain visibility in a public marketplace. Other Okta customers can view and deploy any connectors created through the Connector Builder.

Submitting a connector to the OIN requires a review process to confirm that it meets Okta's quality assurance standards for publication. Any connector available to the general public must meet the following objectives:

  • Developed according to Best practices in Connector Builder

  • Doesn't negatively affect Okta Workflows platform performance

  • Includes help topics for each action card, including Custom API Action cards

  • Executes as expected according to the provided help documentation

The OIN team reviews submitted connectors on a best-effort basis. There are no service level agreements in place around connector submissions. After you submit your connector, the OIN team will contact you with an estimated time frame for the review and publication process.

After it's approved for publication, Okta deploys the connector to preview cells for a one week trial period before being deployed to production cells.


As part of the evaluation, the OIN team expects the submission to be made by an official account. This account needs to have legal access to the associated platform and any APIs used in the connector. It can be directly associated with the company, or through a subsidiary business or a contractor of the company.

If the account isn't clearly associated with the company (typically through the email domain), the OIN team requests proof through an email from a domain that matches the connector, or from a particular owner at the company.


For the OIN testing process, you need to provide the following items when submitting your connector.

Support contact

Provide an actively monitored email address for customer support. Okta publishes this email address as part of your OIN catalog entry.

Escalation contact

You also need to supply an escalation contact address. The OIN team uses this address for any issues encountered during the testing process, or if there's an issue with a published connector. This escalation email isn't made available publicly.


You need to have technical documentation that describes the proper use and configuration of your connector. See Connector Builder submission documentation.

Okta doesn't host the documentation for your connector, so it must be available from your own domain or a publicly accessible third-party site. You can keep this content private during the review process, and then coordinate with the OIN team to make your documentation public when Okta publishes your connector.

Test environment

The OIN team needs a valid account or tenant where they can test your connector. This test tenant should have enough sample data to properly evaluate the connector. For example, if the test connector uses pagination, then you must have enough samples so that the connector can return multiple pages of data.

The test data must not contain any personally identifiable information (PII). Don't use real or pseudonymous profile data.

Provided test credentials should have all the necessary permissions to test the endpoints implemented by your connector.

Test guidance

You also need to provide:

  • A list of test cases, detailing the actions performed by your flows. See Connector Builder submission testing for specific requirements.

  • A copy of your test flows, exported as a folder file.

  • A link to any API documentation associated with the connector. This can be public or private, as long as the OIN team can access these API docs using the provided test credentials.

Related topics

Connector Builder submission documentation

Connector Builder submission testing