Automatically integrate CS-Scripts with PDF conversion

Another way to think of the CS-Script action is as a bridge between PDFCreator and your own business logic. Instead of manually running extra steps after conversion, you can automate them directly inside your workflow. 

You decide when your script runs: 

• Before conversion: to check file properties or adjust metadata 
• After conversion: to rename, move, or upload the finished PDF document 

Here are a few ways businesses use the CS-Script action every day: 

• Quality checks: Cancel or tag print jobs that don’t meet naming rules or metadata standards.
• Automatic uploads: Push completed PDFs to a DMS, cloud folder, or internal API.
• Custom logging: Keep detailed conversion records for audits or billing.
• Post-processing: Apply compression, password protection, or further editing tools automatically.

Essentially, if you’ve ever thought “I wish PDFCreator could do X when a job finishes”, you can probably achieve it with CS-Script. 

Once you enable the action in the profile settings, PDFCreator looks for your script file (usually in the “CS-Scripts” folder). 
When a job starts, PDFCreator: 

1. Loads and compiles your script. 
2. Hands it the current print job’s details. 
3. Executes your pre- and post-conversion methods. 

You can then access properties like filenames, output paths, tokens, and metadata, allowing your code to modify, validate, or trigger additional steps. 

Here’s a minimal template showing how a script might look: 

using System; 
using NLog; 
using pdfforge.CustomScriptAction; 
using pdfforge.PDFCreator.Conversion.Jobs.Jobs; 
 
public class MyScript : IPDFCreatorScript 
{ 
    public ScriptResult PreConversion(Job job, Logger logger) 
    { 
        job.JobInfo.Metadata.Author = "Marketing"; 
        return ScriptResult.Success; 
    } 
 
    public ScriptResult PostConversion(Job job, Logger logger) 
    { 
        logger.Info("Files created: " + string.Join(Environment.NewLine, job.OutputFiles)); 
        return ScriptResult.Success; 
    } 
} 

In this example, the script adds a default author before conversion and logs the output path afterward. 

The CS-Script action is one of PDFCreator’s most flexible tools. It saves hours of manual post-processing, integrates easily into existing systems, and scales perfectly for automated workflows. 

If you’re using one of PDFCreator’s Business editions, we strongly suggest you give it a try. Open your profile settings, enable CS-Script, and see how much smarter your PDF workflows can become. 

The CS-Script action can be enabled in the advanced section of the queue settings. Your script file must be located in the CS-Scripts folder and has to be a .cs or .csx file. To automatically integrate them as part of the workflow (action) feature in PDFCreator, here is what you need to do: 

1. Open PDFCreator 
2. Go to the "Profiles" tab to select the "Automatic saving mode" 
3. Click on “Add action” and select “CS-Script” 
4. Select and check your CS-Script and click on “OK” 

Now your CS-Scripts will automatically be integrated in the workflow when converting your print jobs.