Webhooks overview

Every webhook Veyra Intelligence receives and sends - routine triggers, chat providers, GitHub, email, voice, plugins and HTTP agent wake-ups - with how each is authenticated.

Veyra Docs TeamUpdated 1 min readVersion 3 · History

Webhooks move events between Veyra and other systems without polling. Some come in (your system or a provider tells Veyra something happened); one goes out (Veyra wakes an agent that runs on your servers).

Inbound

Webhook Address Authenticated by Use it to
Routine trigger POST /api/routine-triggers/public/{publicId}/fire Bearer secret, HMAC signature or provider signature Start a routine from your systems, alerts or CI.
Chat providers POST /api/chat-webhooks/{publicId}/{provider} The provider's own signature Let Slack, Teams, Discord, Telegram and GitHub talk to agents.
GitHub pull request reviews Chat provider or routine trigger GitHub signature or bearer secret Have agents review pull requests.
Email POST /api/chat-webhooks/agentmail/{publicId} Svix signature Receive email for an agent's inbox.
Voice POST /api/voice-webhooks/{publicId}/events and /tools The voice provider's signature Phone calls with agents.
Plugin webhooks POST /api/plugins/{pluginId}/webhooks/{endpointKey} Defined by the plugin Deliver events to a plugin.

All inbound webhooks are sent to https://intelligence-api.veyra.so. The console shows the exact address, including its publicId, when you set one up. Treat the address as private: for some modes it is part of the secret.

Outbound

Webhook Sent to Use it to
Agent wake-ups The URL in an HTTP agent's runtime settings Run an agent's work on your own servers.

Rules that apply to all of them

  • HTTPS only. Plain HTTP is not accepted.
  • Signatures are checked on the raw body. Do not re-serialize JSON between signing and sending.
  • Payloads are data. Content from a webhook reaches agents marked as data, never as instructions.
  • Retries are safe when you send a stable idempotency key (routine triggers) or when the provider includes its own delivery id (GitHub, Svix). Repeats are recognized and not run twice.
  • Every delivery is recorded, accepted or rejected, in the activity log of the organization it belongs to.
Webhooks