Zenfulfillment ACTION
Search Orders
Search for orders in Zenfulfillment. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Zenfulfillment account once, then configure and run Search Orders 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: "zenfulfillment-search-orders",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zenfulfillment: { authProvisionId: "apn_xxxxxxx" },
orderExternalId: "Order External ID",
name: "Name",
},
})
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": "zenfulfillment-search-orders",
"configured_props": {
"zenfulfillment": { "authProvisionId": "apn_xxxxxxx" },
"orderExternalId": "Order External ID",
"name": "Name"
}
}'// 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": "zenfulfillment",
},
},
},
)
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: "zenfulfillment-search-orders",
arguments: {
orderExternalId: "Order External ID",
name: "Name",
},
})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 |
|---|---|---|
orderExternalId Order External ID | string | Return only fulfillments having matching order externalId Optional Dynamic |
name Name | string | Returns orders matching order name Optional |
createdAtMin Created At Minimum | string | The minimum creation date of the order (ISO format). Eg. 2025-01-01 Optional |
createdAtMax Created At Maximum | string | The maximum creation date of the order (ISO format). Eg. 2025-01-01 Optional |
updatedAtMin Updated At Minimum | string | The minimum update date of the order (ISO format). Eg. 2025-01-01 Optional |
updatedAtMax Updated At Maximum | string | The maximum update date of the order (ISO format). Eg. 2025-01-01 Optional |
sortCreatedAt Sort by created at | string | Sort either ascending or descending by the creation date of the order Optional |
sortUpdatedAt Sort by updated at | string | Sort either ascending or descending by the update date of the order Optional |
page Page | integer | The page number to return. Default is 1 Optional |
itemsPerPage Items per page | integer | The number of items to return. Default is 50. Maximum is 200. 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
- zenfulfillment-search-orders
- Version
- 0.0.3
- App
- Zenfulfillment
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗