@craigappl, yes, @darius beat me too it. You can find a little background on report processors here, but essentially they represent code that can be configured to run automatically or on-demand after a report has finished running. Because reports are queued up and run asynchronously, and also because they can be scheduled to run based on a cron expression, it is often helpful to have an addiitional processing step that happens automatically once a report is run. There are currently a handful of built-in processors supported - one that can email out the report and one that can save the report to disk somewhere.
To add you own custom processor that would post the results of the report to a web service as a CSV, you would simply create a class that implements the ReportProcessor interface, and registers itself with Spring using the @Component annotation. Then, you’d need to ensure that this ReportProcessor is associated with any ReportDesigns that you configure for a given report.
Happy to answer any questions that arise if you go down this path.