Microsoft SharePoint operation

The SharePoint operation component defines the specific action the connector performs against SharePoint. Every operation starts with an Action Type — Get, Create, or Delete — chosen before any browsing happens. The Action Type determines which Object Types (File, Folder, List, or List Item) and operation fields are available in the browse step that follows.

Supported Action	Object Type	Brief Description
Get	File	Retrieve a file's metadata or download its content
	Folder	Retrieve a folder's metadata/properties
	List	Retrieve a list's definition and settings
	List Item	Retrieve a specific row's field values
Create	File	Upload a new file into a document library
	Folder	Create a new folder in a document library
	List	Create a new list (define its structure)
	List Item	Add a new row to a list
Delete	File	Remove a file from a document library
	Folder	Remove a folder from a document library
	List	Remove a list and its structure
	List Item	Remove a specific row from a list

note

For List Item, the connector calls SharePoint to list every custom list in the site during import and presents each one by name as a selectable object; the underlying list GUID is captured automatically. Hidden lists and document-library-backed lists are excluded. The response (and, for Create, request) profile's custom fields are generated dynamically from the selected list's actual columns — re-import the operation after adding or changing columns to refresh the profile.

Get operation

Use the Get operation to retrieve a single File, Folder, List, or List Item by path/ID, or to download a file's binary content.

Before you begin:

• Know the Document Library (Drive) name and the relative path, or the Graph item GUID, of the item you want

• For List/List Item, know the exact SharePoint list name

• Decide whether you need file metadata (JSON) or the raw file content (binary)

To configure the Get operation:

1. Create a new Get operation or click Import Operation.

2. Select Object Type: File, Folder, List, or List Item

3. For File, choose File Metadata or File Content.

4. Click Next to import Request and Response profiles.

5. On the Operation page, configure the fields shown below for your chosen object type.

6. On the Fields tab, select only the properties or columns you want back — the connector will ask SharePoint for just those instead of everything, which keeps the response smaller and faster. If you do not select anything, you get all the standard fields (and, for List Item, all custom columns) back by default. This applies to File Metadata, Folder, List, and List Item; it does not apply to File Content downloads, which always return the full file.

Get File Metadata and File Content

Operation Fields

Field	Required	Description
Drive Name	Required	The target document library.

Request Schema

Use the following request properties:

{
  "filePath": "Reports/2026/report.xlsx",
  "id": "01BYE5RZ6QN3ZWBTUFOFD3GSPGOHDJD36K"
}

• filepath - Relative path to the file within the configured Drive Name.
• id — Microsoft Graph item GUID. When both properties are supplied, id takes precedence and skips path resolution.

note

File Content returns the raw binary file stream rather than a JSON response.

Response Schema

{
  "id": "01BYE5RZ6QN3ZWBTUFOFD3GSPGOHDJD36K",
  "name": "report.xlsx",
  "size": 245678,
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Shared Documents/report.xlsx",
  "eTag": "\"{A1B2C3D4-1234-5678-ABCD-1234567890AB},1\"",
  "cTag": "\"c:{A1B2C3D4-1234-5678-ABCD-1234567890AB},1\"",
  "@microsoft.graph.downloadUrl": "https://contoso.sharepoint.com/_layouts/15/download.aspx?...",
  "createdDateTime": "2026-01-10T09:15:00Z",
  "lastModifiedDateTime": "2026-01-15T14:22:00Z",
  "createdBy": { "user": { "id": "8f3e...", "displayName": "Jane Doe", "email": "jane.doe@contoso.com" } },
  "file": {
    "mimeType": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
    "hashes": { "quickXorHash": "abc123==" }
  },
  "parentReference": { "driveId": "b!ab12...", "driveType": "documentLibrary", "path": "/drives/b!ab12.../root:" }
}

Get File Content

Operation Fields

Field	Required	Description
Drive Name	Required	The target document library.
Item ID	Optional	GUID; fastest option, no path resolution.
Parent Folder Path	Required if Item ID is not set	Folder containing the file.
File Name	Required if Item ID is not set	Name of the file to download.

The response for Get File Content is a raw binary stream, not JSON — the connector fetches Graph's pre-authenticated redirect and streams bytes directly into the Boomi document, unbuffered regardless of file size.

Get Folder

Operation Fields

Field	Required	Description
Drive Name	Required	The target document library.

Request Schema

Use the following request properties:

{
  "folderPath": "Reports/2026",
  "id": "01BYE5RZ7N4YWBTUFOFD3GSPGOHDJD37L"
}

• folderPath — Relative path to the folder within the configured Drive Name.
• id — Microsoft Graph item GUID. When both properties are supplied, id takes precedence.

Response Schema

{
  "id": "01BYE5RZ7N4YWBTUFOFD3GSPGOHDJD37L",
  "name": "Reports",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Shared Documents/Reports",
  "eTag": "\"{B2C3D4E5-2345-6789-BCDE-2345678901BC},2\"",
  "folder": { "childCount": 12 },
  "createdDateTime": "2025-11-02T08:00:00Z",
  "lastModifiedDateTime": "2026-01-15T14:22:00Z"
}

Get List

No operation-level locator field is required. Supply the required list name or GUID in the input document:

Request Schema

{
  "listName": "Project Tasks"
}

• listName — SharePoint list display name or GUID. This property is required.

Response Schema

{
  "id": "3c9e1a2b-4d5f-6789-abcd-ef0123456789",
  "displayName": "Project Tasks",
  "name": "Project Tasks",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Lists/Project Tasks",
  "list": { "contentTypesEnabled": false, "hidden": false, "template": "genericList" },
  "createdDateTime": "2025-09-01T12:00:00Z",
  "lastModifiedDateTime": "2026-01-20T10:00:00Z"
}

Get List Item

No operation-level locator field is required. Supply the required numeric list-item ID in the input document:

Request Schema

{
  "rowId": "42"
}

• rowId — Numeric SharePoint list-item ID, such as the 42 in ?ID=42. This property is required.

Response Schema

{
  "id": "42",
  "eTag": "\"a1b2c3d4-5e6f-7890-abcd-ef1234567890,3\"",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Lists/Project Tasks/DispForm.aspx?ID=42",
  "createdDateTime": "2026-01-05T09:00:00Z",
  "lastModifiedDateTime": "2026-01-20T10:00:00Z",
  "contentType": { "id": "0x0100...", "name": "Item" },
  "fields": {
    "Title": "Finalize Q1 budget",
    "Priority": "High",
    "DueDate": "2026-02-01T00:00:00Z",
    "PercentComplete": 0.75
  }
}

Create operation

Use the Create operation to add a new File, Folder, List, or List Item.

Before you begin:

• For files: know the target Document Library, destination folder path, and file name

• For lists: prepare the list definition JSON, including any custom columns to create alongside it

• For list items: select the target list during import, then map only your custom column values

To configure the Create operation:

1. Create a new Create operation or click Import Operation.

2. Select Object Type: File, Folder, List, or List Item.

3. Click Next to import Request and Response profiles.

4. Configure the operation fields and map your input document.

Create File

Operation Fields

Field	Required	Description
Drive Name	Required	The target document library.
Parent Folder Path	Optional	Blank uploads to the library root.
File Name	Required	Name of the file to create.
Action if File Exists	Required	Overwrite (default, replace) / Rename / Fail (returns 409).

note

The request body for Create File is the raw file content (binary), not JSON — content type application/octet-stream. Files up to 250 MB are supported; larger files are rejected and must be split into smaller files before upload.

Request Schema

Same shape as Get File Metadata. Graph returns the newly created file's metadata (HTTP 201, or 200 if replace overwrote an existing file).

Create Folder

Operation Fields

Field	Required	Description
Drive Name	Required	The target document library.
Parent Folder Path	Optional	Blank creates at the library root.

Request Schema

{
  "name": "2026 Reports",
  "folder": {},
  "@microsoft.graph.conflictBehavior": "rename"
}

Response Schema

The response uses the SharePoint Folder profile and contains the newly created folder metadata. Graph returns HTTP 201.

{
  "id": "01BYE5RZ7N4YWBTUFOFD3GSPGOHDJD37L",
  "name": "2026 Reports",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Shared Documents/2026 Reports",
  "eTag": "\"{B2C3D4E5-2345-6789-BCDE-2345678901BC},1\"",
  "folder": { "childCount": 0 },
  "createdDateTime": "2026-01-20T10:00:00Z",
  "lastModifiedDateTime": "2026-01-20T10:00:00Z"
}

Create List

No operation-level fields — the list definition, including columns, comes entirely from the input document body (displayName, description, list template, and columns array).

Request Schema

{
  "displayName": "Vendor Contacts",
  "description": "Master list of approved vendor contacts",
  "list": { "template": "genericList" },
  "columns": [
    { "name": "CompanyName", "text": {} },
    { "name": "Priority", "choice": { "choices": ["Low", "Medium", "High"], "displayAs": "dropDownMenu" } },
    { "name": "IsActive", "boolean": {} },
    { "name": "AnnualSpend", "currency": { "locale": "en-US" } }
  ]
}

Response Schema

The response uses the SharePoint List profile and contains the created list metadata, generated ID, and configured columns. Graph returns HTTP 201.

{
  "id": "3c9e1a2b-4d5f-6789-abcd-ef0123456789",
  "displayName": "Vendor Contacts",
  "description": "Master list of approved vendor contacts",
  "name": "Vendor Contacts",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Lists/Vendor Contacts",
  "list": { "template": "genericList", "hidden": false },
  "columns": [
    { "name": "CompanyName", "text": {} },
    { "name": "Priority", "choice": { "choices": ["Low", "Medium", "High"] } },
    { "name": "IsActive", "boolean": {} },
    { "name": "AnnualSpend", "currency": { "locale": "en-US" } }
  ],
  "createdDateTime": "2026-01-20T10:00:00Z"
}

Create List Item

No operation-level fields — the target list is fixed by the object selected during import; only column values are mapped in the request body's fields object.

Request Schema

{
  "fields": {
    "Title": "Renew software license",
    "Priority": "Medium",
    "DueDate": "2026-03-01T00:00:00Z"
  }
}

Response Schema

Response Schema The response uses the SharePoint List Item profile and contains the created item's system metadata and custom fields. Graph returns HTTP 201.

{
  "id": "43",
  "eTag": "\"a1b2c3d4-5e6f-7890-abcd-ef1234567890,1\"",
  "webUrl": "https://contoso.sharepoint.com/sites/finance/Lists/Project Tasks/DispForm.aspx?ID=43",
  "createdDateTime": "2026-01-20T10:00:00Z",
  "lastModifiedDateTime": "2026-01-20T10:00:00Z",
  "contentType": { "id": "0x0100...", "name": "Item" },
  "fields": {
    "Title": "Renew software license",
    "Priority": "Medium",
    "DueDate": "2026-03-01T00:00:00Z"
  }
}

Delete operation

Use the Delete operation to permanently remove a File, Folder, List, or List Item.

caution

Deletion is permanent. Microsoft Graph returns an empty 204 No Content response for a successful delete and does not return the deleted item's content. The connector synthesizes a confirmation payload (status, objectType, statusCode) since downstream Boomi steps expect a document body.

Before you begin:

• Know the Drive Name and Path, or the Graph item GUID, of the File/Folder to delete

• Know the exact List Name for List deletion, or the Item GUID for List Item deletion

• Deletion is permanent — Graph does not return the deleted item's content

To configure the Create operation:

1. Create a new Delete operation or click Import Operation.

2. Select Object Type: File, Folder, List, or List Item.

3. Click Next to import Request and Response profiles.

4. Configure the operation fields for your chosen object type.

DELETE uses a request profile only. It does not use or produce a response profile or output document.

Microsoft Graph returns an empty 204 No Content response for a successful delete. Since Boomi downstream steps expect a document body, the connector synthesizes a confirmation payload.

Delete File

Drive Name is configured on the operation. Supply either the relative file path or Graph item GUID in the input document:

{
  "filePath": "Archive/2025/old-report.xlsx",
  "id": "01BYE5RZ6QN3ZWBTUFOFD3GSPGOHDJD36K"
}

Delete Folder

Drive Name is configured on the operation. Supply either the relative folder path or Graph item GUID in the input document:

{
  "folderPath": "Archive/2025",
  "id": "01BYE5RZ7N4YWBTUFOFD3GSPGOHDJD37L"
}

Delete List

Supply the required list name or GUID in the input document:

{
  "listName": "Project Tasks"
}

Delete List Item

Supply the required numeric list-item ID in the input document:

{
  "rowId": "42"
}

Important Behavior

• For File and Folder operations, id takes precedence over filePath or folderPath.
• listName is required for List GET and DELETE requests.
• rowId is required for List Item GET and DELETE requests.
• DELETE is permanent. Verify the target with a GET operation before deleting in production.
• Re-import the operation when SharePoint list columns change so dynamically generated List Item profiles remain current.

Get / Create / Delete Import Wizard

Step 1: Select Operation Type

1. In your Boomi process, add a connector step.

2. Select SharePoint connector.

3. Choose your configured connection.

4. Click Import Operation for a new operation, and pick the action (Get, Create, or Delete).

Step 2: Select Object Type

1. Choose File, Folder, List, or List Item.

2. If File is chosen for Get, also choose File Metadata or File Content.

3. If List Item is chosen, the connector queries the site for its custom lists and displays each one by name — select the list you want to work with.

Step 3: Import Profiles

1. Click Next to proceed.

2. The connector imports Request and Response profiles — for List Item, custom fields are generated live from the selected list's actual columns.

3. Review imported profiles and click Finish.

Step 4: Configure Operation Fields

1. Set Drive Name/Path/Item ID, List Name, or the Action-if-File-Exists behavior as applicable to your chosen action and object type.

2. For Get, you can also select only the properties or columns you want on the Fields tab, instead of retrieving everything.

Troubleshooting

• "Drive Name is required" / "List Name is required" – A required operation field was left blank – Set the field on the operation page.

• "Item ID is required" on Get or Delete for List Item – No Item ID configured on the operation – Set the Item ID field.

• File upload rejected outright on Create – File exceeds 250 MB – Split the file into smaller parts before uploading.

• Delete appears to succeed but the item still exists – The wrong Drive Name, Path, or Item ID was targeted (Delete does not error on a mismatched-but-valid combination of fields resolving to a different item) – Double-check the identifiers before running Delete in production.

• Get or Delete on List object type fails even with List Name blank – Both actions always require an explicit List Name for the List object type; list names are visible during the List Item browse/import wizard, which lists every custom list in the site.

• A column doesn't appear in the List Item schema – The column is readOnly, hidden, or one of the excluded system columns (Attachments, ComplianceAssetId, ContentType, Author, Editor) that Graph does not accept on Create even when not marked read-only.

Commmon Error Scenarios

File Operations

• File exceeds the simple-upload limit on Create – Files over 250 MB are rejected; split the file into smaller parts before uploading.

• Conflict on upload (409) – A file with the same name already exists and Action if File Exists is set to Fail; choose Overwrite or Rename, or handle the 409 downstream.

List and List Item Operations

• "List Name is required" on Get or Delete – List metadata retrieval and deletion always require an explicit List Name; there is no "get/delete all lists" runtime action.

• "Item ID is required" on Get or Delete – List Item retrieval and deletion require an Item ID to be set on the operation.

• Column missing from the imported profile – The column is excluded because it is read-only, hidden, or a protected system column; re-import after confirming the column is a plain writable column on the list.

Delete Operations

• File or Folder not found (404) on Delete – The Drive Name, Path, or Item ID does not resolve to an existing item; verify the identifiers, especially after the item may have already been moved or deleted.

• Delete removed the wrong item – Drive Name, Path, and Item ID resolved to a different item than intended; prefer Item ID (GUID) and verify with a Get before deleting in production processes.