Authenticator Deactivated
Trigger a flow when an authenticator is deactivated in Okta.
Output
Field | Definition | Type |
---|---|---|
Date and Time | Date and time that the event was triggered in the Okta API. | String |
Message | Message details about the event. | String |
Event ID | Unique identifier of the event. | String |
Event Type | Type of event that was published. | String |
Event Time | Timestamp when the notification was delivered to the service. | String |
Version |
Versioning indicator. |
String |
Admin | Object | |
ID | Unique identifier of the Okta admin who deactivated the authenticator. | String |
Alternate ID | Email address of the Okta admin. | String |
Display Name | Display name of the Okta admin. | String |
Type | Role of the Okta admin. | String |
Authenticator | Object | |
ID | Unique identifier of the deactivated authenticator. | String |
Alternate ID | Alternate ID of the deactivated authenticator. | String |
Display Name | Display name of deactivated authenticator. | String |
Type | Type of the deactivated authenticator. | String |
UUID | Webhook event's universal unique identifier. | String |
Event Details | Raw JSON payload returned from the Okta API for this particular event. | Object |
Headers | Object representing the headers for the response; each key of the header will be parsed into a header string as "key: value" (Content-Type: text/plain ). |
Object |
Source | Source of user-specific data. | Object |
Debug Context | ||
Debug Data | Information on the triggered event used for debugging. For example, returned data can include a URI, an SMS provider, or transaction ID. | Object |

While you can create additional user or group fields for an Okta event, the Okta API only supports four fields for Okta connector event cards: ID, Alternate ID, Display Name, and Type. Values will be returned for these four input fields only. No other fields are supported for users or groups, and data from such fields will not be returned by this event card.