Notification interceptor pattern

My use case for interceptors is to emit notifications based on activity results that occur within a workflow.

The notifications are a cross-cutting concern, not a part of the business/application domain.

I could put the notification logic in the workflow itself, but it would be nice to keep notification logic separate. Interceptors seem to support this use case.

I’ve read up on interceptors in various places (see below), but I don’t understand if, or how, an activity interceptor has an opportunity to use the result of an activity.

Are there any examples of intercepting the result of an activity, performing cross-cutting logic like issuing notifications based on the success or failure of the activity, and then returning the result of the activity to the workflow?

Many thanks!