<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
0D54z00009zqm9ICAQOkta Identity EngineWorkflowsAnswered2026-06-04T21:42:56.000Z2024-02-09T11:52:29.000Z2026-06-04T21:42:56.000Z

b3oku (b3oku) asked a question.

Workflows not turning on.

So my Workflows are not turning on after successfully making connections to apps and configuring the connections. I get an error message in red at the bottom left saying "Cannot Activate flow, Webhook registration failed." I currently do not have any event hooks but I am confused as to if I actually need an event hook to use workflows because all the example I see online with configuring workflows, there are not any that states I need to configure a Webhook ( Event or Inline) before successfully using workflows. Please help thank you. If you can find a video that solves the problem as well I would be forever grateful.


  • TimL.58332 (Workflows)

    @b3oku (b3oku)​ -- Based on your description you have a card in the "Event" slot of the flow. The card is most likely a third-party vendor.

     

    The Event Slot essentially has 2 types of third-party cards:

     

    • API Endpoint + Event/Webhook setup
    • Scheduled + Polling of third-party API for data

     

    In your instance it will be the "API Endpoint" variety that sets up an Event/Webhook on flow enable (and removes it on flow disable). So when you attempt to turn the flow on it is making a call to the third-party. The setup of the Event/Web hook is failing causing the flow enablement to fail.

     

    A pretty common misunderstanding is that Workflows "monitors" something. Workflows doesn't "monitor" anything. In all of these situations Workflows is either invoking due to being an API endpoint and a payload was received OR because on a set schedule it was told to invoke (then do something).

     

    The reason I have mentioned this is for clarity on why you are seeing your error. The built-in cards are designed for ease-of-use by reducing the amount of steps needed for setup. For the Event cards it combines "Setting up an API Endpoint" && Setting up a "Web/Event" Hook pointing to the API Endpoint (and potentially some other processing logic of the received payload to list values in the pre-mapped fields)

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    @b3oku (b3oku)​ -- Based on your description you have a card in the "Event" slot of the flow. The card is most likely a third-party vendor.

     

    The Event Slot essentially has 2 types of third-party cards:

     

    • API Endpoint + Event/Webhook setup
    • Scheduled + Polling of third-party API for data

     

    In your instance it will be the "API Endpoint" variety that sets up an Event/Webhook on flow enable (and removes it on flow disable). So when you attempt to turn the flow on it is making a call to the third-party. The setup of the Event/Web hook is failing causing the flow enablement to fail.

     

    A pretty common misunderstanding is that Workflows "monitors" something. Workflows doesn't "monitor" anything. In all of these situations Workflows is either invoking due to being an API endpoint and a payload was received OR because on a set schedule it was told to invoke (then do something).

     

    The reason I have mentioned this is for clarity on why you are seeing your error. The built-in cards are designed for ease-of-use by reducing the amount of steps needed for setup. For the Event cards it combines "Setting up an API Endpoint" && Setting up a "Web/Event" Hook pointing to the API Endpoint (and potentially some other processing logic of the received payload to list values in the pre-mapped fields)

    Expand Post
    Selected as Best
  • TimL.58332 (Workflows)

    One last add - It not turning on is likely due to permissions for the setup connection for the third-party. That is most often the case. While you can't see the response back from the vendor on the front-end on the back-end it is usually a 403.

  • YasmaryD.74381 (Customer)

    @b3oku (b3oku)​ make sure you have both the okta.eventHooks.manage and okta.eventHooks.read scopes assigned in the Okta Workflows OAuth application. You will need both of these to ensure that Okta can pull the workflow webhooks (it does behind the scenes) and then register the webhook for your particular event. I noticed that these scopes are also needed when you turn a flow OFF and back ON again. Hope this helps!

    Expand Post
This question is closed.
Loading
Workflows not turning on.