Hi - we have a system in place wherein we collect ...
# ask-community
m
Hi - we have a system in place wherein we collect all state change events via webhook triggered by automations. We're collecting this data to identify and alert us if a flow run's duration is anomalous. It would be really helpful if we had the flow's parameters in the webhook payload, because these are the best indicator of how long a flow should run. It's not currently part of the default payload. Should I open an issue in the github repo?
z
Hey Mark, would it be reasonable to just query for the flow run after you've received this payload?
m
ya, that's definitely reasonable - just thought I'd ask
z
It's a helpful data point for us 🙂 feel free to open an issue so others can weigh in. I designed the automation events to be relatively lightweight though and I'm hesitant to pull additional data into them without some necessity.
My intention was to provide the ids and then the graphql API can be used to pull any structured/nested information that you need
m
got it - yea, that makes sense. It's easy to implement on our end so no problem