<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009xSYXSCA4Okta Identity EngineWorkflowsAnswered2026-04-03T09:00:22.000Z2024-02-02T09:09:32.000Z2024-02-03T00:35:20.000Z
  • 3dl5q (3dl5q)

    Our current means for achieving this is through a workaround where after a user is activated an Okta workflow pauses the assignment of apps and groups for 6 hours that should line up with Mimecast's scheduled directory sync that cant be adjusted or controlled manually.

  • Hello @3dl5q (3dl5q)​ Thank you for reacting out to our Community!

     

    Technically speaking this might be doable, but there are a lot of dependencies and certain requirements from Mimecast API. Workflows has an API Endpoint that can listen for requests from services. If Mimecast has a web/event hook type functionality that can monitor for an event that meets the condition you want to monitor and can deliver a payload to Workflows this would invoke a Workflows execution and you could “do something” at that point.

    For this use case to be viable there needs to be some sort of automated means for the required criteria to be made. And Mimecast must have API endpoints that allow the functionality you want to perform.

     

    Community members help others by clicking Like or Select as Best on responses. Try it today.

     

    Earn Today: New Okta Community Badges Have Arrived

     

    Subscribe Today: The Okta Community is on YouTube

    Expand Post
This question is closed.
Loading
Okta / Mimecast API Integration for Directory Sync