Use this page when MeshAgent needs to call your service or toolkit over the webhook transport. This is different from standard project webhooks. For project event delivery such asDocumentation Index
Fetch the complete documentation index at: https://docs.meshagent.com/llms.txt
Use this file to discover all available pages before exploring further.
room.started or storage.file.updated, see Projects > Webhooks.
When to use WebhookServer
Use WebhookServer when your endpoint needs:
- built-in signature verification
- a default
GET /health check - a default
POST /webhookhandler - support for
room.callhandoffs, including websocket upgrades
What room.call sends
For room.call, MeshAgent sends:
room_nameroom_urltoken- optional
arguments
Configure webhook verification
Set the webhook secret if you want the server to verify signed requests:validate_webhook_secret=False.
Run WebhookServer
The built-in server listens on port 8080 by default and exposes:
GET /for health checksPOST /webhookfor webhook deliveryGET /webhookfor websocket upgrades used byroom.call
room.call:
Standard project webhooks
If you just want MeshAgent to notify an external system about project events, you do not needWebhookServer.
Create a standard project webhook instead: