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
| Approach | Best when | |
|---|---|---|
| From the widget | No code | One-off folders while working a record. Nothing to configure. |
| Create Folder flow action | Recommended | Automated structures — a folder per record, triggered by CRM events. This page. |
| Apex / REST API | Developers | Custom logic, bulk migrations, calls from external systems. |
Input parameters
| Parameter | Description | |
|---|---|---|
Folder NameString |
required | Name of the folder to create. Merge fields supported — e.g. {!$Record.Name}. Illegal characters for the target storage are auto-replaced. |
Conflict BehaviorPicklist |
optional | What to do if a folder with this name exists: fail · rename · useExisting (default). |
Destination parameters
| Parameter | Description | |
|---|---|---|
LibraryString |
varies by storage | Which connected storage to create the folder in.
for SharePoint
Required. Use the library ID from Settings → Storage, e.g. sharepoint_a8x2. |
Drive IDString |
varies by storage | The 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 IDString |
varies by storage | Folder 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
| Parameter | Description | |
|---|---|---|
Resource IDString |
CloudFiles ID of the created folder. Store it on the record to skip lookups later. | |
Resource PathString |
Human-readable path, e.g. /Accounts/Acme Corp/Contracts. | |
TypeString |
Always folder for this action. |
Conflict behavior
△
Folder already exists
useExisting 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);
