Hookdeck ACTION
Retrieve all Requests
This endpoint lists all request, or a subset of requests. Requests are sorted by
ingested_at date. See the documentation.- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Hookdeck account once, then configure and run Retrieve all Requests 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: "hookdeck-retrieve-all-requests",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
hookdeck: { authProvisionId: "apn_xxxxxxx" },
id: ["Request ID"],
status: "Status",
},
})
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": "hookdeck-retrieve-all-requests",
"configured_props": {
"hookdeck": { "authProvisionId": "apn_xxxxxxx" },
"id": ["Request ID"],
"status": "Status"
}
}'// 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": "hookdeck",
},
},
},
)
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: "hookdeck-retrieve-all-requests",
arguments: {
id: ["Request ID"],
status: "Status",
},
})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 |
|---|---|---|
id Request ID | string[] | Filter by requests IDs. Optional |
status Status | string | Filter by status. Optional |
rejectionCause Rejection Cause | string | Filter by rejection cause. Optional |
sourceId Source ID | string | Filter by source IDs. Optional Dynamic |
path Path | string | URL Encoded string of the value to match partially to the path. Optional |
ingestedAtInitialRange Ingested At Initial Range | string | Filter by ingested at initial range. YYYY-MM-DD format. Optional |
ingestedAtFinalRange Ingested At Final Range | string | Filter by ingested at final range. YYYY-MM-DD format. Optional |
orderBy Order By | string | Sort key. Optional |
orderByDir Order By Direction | string | Sort direction. Optional |
limit Limit | integer | Limit the number of results. Pipedream will automatically paginate through the results. Optional |
additionalProperties Additional Properties | object | Filter by additional properties. Check the documentation for more details. 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
- hookdeck-retrieve-all-requests
- Version
- 0.0.2
- App
- Hookdeck
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗