Actions156
- Customer Actions
- Resource Actions
- Order Actions
- Item Actions
- Job Actions
- Item Prices Actions
- Job Prices Actions
- Files Actions
- Custom Fields Actions
- Admin Actions
- Customer Address Actions
- Customer Fields Actions
- Get Many by External ID
- Get Many Customer Objects (By Status)
- Get Many Customer Objects (By Status List)
- Get Available Account IDs
- Get Available Payment Methods
- Get Available Workflows
- Get Account
- Get Payment Information
- Get Payment Method Description
- Get Created By Resource ID
- Get Project Manager ID
- Get Source of Contact
- Get Date of Initial Contact
- Get Dossier
- Update Payment Information
- Update Project Manager ID
- Update Source of Contact
- Update Date of Initial Contact
- Update Dossier
- Resource Fields Actions
- Order Fields Actions
- Get Creation Date
- Get Delivery Comment
- Get External ID
- Get Language Combination
- Get Links
- Get Master Project ID
- Get Order Closing Date
- Get Order Confirmations
- Get Order Date
- Get Order Number for View
- Get Project Category
- Get Project Status
- Get Request ID
- Get Subject
- Create Project Linking
- Get List of Templates
- Set Request ID
- Set Creation Date
- Set EN15038 Requested
- Set External ID
- Set Master Project ID
- Set Project Category
- Item Fields Actions
- Job Fields Actions
- Update Job Status
- Run Automatic Job
- Get Comment
- Update Comment
- Get Description
- Update Description
- Get Due Date
- Update Due Date
- Get Delivery Date
- Get Creation Date
- Get Job Number
- Get Currency
- Get Resource ID
- Update Contact Person ID
- Get Contact Person ID
- Get Delivery Note
- Update Delivery Note
- Get Payable ID
- Update CAT Report
- Customer Contact Actions
Files → Upload Document
AI-generatedSummary
Upload a document to Plunet, storing it in a folder identified by the selected folder type and main ID.
Inputs
- folderType (required) — Select the folder type (e.g., Request Source, Quote Reference) that determines where the file will be stored. Each option corresponds to a specific entity such as Request, Quote, Order, etc.
- mainID (required) — The numeric ID of the entity (Request ID, Quote ID, Order ID, etc.) associated with the selected folder type.
- fileByteStream (required) — Base64‑encoded content of the file to upload.
- filePathName (required) — File name with extension (e.g., 'specification.pdf') as it should appear in Plunet.
- fileSize — Size of the file in bytes. If omitted, the node calculates it automatically from the byte stream.
Output shape
json
The node returns the raw JSON response from the Plunet API after the upload, which typically includes a success flag and any metadata about the stored document (such as its internal ID).
Examples
Example 1: Attach a specification PDF to a quote.
Set folderType to 'Quote Source (uses Quote ID)' (value 4), provide the quote’s ID in mainID, supply the Base64‑encoded PDF in fileByteStream, give it a name like 'spec.pdf' in filePathName, and optionally specify fileSize.
