Webhooks

Receive event notifications for automation and integrations.

Outbound product webhooks are planned to let your systems react to WeKeKe events in real time. Inbound provider webhooks (for example Telegram message delivery) are already used internally by integrations.

Status

  • Outbound webhook events are not yet fully published.
  • Payload schema and signing for outbound events are under review.
  • Inbound provider webhook handling is active in supported integrations.

Common event types

  • Rule run started / completed.
  • Integration connected / disconnected.
  • Automation error or validation failure.

Endpoint checklist

  • Use HTTPS with a valid certificate.
  • Validate payloads and reject unknown sources.
  • Respond quickly to avoid retries.

Retries and idempotency

Design your webhook handler to be idempotent so retries do not create duplicates. Store event IDs and ignore repeats.