Deactivate User in Users (Okta )

What this operation does

Deactivate User

• POSTChanges data · Lifecycle Operationsokta.local/api/v1/users/{userId}/lifecycle/deactivate

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Users (Okta ) operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Users (Okta ) operations

• Create User in GroupPOST · changes data
• Clear User SessionsDELETE · changes data
• Suspend UserPOST · changes data
• Activate UserPOST · changes data
• Set Recovery CredentialPUT · changes data
• Unsuspend UserPOST · changes data
• Reset FactorsPOST · changes data
• Reset PasswordPOST · changes data

All 19 Users (Okta ) operations

Questions

Can HumDay deactivate user in Users (Okta )?

Yes. This operation is published in Users (Okta )'s own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Users (Okta ) data?

Yes — this is a POST operation, so it changes something in Users (Okta ). HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Users (Okta ) account.

Where this came from

Read from a published API description for Users (Okta ) at www.postman.com/collections/1755573c5cf5fbf7968b. The description above is the provider’s own wording, not ours. Last published 2021-07-05.