Hey all,
I’m trying to use a webhook from an event based gateway like so:
However, when I deploy the diagram the webhook is converted into a message catch event.
At first, I thought this was a visual bug. However, when I try to activate the webhook, I receive a 404 which leads me to believe it really has become a message catch event.
Was this intended behavior?
Hi @David-Rach,
The Webhook is a specialization of the Message Event: The Webhook connector, will send a message to the process. Operate is probably displaying it as a message receive event because it’s unaware of the connector implementation.
Therefore, I assume that the problem is with the connector. To narrow it down, can you please answer the following questions:
– Stephan
I’m using Camunda 8 Self-Managed (Platform version 8.2.7) with the connectors bundle (version 0.20.2).
Information about the webhook is as follows:
“name”: “Webhook connector”,
“id”: “io.camunda.connectors.webhook.WebhookConnectorIntermediate.v1”,
“version”: 3,
And an example diagram.
example.bpmn (7.8 KB)
I’m using docker to spin up the environment and have the connectors port exposed on my host machine as 8085. To hit the webhook, I use localhost:8085/inbound/webhook_id but receive a 404.
Curious. Seems the example I’ve provided is misleading.
I’ve found the webhook only fails if its inside of a sub-process. The example I provided actually works as it exists outside.
Any clue as to why the webhooks would fail inside a sub process?
Finally managed to find a configuration that works.
The activity call is necessary. I’m not quite exactly sure why, but my guess is because the call activity kicks off a new process all together where as having the escalation going directly to the event based gate doesn’t.
Even if the above diagram doesn’t kick off a new process, I would have thought the webhook would still be callable.
