Skip to content
ClickRuntime

Automate Okta

Watch your identity org for the events that need a second look. Lockouts and admin role grants reach your security channel, you get a daily list of accounts created or deactivated, and once a month you see who hasn't logged in for 90 days. Say what you want to your AI assistant, look over what it plans to do, and it carries on running.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 5 minutes, check the Okta System Log and post to #security in Slack whenever a user is locked out, has MFA reset, or is given an admin role, with the user and who made the change.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Okta

Early warning on risky account events, a record of joiners and leavers, and a regular list of dormant accounts to review. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Alert your security channel on lockouts and admin grants

Account lockouts, MFA resets and new admin roles appear in chat within minutes.

See how it works
Daily

Get a daily list of new and removed accounts

Each morning you see which Okta users were created and which were deactivated the day before.

See how it works
Monthly

Find accounts with no login in 90 days

Once a month you get the users who haven't signed in for 90 days, ready for review.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Okta, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Okta automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Okta should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every 15 minutes, check the Okta system log for account lockouts, MFA resets and admin role changes, and alert me only when a user has three or more failed sign-ins from a new country.

When an Okta admin role is granted, post the user, the role and who granted it to our #security Slack channel.

Every Monday, list Okta users who have not signed in for 60 days, add them to Google Sheets, and create a Jira ticket asking IT to review deactivating them.

Beyond chat

Have Okta work when you're not in the chat

Connecting Okta to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Okta

Okta connects with an API token created by an admin in your org. The token acts with that admin's permissions.

Okta

Identity / IAM

  1. Sign in to the Okta Admin Console as the admin the token should belong to.
  2. Go to Security → API → Tokens and click Create token.
  3. Name the token and copy its value. Okta only shows it once.
  4. In the ClickRuntime dashboard, open Connections & secrets, save the token as a secret and enter your <yourOrg>.okta.com address.

Good to know

Okta limits that affect automations

  • The token has all the permissions of the admin who created it and can't be scoped down. Create it from an admin with the least access that still covers the automation.
  • A token expires after 30 days without use. Each call resets that clock, so a token used by a scheduled automation stays alive.
  • The token stops working if the admin who created it is deactivated.
  • Okta labels these tokens deprecated and recommends per-org OAuth service apps.

FAQ

Questions about automating Okta

What can ClickRuntime see in Okta?
Whatever the admin who created the token can see. The automations here read the System Log and search users. None of them change accounts.
How fast are lockout alerts?
The alert checks the System Log every 5 minutes and posts matching events, such as a lockout or an admin role being granted.
Will the token expire?
Only after 30 days without any calls, or if the admin who made it is deactivated. An automation that runs daily keeps it active.
Do these automations use AI?
No, they filter log events and user records directly. If you add a summary or other AI step, the AI comes with every ClickRuntime plan and you don't need your own key.
How is an inactive user found?
Users are searched by their last login date. The monthly report lists anyone with no login in the last 90 days.
Is this a Okta connector for ChatGPT or Claude?
Not for chatting with Okta data. A chat connector lets your assistant read and change Okta while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Okta event.

Related pages

Keep exploring

Tell your assistant what Okta should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude