Okta · Arazzo Workflow

Okta Create Application, Assign User, and Activate

Version 1.0.0

Create an application, assign a user to it, then activate the application.

1 workflow 1 source API 1 provider
View Spec View on GitHub IdentityWorkforce IdentityCustomer IdentityAuthenticationAuthorizationSingle Sign-OnMulti-Factor AuthenticationIdentity GovernancePrivileged AccessAI AgentsCross-App AccessMCPPlatformArazzoWorkflows

Provider

okta

Workflows

create-app-assign-user-and-activate
Create an application, assign a user, and activate it.
Creates an inactive application, assigns a user to it, then activates the application instance.
3 steps inputs: label, name, oktaApiToken, signOnMode, userId outputs: appId, appUserId
1
createApp
Create the application in an INACTIVE state so it can be configured before going live.
2
assignUser
Assign the supplied user to the newly created application.
3
activateApp
Activate the application now that its first user assignment is in place.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Okta Create Application, Assign User, and Activate
  summary: Create an application, assign a user to it, then activate the application.
  description: >-
    A full application provisioning flow. The workflow creates an application in
    an inactive state, assigns an existing user to it for SSO and provisioning,
    and finally activates the application so it goes live with its first
    assignment in place. The new application id is chained from creation through
    the assignment and activation steps. Every step spells out its request
    inline, including the SSWS API token header, so the flow can be read and
    executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: applicationApi
  url: ../openapi/okta-application-api-openapi.yml
  type: openapi
workflows:
- workflowId: create-app-assign-user-and-activate
  summary: Create an application, assign a user, and activate it.
  description: >-
    Creates an inactive application, assigns a user to it, then activates the
    application instance.
  inputs:
    type: object
    required:
    - oktaApiToken
    - label
    - signOnMode
    - userId
    properties:
      oktaApiToken:
        type: string
        description: Okta API token used for the SSWS Authorization header.
      label:
        type: string
        description: The user-defined display name for the application.
      signOnMode:
        type: string
        description: The application sign-on mode (e.g. BOOKMARK, SAML_2_0).
      name:
        type: string
        description: Optional unique key for the app definition.
      userId:
        type: string
        description: The id of the existing user to assign to the application.
  steps:
  - stepId: createApp
    description: >-
      Create the application in an INACTIVE state so it can be configured before
      going live.
    operationId: createApplication
    parameters:
    - name: Authorization
      in: header
      value: SSWS $inputs.oktaApiToken
    - name: activate
      in: query
      value: false
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.name
        label: $inputs.label
        signOnMode: $inputs.signOnMode
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      appId: $response.body#/id
  - stepId: assignUser
    description: >-
      Assign the supplied user to the newly created application.
    operationId: assignUserToApplication
    parameters:
    - name: Authorization
      in: header
      value: SSWS $inputs.oktaApiToken
    - name: appId
      in: path
      value: $steps.createApp.outputs.appId
    requestBody:
      contentType: application/json
      payload:
        id: $inputs.userId
        scope: USER
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      appUserId: $response.body#/id
  - stepId: activateApp
    description: >-
      Activate the application now that its first user assignment is in place.
    operationId: activateApplication
    parameters:
    - name: Authorization
      in: header
      value: SSWS $inputs.oktaApiToken
    - name: appId
      in: path
      value: $steps.createApp.outputs.appId
    successCriteria:
    - condition: $statusCode == 200
  outputs:
    appId: $steps.createApp.outputs.appId
    appUserId: $steps.assignUser.outputs.appUserId

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/okta-create-app-assign-user-and-activate-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.