Skip to main content

Smart fields in the Upload file to SFTP action

Which smart fields you can type in the folder path, the file name and the metadata file of an SFTP upload.

In the Upload file to SFTP workflow action, you can type smart fields in four places: the folder path, the file name, the metadata template and the metadata file name. When the workflow runs, Kolleno replaces each smart field with the value of the record.

How to type a smart field

Type the smart field between double curly brackets, for example {{ customer.ref }}. The file name Reminder {{ customer.ref }} becomes Reminder C-1042.pdf.

Smart fields of the record

You can use the same smart fields as in the API call action. They depend on the workflow level. For example, {{ customer.name }} works on every level, {{ invoices.0.ref }} on an invoice workflow, and {{ email_sent.subject }} on an email sent workflow.

Smart fields of the uploaded file

In the metadata template and the metadata file name, you can also use these smart fields. They describe the main file that Kolleno uploads:

  • {{ sftp_file.name }}: the name of the file on the SFTP server, for example INV-1042.pdf.

  • {{ sftp_file.size }}: the size of the file, in bytes.

  • {{ sftp_file.sha256 }}: the SHA-256 checksum of the file, in lowercase hexadecimal.

  • {{ sftp_file.uploaded_at }}: the date and time of the upload in UTC, for example 2026-11-13T09:30:00+00:00.

These four smart fields do not work in the folder path or the file name.

Common questions

Do I need to escape special characters in the metadata template?

No. In an XML or JSON template, Kolleno escapes each value for you, so a customer name such as Smith & Co does not break the file.

What happens if a smart field has no value?

Kolleno leaves it empty in the text. If the whole file name is empty, Kolleno does not upload the file, and the workflow shows the reason.

What happens if the metadata is not valid XML or JSON?

Kolleno does not upload the file or the metadata, and the workflow shows the reason. After you fix the template, the workflow tries again.

Did this answer your question?