FR: Pass enrollment user info in webhook #45

New Issue

michael · 2026-01-19T18:31:20Z

michael commented

2026-01-19 18:31:20 +00:00

Originally created by @Uggbert on GitHub.

Hi

Would it please be possible to capture and pass the following info in the webhook:

Send the below during onstart webhook

capture the email address of the user who enrolled the device (we use Enrolment Customisation and EntraID)
Device Name
Building
Room

The device and location would need an additional key to cause the webhook to wait and line up with 'wait for user entry'

with the default action being false for those who dont want to wait for any reason.

Originally created by @Uggbert on GitHub. Hi Would it please be possible to capture and pass the following info in the webhook: Send the below during onstart webhook - capture the email address of the user who enrolled the device (we use Enrolment Customisation and EntraID) - Device Name - Building - Room The device and location would need an additional key to cause the webhook to wait and line up with 'wait for user entry' <delaywebhook> <true> with the default action being false for those who dont want to wait for any reason.

michael added the enhancement label 2026-01-19 18:31:20 +00:00

michael closed this issue

2026-01-19 18:31:20 +00:00

michael commented

2026-01-19 18:31:20 +00:00

@Uggbert commented on GitHub:

https://github.com/jamf/Setup-Manager/issues/143

Done

@Uggbert commented on GitHub: https://github.com/jamf/Setup-Manager/issues/143 Done

michael commented

2026-01-19 18:31:20 +00:00

@scriptingosx commented on GitHub:

I agree that the customized enrollment user ID needs to be added to both the started and finished web hook

The user entry data (including device name, Building and Room) is already part of the finished web hook. However, I do not like the idea of deferring the started web hook to after user entry. What I think would be a better solution is to have an additional web hook during waitForUserEntry when that action is present?

@scriptingosx commented on GitHub: I agree that the customized enrollment user ID needs to be added to both the started and finished web hook The user entry data (including device name, Building and Room) is already part of the finished web hook. However, I do _not_ like the idea of deferring the started web hook to after user entry. What I think would be a better solution is to have an additional web hook during `waitForUserEntry` when that action is present?

michael commented

2026-01-19 18:31:20 +00:00

@Uggbert commented on GitHub:

Ah yes an additional webook that fires after user input is a good idea!

On Mon, 18 Aug 2025, 08:18 Armin Briegel, @.***> wrote:

scriptingosx left a comment (jamf/Setup-Manager#140)
https://github.com/jamf/Setup-Manager/issues/140#issuecomment-3195427497

I agree that the customized enrollment user ID needs to be added to both
the started and finished web hook

The user entry data (including device name, Building and Room) is already
part of the finished web hook. However, I do not like the idea of
deferring the started web hook to after user entry. What I think would be a
better solution is to have an additional web hook during waitForUserEntry
when that action is present?

—
Reply to this email directly, view it on GitHub
https://github.com/jamf/Setup-Manager/issues/140#issuecomment-3195427497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMF7CIEKMYWUM4VZLIXXEPL3OF425AVCNFSM6AAAAACDH7GZ3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJVGQZDONBZG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

@Uggbert commented on GitHub: Ah yes an additional webook that fires after user input is a good idea! On Mon, 18 Aug 2025, 08:18 Armin Briegel, ***@***.***> wrote: > *scriptingosx* left a comment (jamf/Setup-Manager#140) > <https://github.com/jamf/Setup-Manager/issues/140#issuecomment-3195427497> > > I agree that the customized enrollment user ID needs to be added to both > the started and finished web hook > > The user entry data (including device name, Building and Room) is already > part of the finished web hook. However, I do *not* like the idea of > deferring the started web hook to after user entry. What I think would be a > better solution is to have an additional web hook during waitForUserEntry > when that action is present? > > — > Reply to this email directly, view it on GitHub > <https://github.com/jamf/Setup-Manager/issues/140#issuecomment-3195427497>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AMF7CIEKMYWUM4VZLIXXEPL3OF425AVCNFSM6AAAAACDH7GZ3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOJVGQZDONBZG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

michael commented

2026-01-19 18:31:20 +00:00

@scriptingosx commented on GitHub:

can you split this out into separate issue? (I could do it, but you create it, you will get notifications when I update it)

@scriptingosx commented on GitHub: can you split this out into separate issue? (I could do it, but you create it, you will get notifications when I update it)

michael commented

2026-01-19 18:31:20 +00:00

@scriptingosx commented on GitHub:

enrollmentUserID is part of the webhook data in v1.4beta

@scriptingosx commented on GitHub: `enrollmentUserID` is part of the webhook data in [v1.4beta](https://github.com/jamf/Setup-Manager/releases/tag/v1.4beta)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: jamf/Setup-Manager#45