BusyBot
Search all guides

Reference · Credentials

Connect Okta to BusyBot

Used by 1 BusyBot node.

Type oktaApi 2 fields

Fields

FieldTypeRequiredNotes
URL
url		 string Yes Your Okta organization URL (e.g., https://dev-123456.okta.com).
Access Token
accessToken		 password Yes Okta SSWS API token. Create in Okta Admin Console: Security > API > Tokens > Create Token.

Setting up Okta API

  1. In Okta API, create the credential this connection needs — the values listed in the table above. These are issued from your own Okta API account, usually under its developer, API or integrations settings.
  2. In BusyBot, open Credentials → Add credential and choose Okta API.
  3. Paste each value into the matching field and save.
  4. Add the Okta node to a workflow, select this credential, and run a simple operation to confirm it authenticates.

Security

  • Secret values are encrypted at rest with AES-256-GCM, never written to logs, and readable only by your own account (to edit them).
  • Grant the minimum scopes or permissions the operations you actually use require.
  • Rotate the credential periodically, and immediately if it may have been exposed.
  • Credentials are scoped to your account — a workflow cannot use another account's.

Frequently asked questions

Which BusyBot nodes use Okta credentials?

One node: Okta. Create the credential once and select it in that node.

What does a Okta credential need?

2 fields: URL, Access Token. Required: URL, Access Token. The values come from your own Okta account.

How are Okta secrets stored?

Secret values are encrypted at rest with AES-256-GCM, never written to logs, and scoped to your account: only you can open the credential again to edit it, and a workflow in another account cannot use it.

Nodes that use Okta API

One credential works across every node below — create it once and reuse it.