Skip to main content

[Workflow Builder - GCW] How to Configure Send to SFTP Activity

Anastasiia Zbrozhek avatar
Written by Anastasiia Zbrozhek
Updated over a week ago

When you want to securely upload the output of an imposition activity to a remote server, the Send to SFTP activity is your go-to option. This activity enables file transfer via the SFTP protocol, and it's commonly used after activities like imposition templates or other production steps that generate printable files.

This guide walks you through configuring both single and multiple file uploads using the Send to SFTP activity, including naming conventions, optional subfolders, and dry run behavior.


Setting Up a Single File Upload

Use this method when you're uploading just one file—typically the result of an imposition activity.

Step-by-step setup

  1. Add the Send to SFTP activity
    Drag and drop the activity into your workflow, typically after an imposition-related step.

  2. Choose single file mode
    In the activity settings, select the option for a single file.

  3. Specify the file to upload

    • Use the plate ID from the imposition or config activity.

    • Note: During a dry run, plate IDs may show as “none” because plates aren't actually generated until a live run. In a real run, valid plate IDs will be created automatically.

    • In the file input, enter url. This lets you select the result of the imposition activity.

  4. Validate the selected file

    • You can click on the provided URL to confirm it opens the correct file in a new tab.

  5. Define a unique file name

    • File names should contain a unique identifier, such as a print job ID or part ID.

    • If left blank, the system will use Gelato’s default naming convention (e.g., W01, followed by product SKU and details).

    • To customize, type something like Poster_PartID or just Poster.

  6. Optional: Add a subfolder path

    • If your SFTP destination contains subfolders, you can paste the desired path in the optional subfolder field to organize files within the main directory.

  7. Optional: Execute during dry run

    • By default, uploads are skipped during a dry run.

    • If you enable this checkbox, the system will send a file to your SFTP even during test runs.


Setting Up Multiple File Uploads

Use this method when you want to send a collection of files—for example, all the outputs from an imposition activity.

Step-by-step setup

  1. Switch to multiple file mode

    • In the Send to SFTP activity, select the multiple files option.

  2. Provide the files

    • Choose the output collection from your imposition activity. This is typically a list of plate files.

  3. Enter plate IDs

    • As with single files, reference the plate ID from the relevant activity.

  4. Name your files

    • Define a consistent and unique file naming pattern (e.g., use PartID_Poster).

    • This helps ensure clear identification once uploaded to the SFTP server.

  5. Optional: Add a subfolder path

    • As with single files, you can place the collection inside a specific subfolder by pasting the path.


Frequently Asked Questions

Can I use dynamic variables in file names?
Yes! You can include variables like {{PartID}} or {{PrintJobID}} to make filenames unique and informative.

What happens if I don’t provide a file name?
Gelato’s system will generate a standard file name, starting with W and followed by product details.

Is it safe to enable uploads during a dry run?
Enabling uploads during dry runs is helpful for testing, but make sure not to overwrite real production files.

Can I upload to nested subfolders in my SFTP?
Absolutely. Just paste the full path in the subfolder field (e.g., clients/posters/April).


📝 Not what you needed?

Help us improve this article, send us an email to [email protected] — please include the article title.

Did this answer your question?