# InsightOps

Source: /docs/raptor-mcp/insightops

Configure InsightOps sources, templates, verified channels, schedules and event delivery on a customer-managed Raptor Gateway.

## Prepare a source and a delivery channel

InsightOps runs on your Gateway. It can use Qlik visualizations, expressions, reload state, alerts and bounded data queries as sources. Agent-based schedules also require an administrator-configured model provider and the appropriate app access. Sources must match the connected Cloud or Qlik Sense on Windows environment.

An administrator configures and verifies the permitted delivery targets. Supported adapters include Teams, Slack, email, Telegram, webhooks and an archive target. Each adapter needs its own service configuration, such as an incoming webhook or SMTP connection. Store those credentials in Gateway administration, outside prompts and Qlik objects.

## Preview before enabling a schedule

Start with a question the recipient can act on: a failed reload, an overdue approval or a measure crossing an agreed threshold. Choose a built-in template and validate its exact app, object or expression source. A preview can check message content without sending to a channel.

1. Discover the available InsightOps templates and approved channel targets.
2. Validate the source against live Qlik access. A configuration-only preview does not prove the source can be read.
3. Preview the message and check its facts, period, severity, owner and source links.
4. Create the schedule as a draft, with the intended recipient and timing.
5. Perform an explicitly authorized test delivery, inspect its history, then enable the schedule.
6. Review delivery failures, acknowledgements and source access as part of normal operations.

- Manual delivery defaults to preview. Sending requires an explicit request and a verified channel target.
- The schedule owner needs continuing access to the source. A successful preview does not guarantee future access or freshness.
- A provider accepting a message is delivery evidence from that provider; it does not establish that the recipient read it.

## Events and operational checks

Event-triggered schedules can consume Qlik Cloud webhooks or QSEoW QRS notifications through the Gateway's signed event receiver. The receiver is disabled in the packaged example until an administrator configures event delivery, signing keys and the reachable endpoint. Saving a subscription alone does not configure Qlik to send events.

Keep the Gateway running for scheduled processing. Administrators should check scheduler configuration, source permissions, channel credentials and delivery history when a message is missing. Workflow reminders and escalation messages also depend on their approved workflow definitions and monitoring rules.

## Related Links

- [Qlik connections](/docs/raptor-mcp/qlik-connections)
- [Users and roles](/docs/raptor-mcp/users-and-roles)
- [Writeback and workflows](/docs/raptor-mcp/writeback-and-workflows)
- [Updating and maintenance](/docs/raptor-mcp/updating-and-maintenance)