Source validation
Webhook tokens, PagerDuty signatures, mailbox filters, message size controls, and source history protect intake quality.
Inbounds are the entry points for alerts, incidents, events, email, chat channels, and voice lines. They decide how external signals enter OpsRabbit, which tenant and agent receive them, and which source-specific controls apply before investigation starts.

What this page covers
Support Datadog, generic webhooks, PagerDuty, Jira, Zoho, email polling, chat channels, SIP voice, and media-stream voice patterns.
Assign each inbound to an agent and use named instances for customer, environment, or source-specific routing.
For voice, enable the assigned agent voice profile and configure disclosure, handoff, timing, tools, and knowledge permissions there.
Operational detail
Inbounds are the entry points for alerts, incidents, events, email, chat channels, and voice lines. They decide how external signals enter OpsRabbit, which tenant and agent receive them, and which source-specific controls apply before investigation starts.
Webhook tokens, PagerDuty signatures, mailbox filters, message size controls, and source history protect intake quality.
Provider-default or named instance webhooks resolve to an inbound instance, assigned agent, tenant, and investigation thread.
Voice SIP and media-stream inbounds can route live calls through approved realtime providers when licensing and agent voice settings allow it.
Related pages