[GH-ISSUE #871] [Feature]: Standardize Webhook Notification Payload Fields #592

New issue

Closed

opened 2026-05-07 00:11:57 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:11:57 +02:00

Owner

Originally created by @VREmma on GitHub (Apr 2, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/871

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

While working on getting some notification webhook automation setup the last few days, I noticed that the documentation says that the webhook payload format has certain fields, but they are not always there for all notifications. I was looking to do some automation on the event field data, using information from the printer name and filename, etc as seen in the Payload format: https://wiki.bambuddy.cool/features/notifications/#webhook-custom

However, Print Started, Print Complete, First Layer Complete, and progress notifications all do not have these fields. They only have title, message, and the image. It also appears the Maintenance Due notifications only have title and message to them, no event or printer.

Proposed Solution

I propose we get the webhook notification payload standardized across all the notifications (where applicable). This way every payload has the basics of the print job/task on hand, and the webhooks can parse the data without having to parse the message field for any data. We can keep the title and message in there, and it should not break any current notifications since its just a json payload we are adding more to.

Alternatives Considered

No response

Feature Category

Notifications

Priority

Nice to have

Mockups or Examples

Here is an example from n8n that shows that Print Completed doesn't send the other payload fields like the documentation suggests.

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @VREmma on GitHub (Apr 2, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/871 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case While working on getting some notification webhook automation setup the last few days, I noticed that the documentation says that the webhook payload format has certain fields, but they are not always there for all notifications. I was looking to do some automation on the event field data, using information from the printer name and filename, etc as seen in the Payload format: https://wiki.bambuddy.cool/features/notifications/#webhook-custom However, Print Started, Print Complete, First Layer Complete, and progress notifications all do not have these fields. They only have title, message, and the image. It also appears the Maintenance Due notifications only have title and message to them, no event or printer. ### Proposed Solution I propose we get the webhook notification payload standardized across all the notifications (where applicable). This way every payload has the basics of the print job/task on hand, and the webhooks can parse the data without having to parse the message field for any data. We can keep the title and message in there, and it should not break any current notifications since its just a json payload we are adding more to. ### Alternatives Considered _No response_ ### Feature Category Notifications ### Priority Nice to have ### Mockups or Examples Here is an example from n8n that shows that Print Completed doesn't send the other payload fields like the documentation suggests. <img width="598" height="459" alt="Image" src="https://github.com/user-attachments/assets/4370f511-bacd-40cd-939b-d47def289fab" /> ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-07 00:11:57 +02:00

closed this issue
added the
enhancement
label

BreizhHardware commented

2026-05-07 00:11:57 +02:00

Author

Owner

@maziggy commented on GitHub (Apr 2, 2026):

Available/Fixed in branch dev and available with the next release or daily build.

Can you please test and let me know how it goes? Thanks!

@maziggy commented on GitHub (Apr 2, 2026): Available/Fixed in branch dev and available with the next release or daily build. Can you please test and let me know how it goes? Thanks!

BreizhHardware commented

2026-05-07 00:11:57 +02:00

Author

Owner

@VREmma commented on GitHub (Apr 2, 2026):

Looks good so far! Just started 3 prints across 3 printers, and they all sent images and the other fields across the board so far. Will watch for it to progress through everything and make sure they are okay.

@VREmma commented on GitHub (Apr 2, 2026): Looks good so far! Just started 3 prints across 3 printers, and they all sent images and the other fields across the board so far. Will watch for it to progress through everything and make sure they are okay.