User Okta Profile Updated
Trigger a flow when an user's Okta profile is updated.
|Date and Time
|Date and time the event was triggered in Okta API.
|Message details about the event.
|Event's unique identifier key.
|Type of event that was published.
|Legacy Event Type
|Type of legacy event that was published.
|Timestamp when the notification was delivered to the service.
|Webhook event's universal unique identifier.
|Severity of the event; one of:
|Outcome of the update; one of:
|List of attributes that were updated.
|ID of the Okta actor who performed the update.
|Email address of the Okta actor.
|Display name of the Okta actor.
|Type of data returned.
|ID of the Okta user whose profile was updated.
|Email address of the Okta user.
|Display name of the Okta user.
|Type of Okta user.
|Client that requested the update.
|Transaction details for the update.
|Information on the triggered event used for debugging; for example, returned data can include a URI, an SMS provider, or transaction ID.
|Authentication data for the update; includes the update's remote address and session ID.
|Security data for the update.
|Raw JSON payload returned from the Okta API for this particular event.
|Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (
|Source of user-specific data.
While you can create additional user or group fields for an Okta event, the Okta API only returns values for four fields: ID, Alternate ID, Display Name, and Type.
No other fields are supported for users or groups, and data from such fields isn't returned by this event card.