Rydoo ACTION
Search Payment Methods
Finds payment methods by type, branch, card type, status, and more. 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 Payment Methods 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-payment-methods",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rydoo: { authProvisionId: "apn_xxxxxxx" },
search: "Search",
accountType: ["Account Type"],
},
})
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-payment-methods",
"configured_props": {
"rydoo": { "authProvisionId": "apn_xxxxxxx" },
"search": "Search",
"accountType": ["Account Type"]
}
}'// 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-payment-methods",
arguments: {
search: "Search",
accountType: ["Account Type"],
},
})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 |
|---|---|---|
search Search | string | Filter payment methods where the name or ID contains this string Optional |
accountType Account Type | string[] | Filter by one or more payment method types Optional |
branchId Branch ID | string | Filter by branch ID Optional Dynamic |
isActive Is Active | boolean | Filter by active ( true) or inactive (false) payment methods. Defaults to all Optional |
validationStatus Validation Status | string[] | Filter by one or more validation statuses (e.g., Pending, Valid, Failed) Optional |
isReimbursable Is Reimbursable | boolean | Filter by reimbursable ( true) or non-reimbursable (false) payment methods. Defaults to all Optional |
cardNumber Card Number | string | Filter by card number Optional |
cardType Card Type | string[] | Filter by one or more card types Optional |
accountOwnership Account Ownership | string[] | Filter by one or more account ownership values Optional |
sort Sort | string | The field to sort the results by Optional |
limit Limit | integer | The number of payment methods to return per page (defaults to 50) Optional |
offset Offset | integer | The number of payment methods 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-payment-methods
- Version
- 0.0.2
- App
- Rydoo
- Authentication
- OAuth
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗