CONNECT APP
Build with Rydoo
Business Management
- OAuth
MCP
Give your agent Rydoo tools
Every Rydoo action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Rydoo account for each tool call — you store no tokens.
// 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()
// e.g. run Add New User:
const result = await mcp.callTool({
name: "rydoo-add-new-user",
arguments: {
email: "Email",
firstName: "First Name",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Add New User:
result = await session.call_tool("rydoo-add-new-user", {
"email": "Email",
"firstName": "First Name",
})API PROXY
Call the Rydoo API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Rydoo API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.rydoo.com/v2/users",
})
// Any allowed Rydoo endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.rydoo.com/v2/users
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucnlkb28uY29tL3YyL3VzZXJz?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Rydoo actions from your backend
Connect a user's Rydoo account once, then run Add New User on their behalf from your own code — TypeScript, Python, or plain HTTP.
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-add-new-user",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
rydoo: { authProvisionId: "apn_xxxxxxx" },
email: "Email",
firstName: "First Name",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="rydoo-add-new-user",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"rydoo": {"authProvisionId": "apn_xxxxxxx"},
"email": "Email",
"firstName": "First Name",
},
)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-add-new-user",
"configured_props": {
"rydoo": { "authProvisionId": "apn_xxxxxxx" },
"email": "Email",
"firstName": "First Name"
}
}'TOOLS
Rydoo actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Add New User
actionCreates a new employee record in the company directory. See the documentationWritev0.0.2 -
Create Bank Transaction
actionManually pushes a bank transaction record for a specific user. See the documentationWritev0.0.2 -
Create Expense
actionAdds a new expense entry for a user. See the documentationWritev0.0.1 -
Create Project
actionSets up a new company project for expense allocation. See the documentationWritev0.0.2 -
Create Trip
actionRegisters a new business trip for a specific user. See the documentationWritev0.0.2 -
Export Expenses
actionRetrieves a list of expenses that have been exported, with optional filtering by date range, user, group, trip, or branch. See the documentationRead-onlyv0.0.2 -
Find Group
actionSearches for organizational groups by name to find their UUIDs. See the documentationRead-onlyv0.0.2 -
Get User Details
actionRetrieves full profile information, roles, and modules for a specific user. See the documentationRead-onlyv0.0.1 -
Reject Expenses
actionDenies a set of expenses with a specific rejection reason and message. See the documentationWritev0.0.1 -
Search Branches
actionFinds branches by name, ID, or active status. See the documentationRead-onlyv0.0.2 -
Search Payment Methods
actionFinds payment methods by type, branch, card type, status, and more. See the documentationRead-onlyv0.0.2 -
Search Projects
actionFinds active projects by name or reference ID. See the documentationRead-onlyv0.0.2 -
Search Trips
actionFinds trips by user, status, or name. See the documentationRead-onlyv0.0.2 -
Search User
actionSearches for users by email, first name, last name, free-text, card status, or external ID. See the documentationRead-onlyv0.0.2 -
Set Expense to Reimbursed
actionSets an expense as reimbursed. See the documentationWritev0.0.1 -
Update Expense Status to Reported
actionMarks an individual expense as included in a report. See the documentationWritev0.0.1 -
Update User Profile
actionModifies existing user details like names, nationality, or status. See the documentationWritev0.0.2
No Rydoo triggers are available yet.
- App slug
- rydoo
- Authentication
- OAuth
- Categories
- Business Management
- Actions
- 17
- Triggers
- 0
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Rydoo OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- company
- structure:read
- structure:write
- expenses:read
- expenses:write
- fields:read
- fields:write
- users:read
- users:write