Upload File

salesforce.upload_file
ActionCRM & salesconnection required

Calls the Salesforce REST API at the connection's instance URL.

Upload a file to Salesforce Files as a new ContentVersion.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Salesforce
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
login_url, api_version
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
title
Title shown in Salesforce Files.
stringYes———
filename
File name with its extension (PathOnClient) — Salesforce reads the file type from it.
stringYes———
file_content
The file, base64-encoded — e.g. {{ steps.download.file_content }}.
stringYes———
description
Optional description of the file.
stringNo———
linked_entity_id
Record to publish the file to at upload (FirstPublishLocationId). Leave empty and link later with salesforce.link_file.
stringNo———

Output

One shape.

result

FieldTypeExample
id
The new ContentVersion id.
string—
content_version_id
The new ContentVersion id.
string—
content_document_id
The ContentDocument the version belongs to — what salesforce.link_file needs.
string—
success
True when Salesforce accepted the upload.
boolean—
{
  "content_document_id": "",
  "content_version_id": "",
  "id": "",
  "success": false
}

Notes

  • A JSON (non-multipart) upload is capped at 37.5 MB of base64 data.
  • Reads the ContentDocumentId back in a second call, since Salesforce returns only the ContentVersion id.

See Upload File run in a workflow.

In a technical demo we add the Salesforce connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.