Can you provide some more details... Is the script to be run by Splunk? Is the script in question generating the output already? How would you like to control the output?
If the script is external and is output results (e.g. via STDOUT/STDERR), then you should easily be able to re-direct this to file and have Splunk monitor this file, via the standard inputs.
If the script is to be run by Splunk (e.g. as scripted input), Splunk will index the STDOUT by default. You could also have your script write to file so that you can capture STDOUT and STDERR, and having a rolling log. You can apply this to have a script run by Splunk which will manipulate data that has already been generated by another process.
If you wish to add value/manipulate data that is already in Splunk, you can use custom scripted commands, which run a python/perl script to meet your needs.
The script would be run by Splunk. It is currently generating html output (includes images / tables / graphs). I would like to pull this into a view along side other views containing data from Splunk to create a single interface and retain the search capability of Splunk.