Rydoo ACTION
Search Trips
Finds trips by user, status, or name. See the documentation
- Action
- Read only
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Rydoo account once, then configure and run Search Trips 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: "rydoo-search-trips",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rydoo: { authProvisionId: "apn_xxxxxxx" },
userId: "User",
search: "Search",
},
})
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": "rydoo-search-trips",
"configured_props": {
"rydoo": { "authProvisionId": "apn_xxxxxxx" },
"userId": "User",
"search": "Search"
}
}'// 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": "rydoo",
},
},
},
)
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: "rydoo-search-trips",
arguments: {
userId: "User",
search: "Search",
},
})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 |
|---|---|---|
userId User | string | The user to whom the expense belongs (e.g., d290f1ee-6c54-4b01-90e6-d701748f0851) Optional Dynamic |
search Search | string | Filter trips where the name contains this string Optional |
status Status | string[] | Filter by one or more trip statuses Optional |
isActive Is Active | boolean | Filter by active trips ( true) or inactive trips (false). Defaults to all trips Optional |
fromDate From Date | string | Return trips whose end date is on or after this date (ISO 8601, e.g., 2024-01-01T00:00:00Z) Optional |
toDate To Date | string | Return trips whose start date is on or before this date (ISO 8601, e.g., 2024-12-31T23:59:59Z) Optional |
sort Sort | string | The field to sort the results by Optional |
limit Limit | integer | The number of trips to return per page (defaults to 50) Optional |
offset Offset | integer | The number of trips to skip for paging (defaults to 0) 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
- rydoo-search-trips
- Version
- 0.0.2
- App
- Rydoo
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗