starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow more granular filtering of webhooks #3760

New Issue
Closed
opened 2025-12-29 18:31:06 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:06 +01:00
Owner
Copy Link

Originally created by @arjenvri on GitHub (Jun 8, 2020).

Environment

  • Python version: 3.8.3
  • NetBox version: 2.8.4

Proposed Functionality

Webhooks are a great way to notify external systems using RESTAPI of a NetBox object change, but cannot be filtered to be more specific than an object type. Would it be possible add some basic filtering to trigger only for a specific site and/or tenant for example?

Use Case

  • Globally distributed DHCP and/or DNS servers that would receive a notification to update records for the site handled by the server.
  • Microsoft Teams/Slack notifications for objects in specific key sites or to different channels for different responsible parties.

Database Changes

N/A

External Dependencies

N/A

Originally created by @arjenvri on GitHub (Jun 8, 2020). ### Environment * Python version: 3.8.3 * NetBox version: 2.8.4 ### Proposed Functionality Webhooks are a great way to notify external systems using RESTAPI of a NetBox object change, but cannot be filtered to be more specific than an object type. Would it be possible add some basic filtering to trigger only for a specific site and/or tenant for example? ### Use Case * Globally distributed DHCP and/or DNS servers that would receive a notification to update records for the site handled by the server. * Microsoft Teams/Slack notifications for objects in specific key sites or to different channels for different responsible parties. ### Database Changes N/A ### External Dependencies N/A
adam added the status: duplicate label 2025-12-29 18:31:06 +01:00
adam closed this issue 2025-12-29 18:31:06 +01:00
adam commented 2025-12-29 18:31:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 8, 2020):

Duplicate of #4567

@jeremystretch commented on GitHub (Jun 8, 2020): Duplicate of #4567
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3760
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?