webhook-subscriptions

External webhooks trigger agent runs by POSTing events to a dedicated Moltis ingestion endpoint. You create webhook subscriptions for specific services so incoming event payloads automatically initiate automated agent orchestration without direct agent access.

Yes, webhook subscriptions work across common source profiles including GitHub, Stripe, GitLab, Linear, PagerDuty, Sentry, and generic sources. You can configure event filters and authentication modes to tailor exactly when and how agent runs start.

Event filtering and authentication are configured when creating or updating webhook subscriptions via RPC. You select a source profile, define event filters, choose authentication modes, and set session behavior to control how agent runs are triggered.

Webhook subscriptions include built-in deduplication and per-webhook rate limits to manage incoming event payloads. These built-in security features prevent duplicate agent runs and protect against event flooding from external services.

Existing webhook subscriptions are managed via RPC calls that support listing, updating, and deleting configurations. You can modify event filters, authentication modes, and session management settings for any active webhook subscription.

Webhook subscriptions require external services to support outbound webhooks and per-webhook rate limits apply. You must configure authentication modes and event filters correctly, as incorrect settings may prevent valid events from triggering agent runs.