Allow multiple hooks in one event rule and set their execution order #1178

New Issue

MrUnknownDE · 2026-04-05T21:31:15+02:00

MrUnknownDE commented

2026-04-05 21:31:15 +02:00

Originally created by @4ydan on 9/29/2025

NetBox version

v4.4.1

Feature type

Change to existing functionality

Proposed functionality

When creating an event rule, one can assign multiple webhooks and their execution order.

Replace single webhook dropdown with a sortable multi-select interface, making the execution order the sort order.
Add one field for delay between each webhook. The delay is the time when the webhook gets added to the rq.
Continue or not execution if one webhook fails? (also a checkbox maybe?)

Use case

I have multiple webhooks which trigger when VM's are updated, but it is important to me in which order they are executed. Also I would like to group these webhooks together in one event rule.

Currently I have to create multiple event rules with almost the same conditions and objects, which is also error prone when creating new event rules for new tenants etc...

Database changes

Modify the relationship between event rules and webhooks from one-to-one to one-to-many
Expand the webhook model to contain a field for execution_order
Migrate existing event rules: convert single webhook reference to the new many-to-many relationship with execution_order=0

External dependencies

*Originally created by @4ydan on 9/29/2025* ### NetBox version v4.4.1 ### Feature type Change to existing functionality ### Proposed functionality When creating an event rule, one can assign multiple webhooks and their execution order. - Replace single webhook dropdown with a sortable multi-select interface, making the execution order the sort order. - Add one field for delay between each webhook. The delay is the time when the webhook gets added to the rq. - Continue or not execution if one webhook fails? (also a checkbox maybe?) ### Use case I have multiple webhooks which trigger when VM's are updated, but it is important to me in which order they are executed. Also I would like to group these webhooks together in one event rule. Currently I have to create multiple event rules with almost the same conditions and objects, which is also error prone when creating new event rules for new tenants etc... ### Database changes - Modify the relationship between event rules and webhooks from one-to-one to one-to-many - Expand the webhook model to contain a field for execution_order - Migrate existing event rules: convert single webhook reference to the new many-to-many relationship with execution_order=0 ### External dependencies -

MrUnknownDE closed this issue

2026-04-05 21:31:15 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1178