Select to view content in your preferred language

Webhook Configuration Wizard

618
3
04-09-2024 11:28 AM
KevinWyckoff1
Occasional Contributor

You can configure Portal to send email on your behalf, and Webhook functionality has been introduced. However, configuring webhooks can be highly technical and hard to create based on differences in architecture. I think my main use case for Webhooks is common enough to warrant adding as a function in Portal. 

I have a referenced feature class that field staff use to collect data on new assets and errors in existing features. I have worked to build a webhook workflow that will notify me when new features are created. My idea is that this functionality should be easier and configurable within the Portal GUI.

3 Comments
LindsayRaabe_FPCWA

Yes please! Webhooks are still a bit of a mystery to me. One day I'll dive in proper and figure it out as I'm sure we are missing out on opportunities to improve our workflows,m especially regarding feature creation/update/deletion notifications. 

KevinHibma

@KevinWyckoff1 - For the sake of clarity, can you expand on what exactly you'd like to see streamlined or simplified? You mention webhooks and emails and difficulty configuring the webhooks. Are you looking for a way to have the webhook trigger an email? If I'm missing the ask, can you please provide more information?

KevinWyckoff1

@KevinHibma my hope is for something more out of the box to have a webhook trigger an email, or post to a Teams Channel. There are enough organizations that use Outlook/Office365 for email that a wizard for creating and email would make sense. My main use case is wrapped around notifying members of my organization when new features are created or specific attribute changes are made.

I can give a couple examples of perfect world functionality to illustrate. When a new fire hydrant is installed, field staff use GPS to create a point feature. With a webhook we could notify the GIS Department and Fire Department. Another example is from our inspection work where we have coded domains for issues identified. Some issues are handled by the Customer Service Department, and others by the GIS Department. It would be great to notify the appropriate department when that attribute is changed to a pertinent code.