BOX n8n INTEGRATION: AUTOMATE BOX WITH N8N

This action lets you programmatically create new folders in your Box account, enabling you to build organized file structures automatically. It's the foundation for any automation that needs to store or categorize incoming content.

Key parameters: Credential to connect with (select your authenticated Box account, dropdown, required); Name (the name for your new folder, text input, required—you can use dynamic data like "Project_{{projectName}}"); Parent ID (the ID of the folder where your new folder will be created, text input, optional—if not specified, folder is created at root level, use "0" for root).

Use cases: Create client folders automatically when new deals close in your CRM; Generate dated archive folders (e.g., "Reports_2024_January") on a schedule; Build project folder structures automatically when projects are initiated in your PM tool.

This action retrieves detailed information about a specific folder, including its metadata, size, parent folder, and more. Essential for workflows that need to verify folder existence or extract folder properties before performing other operations.

Key parameters: Credential to connect with (your Box account credential, dropdown, required); Folder ID (the unique identifier of the folder you want to retrieve, text input, required—you can find this ID in the Box URL when viewing a folder, or capture it from a trigger's output).

Use cases: Verify a folder exists before attempting to upload files to it; Retrieve folder metadata to log folder sizes and item counts; Get parent folder information to navigate folder hierarchies.

This action searches for folders within your Box account based on query terms. Perfect for finding specific folders when you don't have the exact Folder ID but know the folder name or part of it.

Key parameters: Credential to connect with (Box account authentication, dropdown, required); Query (the search term for finding folders, text input, optional—leave empty to retrieve all folders); Return All (toggle to determine if all matching results should be returned, boolean, optional, defaults to false); Limit (maximum number of results to return, numeric input, optional, defaults to 100).

Use cases: Find all folders containing "2024" in their name for year-end archiving; Search for client folders by partial name to verify existence before creating duplicates; Retrieve all project folders matching a specific naming pattern.

This action modifies the properties of an existing folder. Use it to rename folders, move them to different locations, or update folder settings programmatically.

Key parameters: Credential to connect with (your Box account, dropdown, required); Folder ID (the unique identifier of the folder to update, text input, required); Update Fields (expandable section where you specify which properties to modify, optional—can include new name, new parent folder, description, and other metadata).

Use cases: Rename folders based on updated project names in your PM tool; Move completed project folders to an archive directory automatically; Update folder descriptions when project status changes.

This action enables sharing a folder with specific users or groups, complete with role-based permissions. Critical for automating collaboration workflows and ensuring the right people have access at the right time.

Key parameters: Credential to connect with (Box account credential, dropdown, required); Folder ID (the folder to share, text input, required); Accessible By (determines who receives access, dropdown with options like "User", required); Use Email (toggle to specify whether to identify the recipient by email, boolean, optional); Email (the recipient's email address if "Use Email" is enabled, text input, conditionally required); Role (the permission level for the shared access such as "Editor", "Viewer", "Co-owner", dropdown, required).

Use cases: Automatically share project folders with new team members when they're assigned in your HR system; Grant client access to their folders when projects kick off; Share completed deliverable folders with stakeholders upon project completion.

This action permanently removes a folder from your Box account. Use with caution—but it's invaluable for cleanup automations and maintaining organized storage.

Key parameters: Credential to connect with (Box account, dropdown, required); Folder ID (the folder to delete, text input, required); Recursive (when enabled, deletes the folder and all its contents including subfolders and files, toggle, optional—if disabled and the folder isn't empty, the deletion will fail).

Use cases: Automatically clean up temporary processing folders after workflows complete; Remove obsolete project folders after a retention period; Delete duplicate folders identified by your deduplication workflow.

This action uploads files directly to your Box account, whether from binary data passed through the workflow or from text content you specify. It's the cornerstone of any document ingestion automation.

Key parameters: Credential to connect with (your Box account, dropdown, required); File Name (the name for the uploaded file including extension, text input, required); Binary File (toggle indicating whether the input is binary data, boolean, optional); File Content (the actual content to upload if not using binary data, text input, required when Binary File is disabled); Parent ID (the destination folder's ID, text input, optional—defaults to root folder if not specified).

Use cases: Upload email attachments to Box automatically when received; Save generated reports from Notion or other tools directly to specific Box folders; Store webhook payloads or API responses as JSON files for auditing.

This action retrieves detailed information about a specific file, including its metadata, version history, and current location. Use it to verify file existence or extract file properties for downstream processing.

Key parameters: Credential to connect with (Box account credential, dropdown, required); File ID (the unique identifier of the file, text input, required); Additional Fields (optional fields for retrieving specific metadata or properties).

Use cases: Check if a file exists before attempting updates or downloads; Retrieve file metadata for logging or audit purposes; Get file version information to determine if processing is needed.

This action downloads a file from Box as binary data, making it available for further processing in your workflow—like sending as an email attachment, uploading to Dropbox, or processing with a conversion tool.

Key parameters: Credential to connect with (your Box account, dropdown, required); File ID (the unique identifier of the file to download, text input, required); Put Output File in Field (the name of the binary field where the file data will be stored, text input, required—typically set to "data" unless you need to handle multiple files).

Use cases: Download files from Box to process and re-upload elsewhere (Google Drive, S3, etc.); Retrieve attachments to include in automated email sends; Pull files for processing through AI/ML tools or document converters.

This action searches for files within your Box account using query terms. Ideal for finding specific documents when you know the filename or content keywords but not the exact File ID.

Key parameters: Credential to connect with (Box account, dropdown, required); Query (the search keywords, text input, required); Return All (whether to return all matching results, boolean toggle, optional); Limit (maximum results to return, numeric, optional, defaults to 100); Additional Fields (extra parameters to refine your search).

Use cases: Find all files matching a client name across your entire Box account; Search for documents containing specific keywords for compliance reviews; Locate files by partial filename when processing requests.

This action creates a duplicate of a file in a specified destination folder. Perfect for backup workflows, creating working copies, or distributing files across multiple folders.

Key parameters: Credential to connect with (your Box account, dropdown, required); File ID (the source file to copy, text input, required); Parent ID (the destination folder for the copy, text input, required); Additional Fields (optional parameters like new filename for the copy).

Use cases: Create backup copies of important files to archive folders; Distribute template files to multiple project folders; Copy processed files to output directories while preserving originals.

This action shares a specific file with designated users, complete with role-based permissions. Essential for document collaboration workflows where individual files need controlled access.

Key parameters: Credential to connect with (Box account credential, dropdown, required); File ID (the file to share, text input, required); Accessible By (who receives access, dynamic field, optional); Role (permission level such as Editor or Viewer, dropdown, required); Options (additional sharing configuration options).

Use cases: Share contracts with clients automatically upon generation; Grant temporary access to specific files for external reviewers; Distribute reports to stakeholders with view-only permissions.

This action permanently removes a file from your Box account. Use it for cleanup operations, removing obsolete documents, or implementing retention policies.

Key parameters: Credential to connect with (your Box account, dropdown, required); File ID (the unique identifier of the file to delete, text input, required).

Use cases: Automatically delete temporary files after processing completes; Remove outdated document versions as part of retention workflows; Clean up duplicate files identified by deduplication automation.