Papertrail ACTION
Search Log Events
Search Papertrail log events programmatically. Supports query syntax, system/group scope, time or ID bounds, limit, and tail mode. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Papertrail account once, then configure and run Search Log Events 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: "papertrail-search-events",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
papertrail: { authProvisionId: "apn_xxxxxxx" },
q: "Query",
systemId: "System ID",
},
})
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": "papertrail-search-events",
"configured_props": {
"papertrail": { "authProvisionId": "apn_xxxxxxx" },
"q": "Query",
"systemId": "System ID"
}
}'// 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": "papertrail",
},
},
},
)
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: "papertrail-search-events",
arguments: {
q: "Query",
systemId: "System ID",
},
})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 |
|---|---|---|
q Query | string | Search query (Papertrail search syntax). Omit to return recent events. Optional |
systemId System ID | string | Papertrail system ID Optional Dynamic |
groupId Group ID | string | The ID of the group Optional Dynamic |
minId Min Event ID | string | Oldest message ID to examine (64-bit ID as string). Optional |
maxId Max Event ID | string | Newest message ID to examine. Optional |
minTime Min Time (Unix) | integer | Oldest timestamp to examine (epoch seconds, UTC). Optional |
maxTime Max Time (Unix) | integer | Newest timestamp to examine (epoch seconds, UTC). Optional |
limit Limit | integer | Maximum messages to return (default 1000, max 10,000). Optional |
tail Tail | boolean | When true, prioritizes recency (useful for live tail). Defaults to true when min_id is set without max_id/max_time on the API side. 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
- papertrail-search-events
- Version
- 0.0.2
- App
- Papertrail
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗