Create Attachment
salesforce.create_attachment
ActionCRM & salesconnection required
Calls the Salesforce REST API at the connection's instance URL.
Attach a file to a record the classic way, as an Attachment.
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.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
parent_id Id of the record the attachment hangs off. Supports {{ }}. | string | Yes | — | — | — |
name File name with its extension. | string | Yes | — | — | — |
file_content The file, base64-encoded — e.g. {{ steps.download.file_content }}. | string | Yes | — | — | — |
content_type MIME type, e.g. application/pdf. Salesforce guesses from the name when empty. | string | No | — | — | — |
description Optional description of the attachment. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The new Attachment id. | string | — |
parent_id The record it was attached to. | string | — |
success True when Salesforce accepted the attachment. | boolean | — |
{
"id": "",
"parent_id": "",
"success": false
}Notes
- Attachments are the legacy model and only work on objects that still support them; new work should use salesforce.upload_file.
- The body is capped at 25 MB of base64 data.
Templates that use Salesforce
Solutions with Salesforce
See Create Attachment 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.