Not sure the right level of detail for an answer. I would suggest that you engage the professional services group if you are looking for more in depth information.
In any case, here's a bit of a high level answer.
FFCore hot folders support use of manifests (csv files) to drive production. When a manifest is received, FFCore will parse the data columns in the csv file per the hot folder configuration and submit the job to the selected workflow (or use the routing rules to automatically select a workflow for the job in each manifest row)
The manifest fields are configured in the Hot Folder Setup tab.
We have a few "Standard fields" which are used to control job submission from the manifest.
You can also add custom fields so set additional variables with information from the manifest
After a manifest is parsed, FFCore will use the configuration in the Workflow Destinations to automatically select a workflow
If you enable hot folder scripting then FFCore will execute the confired script before any other processing is done by the hot folder.
The configuration itself is pretty straight forward
Under the hood FFCore will concatenate the path to the script along with the parameters and execute the script as if it was executed from the CLI. There are no requirements on the script itself. If you can get it working from the CLI then you can configure it to execute when a file is dropped into the hot folder. The only requirement that the script output a valid job file and place it at the location defined in the $$out$ variable. The file does not have to be a manifest but that is what most customers implement.