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

Webhook integration for Reports #7066

New Issue
Closed
opened 2025-12-29 19:48:32 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:48:32 +01:00
Owner
Copy Link

Originally created by @PaulR282 on GitHub (Oct 4, 2022).

NetBox version

v3.3.4

Feature type

New functionality

Proposed functionality

It would be nice to be able to call a webhook after a report has finished. This would be achieved by adding Extras > Reports to the Content types when creating a webhook.

Use case

This is very useful when you want to evaluate the results of a report automatically.

Database changes

No response

External dependencies

No response

Originally created by @PaulR282 on GitHub (Oct 4, 2022). ### NetBox version v3.3.4 ### Feature type New functionality ### Proposed functionality It would be nice to be able to call a webhook after a report has finished. This would be achieved by adding `Extras > Reports` to the `Content types` when creating a webhook. ### Use case This is very useful when you want to evaluate the results of a report automatically. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:48:32 +01:00
adam closed this issue 2025-12-29 19:48:32 +01:00
adam commented 2025-12-29 19:48:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2022):

I don't think this is feasible: Webhooks are designed to track the creation, modification, and deletion of individual database objects as discrete events, and running a report doesn't map to any of these actions. However, it's also unnecessary. Because you have direct Python access within a report, you're free to generate arbitrary HTTP requests as needed using e.g. the requests library.

@jeremystretch commented on GitHub (Oct 4, 2022): I don't think this is feasible: Webhooks are designed to track the creation, modification, and deletion of individual database objects as discrete events, and running a report doesn't map to any of these actions. However, it's also unnecessary. Because you have direct Python access within a report, you're free to generate arbitrary HTTP requests as needed using e.g. the `requests` library.
adam commented 2025-12-29 19:48:33 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Oct 5, 2022):

It would be possible to enable webhooks for the JobResult model, which essentially provides the functionality he is requesting.

I had planned on implementing it here but got sidetracked #8958

@kkthxbye-code commented on GitHub (Oct 5, 2022): It would be possible to enable webhooks for the JobResult model, which essentially provides the functionality he is requesting. I had planned on implementing it here but got sidetracked #8958
adam commented 2025-12-29 19:48:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 5, 2022):

Ah, yeah that makes more sense. Looking at the history of #8958, I see that I applied the "needs milestone" tag after it was closed for going stale. I'm pretty sure the intent was to keep it open.

@jeremystretch commented on GitHub (Oct 5, 2022): Ah, yeah that makes more sense. Looking at the history of #8958, I see that I applied the "needs milestone" tag after it was closed for going stale. I'm pretty sure the intent was to keep it open.
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 type: feature
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#7066
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?