Home > Asset management > Webhooks > Review webhooks

Review webhooks

Last updated: 2026-11-03

Cadence: Weekly

Subscription model: All

Roles: Tenant Admin (TA)

Last verified: 2026-05

	Initial	Recurring
Estimated time	15 min	5 min

Benefits:

Surfaces users approaching the 150-per-user webhook limit
Catches failed deliveries before downstream integrations break
Confirms ownership concentration isn't a single point of failure

Goal

Webhooks are managed on the Webhooks page in the admin console. Permission paths:

Tenant Admin—manage all webhooks in the tenant.
Use webhooks permission—manage own webhooks only (non-admin users; also available as an OAuth scope).
Manage Webhooks permission—manage all webhooks (also available as an OAuth scope).

Webhook event history is retained for 7 days, after which delivery failures can't be reviewed in the UI.

As of November 2025, payloads use the CloudEvents 1.0.2 envelope. Type identifiers vary: most app lifecycle events dropped the v1 segment in April 2026 (for example, com.qlik.app.created), while reload-finished retains com.qlik.v1.app.reload.finished. Check the qlik.dev event catalog for canonical names.

Limits

150 webhooks per user (the documented per-user maximum)
7 days of event history retention

Tasks

Task	TA	AA	DA	AuA
Review failed deliveries in webhook history; resend or disable as needed	✓
Surface any user approaching the 150-per-user webhook limit, and check for ownership concentration that would create a single point of failure	✓

References

Tags: #weekly #asset_management #webhooks #qlik_automate

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here