Hey Koji, thank you. I did in fact end up using ExtractText. I missed that processor on my first pass.
I think I was just expecting some kind of standard in how processors are designed. For instance, InvokeHttp and EvalutateJsonPath are processors that produce output and give you the option of whether the output should go in an attribute or be written to FlowFile content. Processors that read data should give you the option of reading from nifi a property supporting nifi expression language or from the FlowFile content. So ExtractText lets us write attributes from the content and ReplaceText lets us match the entire contents are replace with some expression language. Thanks, Nick On Tue, May 8, 2018 at 5:28 PM, Koji Kawamura <[email protected]> wrote: > Hi Nick, > > You may find ExtractText useful to extract string from FlowFile > content into FlowFile attribute. > E.g. MonitorActivity -> ExtractText -> PutSlack > > Thanks, > Koji > > On Wed, May 9, 2018 at 9:03 AM, Nick Carenza > <[email protected]> wrote: > > Hey all, > > > > I can't find a way to send messages with PutSlack from the > MonitorActivity > > processor. MonitorActivity only writes to content and PutSlack only reads > > from attributes and expression language doesn't provide a way to bridge > the > > two. What is the best way to make these processors communicate? > > > > Thanks, > > Nick >
