# Capture output of notification block in pipeline for logging purposes

**URL:** <https://forum.inductiveautomation.com/t/capture-output-of-notification-block-in-pipeline-for-logging-purposes/72636>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [April 19, 2023, 11:41am UTC](https://forum.inductiveautomation.com/t/capture-output-of-notification-block-in-pipeline-for-logging-purposes/72636 "2023-04-19T11:41:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![liam1](https://avatars.discourse-cdn.com/v4/letter/l/e68b1a/32.png) [@liam1](https://forum.inductiveautomation.com/u/liam1)\
**Post date:** [April 19, 2023, 11:41am UTC](https://forum.inductiveautomation.com/t/capture-output-of-notification-block-in-pipeline-for-logging-purposes/72636/1 "2023-04-19T11:41:21Z")

</div>

Hi everyone,

I'm attempting to create an SMS logging function for the notification pipeline for all SMSs sent out. I want to log this information into a database.

Is there a return object generated by the notification block that contains all the information used when creating the SMS to be sent out? (Direct Roster Type)

I could like to attach a scripting block to the output of the notification block and capture this information for logging purposes.

If this is not possible I can obviously convert the notification block's roster type to calculated and do this in scripting.

The goal is to use this scripting block as a logging function in other pipelines, meaning it should be easy to copy, maintain, and extend.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 19, 2023, 3:08pm UTC](https://forum.inductiveautomation.com/t/capture-output-of-notification-block-in-pipeline-for-logging-purposes/72636/2 "2023-04-19T15:08:30Z")

</div>

No, the notification block doesn't return anything. Notifications are async, at that point; there's no guarantee the notification even succeeded before the pipeline continues (since blocking the pipeline on something like an SMTP server configured with no timeout would be bad).