Creatio icon

Creatio

Read and write records in Creatio CRM (contacts, accounts, leads, opportunities, custom objects) via OData. Use to look up, create, update, or delete Creatio CRM data.

Schema → Upload File

AI-generated

Summary

Upload a binary file from the workflow input to a specified Creatio file entity, linking it to a parent record by its GUID.

Inputs

  • Authentication (required) — Choose between OAuth2 or Username & Password authentication methods.
  • Input Binary Field (required) — The name of the binary property on the input item that contains the file to upload.
  • Entity Schema Name (required) — The Creatio file entity schema name, e.g., ContactFile, AccountFile, or SysFile, to which the file will be uploaded.
  • Column Name (required) — The column in the file entity that holds the file data; typically 'Data'.
  • Parent Column Name (required) — The foreign key column linking the file to its parent record, e.g., Contact or RecordId.
  • Parent Column Value (required) — The GUID of the existing parent record to which the file will be attached.
  • Options — Optional settings including Additional Params as JSON string, File ID (GUID) for the file, an override for the File Name, and an override for the MIME Type.

Output shape

a single JSON object indicating success and including the file ID of the uploaded file

If the Creatio API response is empty, the node returns { success: true, fileId } with the fileId used for the upload. If the API returns a response string, the node attempts to parse it as JSON and ensure the fileId is included. Errors are thrown for failed upload attempts.

Examples

Example 1: Upload a 'data' binary file property to the 'ContactFile' entity, linked by 'Contact' column to a known parent record GUID

Set input binary field to 'data', entity schema name to 'ContactFile', column name to 'Data', parent column name to 'Contact', parent column value to the parent GUID, and optionally provide a file name or MIME type override.

Links

Discussion