# Receive Flow Run Summary data in other places than email (via webhooks)

**URL:** <https://community.parabola.io/t/receive-flow-run-summary-data-in-other-places-than-email-via-webhooks/2443>\
**Category:** Feature Requests\
**Tags:** Other-Request\
**Created:** [July 29, 2022, 3:01pm UTC](https://community.parabola.io/t/receive-flow-run-summary-data-in-other-places-than-email-via-webhooks/2443 "2022-07-29T15:01:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Dawson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.parabola.io/brian_dawson/32/1454_2.png) [@Brian\_Dawson](https://community.parabola.io/u/Brian_Dawson)\
**Post date:** [July 29, 2022, 3:01pm UTC](https://community.parabola.io/t/receive-flow-run-summary-data-in-other-places-than-email-via-webhooks/2443/1 "2022-07-29T15:01:59Z")

</div>

My #1 feature request right now:

_1. What is your feature/integration request?_

An option to get a summary of the flow run as a webhook payload (in addition to existing email summary).

_2. What problem would this feature/integration solve?_

Would solve three issues:  
a.) Would allow for tracking success/failure of flow runs in other places besides email.

For example, sending the summary via webhook would allow another automation/flow to push that info anywhere, like a Slack channel.

Right now, you’d have to add tons of steps to catch all possible errors that could happen in a flow and get that sent to a Slack channel. Plus tons of reformatting and conditional if/thens for successful runs.

b.) Would allow for more customization of who receives summaries about flows.

For example, whatever is catching the webhook could _not_ notify an editor of the flow if desired. Or it _could_ notify a viewer of the flow.

(This would be even better if paired with the option to disable email summaries to flow editors)

c.) If the data came as a JSON payload in a webhook, it could be reformatted much more easily than what comes through via email. This would be good if you wanted to track all automation runs in a dashboard, Google sheet, or somewhere else.

_3. How do you solve/workaround this problem today?_

Theoretically could build an automation/flow to auto-forward the summary emails to somewhere else but this is very duct-tapey.

In the Slack example, I don’t think you can auto-forward email to a shared channel. You’d need to forward to another Parabola flow or something else that can post to a shared Slack channel.

I’ve seen many people allude to wanting functionality that this feature request would enable, but looks like no one ever actually made a feature request.

**So please upvote this request!**