What this action does

Creates a folder at a destination in your connected storage. Use it for automated folder structures — e.g. a folder per Opportunity on creation. Available in record-triggered, scheduled and screen flows. The async variant Create Folder (Async) returns immediately and emits a ⚡ Folder Created event when done.

Creating folders — choose your approach
ApproachBest when
From the widgetNo codeOne-off folders while working a record. Nothing to configure.
Create Folder flow actionRecommendedAutomated structures — a folder per record, triggered by CRM events. This page.
Apex / REST APIDevelopersCustom logic, bulk migrations, calls from external systems.
Input parameters
ParameterDescription
Folder Name
String
requiredName of the folder to create. Merge fields supported — e.g. {!$Record.Name}. Illegal characters for the target storage are auto-replaced.
Conflict Behavior
Picklist
optionalWhat to do if a folder with this name exists: fail · rename · useExisting (default).
Destination parameters
ParameterDescription
Library
String
varies by storageWhich connected storage to create the folder in.
for SharePoint
Required. Use the library ID from Settings → Storage, e.g. sharepoint_a8x2.
Drive ID
String
varies by storageThe drive/document library within the storage.
for SharePoint
Required. Every SharePoint site has 1+ document libraries (drives). Get it via Get Connected Folder or the SharePoint library page.
Parent Folder ID
String
varies by storageFolder under which the new folder is created.
for SharePoint
Required. Use root for the drive root.
Where do these IDs come from?Use the Get Connected Folder action to resolve a record’s folder and drive, or copy IDs from the storage library page in CloudFiles Settings. The library configuration pages explain each provider’s ID model.
Output parameters
ParameterDescription
Resource ID
String
CloudFiles ID of the created folder. Store it on the record to skip lookups later.
Resource Path
String
Human-readable path, e.g. /Accounts/Acme Corp/Contracts.
Type
String
Always folder for this action.

Conflict behavior

Folder already existsuseExisting makes the action idempotent — re-runs return the existing folder instead of failing. Prefer it in record-triggered flows, which can fire twice.
// Same operation via Apex — see Developer reference
List<Types.CreateFolderInput> inputs = new List<Types.CreateFolderInput>();
inputs.add(new Types.CreateFolderInput('Contracts', parentId));
List<Resource> out = Client.createFolders(inputs, 'sharepoint_a8x2', null);