Microsoft GraphSearch files
BetaReads data
Finds files and folders in OneDrive or SharePoint that match a text.
Settings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Microsoft Graph connection the step signs in with. |
| Drive of | "user" or "group" or "site" or "drive" |
| OwnerRequired | The person's id or sign-in address, the group's id, the site's id or the drive's id — whichever Drive of names. |
| Search forRequired | Matched against names, contents and other fields across the whole drive, as Microsoft 365's own search does. |
| Fields | Comma-separated property names. Empty answers Microsoft 365's default set. |
| Items per call | 1 to 999. |
| Fetch every page | Follows Graph's own next-page link. |
| Stop after | Pages — at most 50. |
| Cursor | Paste a previous run's Next cursor to read the page after it. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `microsoft-graph`) |
driveOf | "user" or "group" or "site" or "drive", by default "user" |
owner | text |
query | text |
select | text |
top | number, by default 100 |
returnAll | true/false, by default false |
maxPages | number, by default 10 |
cursor | text |
Output
| Field | Type |
|---|---|
itemsFiles and folders found | array |
countItems in this answer | number |
hasMoreMore items are waiting behind this page | boolean |
nextCursorCursor for the next page | string |
Sample output, and the expression for each field
- count0
- hasMorefalse
- items[]
- nextCursor""
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"cursor": "",
"driveOf": "user",
"maxPages": 10,
"owner": "<owner>",
"query": "<search for>",
"returnAll": false,
"select": "",
"top": 100
},
"label": "Search files",
"type": "graph.searchFiles",
"version": 1
}