Sharepoint ACTION
Search Files
Search for files across the tenant. Supports KQL via the optional query template.
Backed by the Microsoft Search index and eventually consistent — newly created or modified files may not appear until indexing catches up.
For immediate, deterministic results, prefer:
- Get File by ID when the ID is known
- List Files in Folder for path-based listing
- Search and Filter Files for OData
$filteragainst a document library
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Sharepoint account once, then configure and run Search Files from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "sharepoint-search-files",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
sharepoint: { authProvisionId: "apn_xxxxxxx" },
queryString: "Query String",
queryTemplate: "Query Template",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "sharepoint-search-files",
"configured_props": {
"sharepoint": { "authProvisionId": "apn_xxxxxxx" },
"queryString": "Query String",
"queryTemplate": "Query Template"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "sharepoint",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "sharepoint-search-files",
arguments: {
queryString: "Query String",
queryTemplate: "Query Template",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
queryString Query String | string | The search query containing the search terms Required |
queryTemplate Query Template | string | Provides a way to decorate the query string. Supports both KQL and query variables. Example: ({searchTerms}) AuthorOWSUSER:Adventure See the documentation for more information. Optional |
select Select | string | A comma-separated list of properties to return in the response Optional |
size Max Results | integer | The maximum number of results to return Optional |
sortField Sort Field | string | The field to sort the results by Optional |
descending Descending | boolean | Whether to sort the results in descending order Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- sharepoint-search-files
- Version
- 0.0.9
- App
- Sharepoint
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗