Overview
Webhooks let MeshAgent notify your systems when events occur. Instead of polling, you register a webhook URL (from MeshAgent Studio) and MeshAgent delivers event payloads in real time. Common uses:- Trigger a workflow when a room starts or ends.
- Sync files to an external system.
- Kick off automation when specific events happen in a room.
Event types
MeshAgent emits a small set of core webhook events. You can subscribe to specific events or use* to receive all.
room.started- Room session started. Payload includesroom_name.room.ended- Room session ended. Payload includesroom_name.storage.file.updated- File written or updated. Payload includespathandparticipant_id.storage.file.deleted- File deleted. Payload includespathandparticipant_id.*- Receive all events.
Payload format
Webhook requests are sent as JSON:Delivery and verification
If you set a webhook secret, MeshAgent signs each request and sends aMeshagent-Signature header.
- The header value is
Bearer <jwt>. - The JWT contains a SHA-256 hash of the payload.
- The SDK
WebhookSerververifies the signature automatically when a secret is set.
Built-in WebhookServer
MeshAgent provides a helper server so you can focus on handling events. It listens on port8080 by default and exposes:
GET /for health checks.POST /webhookfor webhook delivery.