Skip to main content

Hi Community,

 

I have a tricky situation with a webhook behaviour that I don't understand.

 

I have created an Action Flow starting with a webhook supposed to listen to any sollicitation.

 

First of all, I'd like to say that the way to instruct the Action Flow to use webhook entries a little bit stupid but ok, I did it, creating first the webhook with scheduling type = "Immediately", then published, ran the webhook, sent data under JSON format through API client, got my data received by the webhook, then added the other modules and mapped data received by the webhook into the CSV module (then map under base64 to send attached file in an email sent with a skill).

 

I then ran again the complete action flow, sending data the same way from API client. All worked fine, I received data inside CSV by email.

 

Now I created an actionable view to activate this action flow from a selected line in that view. To make it work, I created an action into the knowledge model but there, you have to switch the scheduling style of the action flow from "Immediately" to "On demand", otherwise the action button does not appear in the view.

 

And there lies the trick...data from the view are not transferred to the action flow, or are they, but the webhook is empty.

 

Anyone knows what I did wrong while I have the feeling that I have respected all best practices of this use case?

 

It defies all logic to me but reality is that I am stuck so any non-logical solution would be fine. :)

 

Thanks for your help.

 

CC

Answering on my own, for anyone who would be concerned.

 

Webhooks are not relevant in this use case. Plus, they prevent action flow from executing correctly in that same use case.

 

You need to create inputs to your Action Flow then go to your view and modify your action telling Celonis to map those inputs from selection in the view.

 

Replace first module of the Action Flow by anything else than a webhook but still one that is accepted as an entry module, and don't forget to precise that the Action Flow has to be executed On demand.

 

And you're good to go. Map your inputs wherever you need them in the Action Flow and that'll be working.

 

Webhooks should be kept for instant request where you will specifically call the generated URL from the sending entity to your Action Flow.

 

Hope this helps.


Reply