Actions43
- Document List Actions
- Document Pins Actions
- Document Tags Actions
- Document Upload Actions
- Document Watchers Actions
- Document Webhooks Actions
- Document Workflow Actions
- Group Actions
- Safe Actions
- Signatory Actions
- Template Actions
Document Upload → Upload Document
AI-generatedSummary
Upload a new document to a selected safe (vault), optionally inside a folder, by providing file content as either binary data from a specified binary property or as Base64-encoded content.
Inputs
- Safe (required) — Select the safe (vault) where the document will be uploaded.
- Folder — Optional folder UUID inside the selected safe.
- Content Source (required) — Choose how the file content will be provided: either from a binary property or Base64 content.
- Binary Property (required) — Name of the incoming binary property containing the file data (required if Content Source is 'Binary Property').
- Base64 Content (required) — Base64-encoded file content (raw or data URL), with whitespace and new lines removed and validated (required if Content Source is 'Base64 Content').
- MIME Type (required) — MIME type of the Base64 content; examples include 'application/pdf', 'image/png', 'image/jpeg' (required if Content Source is 'Base64 Content').
- File Name — Optional filename to use for the uploaded document; if omitted, defaults to the source name or 'document'.
Output shape
a single record representing the uploaded document, including metadata returned by the D4Sign API
The output JSON includes the response from D4Sign API about the created document. The operation validates UUID formats for safe and folder. Base64 content is normalized and validated. If the content source is 'binary', the binary data is read and converted to Base64 before upload.