Bring Okta activity into Coherence
Start from a supported Okta event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Event
Finishes with
Create or update a Coherence record

Okta currently provides 1 trigger that can start a workflow and 10 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Event
Fires when a new Okta event is generated
Create User
Creates a user without credentials and sends account creation prompt via email
Activate User
Activate a previously deactivated or pending user
Deactivate User
Deactivate (disable) a user in Okta
Suspend User
Temporarily suspend a user in Okta
Add User to Group
Add a user to a specific Okta group
Remove User from Group
Remove a user from an Okta group
Update User
Update user profile information
Find User by Email
Look up an Okta user by their email address
Find Group by Name
Search for an Okta group by name
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Okta event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Event
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Okta action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create User
Combine Okta with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Event
Finishes with
Create User, then preserve the outcome in Coherence
The exact authentication fields depend on Okta. The workflow structure stays straightforward:
Authorize the Okta account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Okta or provide a complementary trigger or action.
Okta currently provides 1 trigger that can start a workflow and 10 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Okta currently lists 1 trigger and 10 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Okta triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.