If the Hermes Agent webhook does not receive the event, first confirm that the external service can access your callback address, and then look at the signature, path, port, and gateway logs. Webhook Problems Don't doubt the agent's intelligence first, the first layer is usually that the HTTP request does not reach Hermes.
Verify that the request is not coming in first
Use hermes logs or gateway logs to see if there are any log of requests. If not, indicate that the problem is penetrating the domain, port, firewall, reverse proxy, or intranet. You need to first give the external platform access to the webhook endpoint exposed by Hermes.
Check the platform configuration again
- Whether the callback URL is written completely, including the protocol, path, and port.
- Whether the platform requires HTTPS and whether the certificate is valid.
- Whether the signature secret is consistent with the Hermes configuration.
- Whether the event type is checked, such as push, issue, comment, release.
What to do if you receive a request but no action
If you can see the request in the log, but Hermes doesn't reply or trigger the task, check the subscription rules, target platform, target session, and permissions. The webhook is just a "wake-up" entrance, and you need to know which agent, which session, and what tool to handle the event to.
It is recommended to test with minimal events, such as sending a test payload so that Hermes only replies "received". Confirm that the link is open and then let it perform complex automation. This separates network issues, signature issues, and agent logic issues.
