
Connectors / Finance · HTTP Connector
Automate Rydoo with Tray.ai
Add an expense, upload a receipt and add a project in Rydoo, and start a workflow when Rydoo sends “Expense submitted”.
What can you do with Rydoo on Tray.ai?
Rydoo is an expense management platform where employees submit receipts and expenses, managers approve them, and finance teams export them to accounting or ERP systems. Tray.ai connects to Rydoo through the HTTP Connector, so your workflows can call the Rydoo API alongside the rest of your stack. API access comes through Rydoo's partner program or API plan, so you need approved credentials first.
- When Rydoo sends “Expense approved”, post the expense to your accounting system for reimbursement.
- Add a user in Rydoo for each new employee in your HR system, with the right approval group.
- When Rydoo sends “Expense rejected”, send the employee a direct message in your team chat with the reason.
- Mark expenses reimbursed once the payout clears in your payroll system.
- Connects through
- HTTP Connector
- Authentication
- OAuth 2.0
- Base URL
- https://api.rydoo.com
Set it up
Connect Rydoo to Tray.ai
Each step uses Rydoo's own API details, from its documentation.
Step 1
Sign in to Rydoo with OAuth 2.0
Ask Rydoo for API access. Once it's approved, set up an OAuth 2.0 authentication with the client ID and secret of an OAuth app you register with Rydoo. Sign in once and every step reads the token from there.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://api.rydoo.com as the base URL. Or paste a cURL example from Rydoo's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “Get an expense”
It's one of 22 documented actions, under Expenses. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from Rydoo events
Give Rydoo the URL of a Tray.ai webhook trigger. “Expense submitted” can then start a workflow, and so can 6 other events.
Workflows to build with Rydoo
Each one uses actions and events from Rydoo's own API documentation.
Send approved Rydoo expenses to NetSuite
When
Expense approved
Then
- Get an expense with its details
- Create an expense report in NetSuite
With NetSuite
Mark Rydoo expenses reimbursed after QuickBooks payment
When
A bill payment is made in QuickBooks
Then
- Get an expense to confirm the amount
- Mark expenses reimbursed for the paid employee
With QuickBooks
Add new Workday hires as Rydoo users
When
A worker is hired in Workday REST
Then
- Search for users to check for a match
- Add a user with manager and group
With Workday REST
Apps you can build on Rydoo data
Internal tools your team can build with an AI assistant, each one using Rydoo calls from its API documentation.
Expense review queue
Shows expenses as they are submitted and lets finance reject any that break policy.
Reimbursement tracker
Lists approved expenses and lets finance mark each one reimbursed once paid.
Project expense report
Shows exported expenses grouped by project so project leads can see what each one has spent.
Give your AI agents Rydoo tools
Build an MCP server on Rydoo in Agent Gateway and choose which actions your agents can call. Every call runs with access control and an audit trail. How Agent Gateway works
- Add an expense
- Upload a receipt
- Add a user
- List groups
- List projects
- Add a transaction
- Get an expense
- Reject expenses
What the Rydoo API covers
6 resources and 22 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. Rydoo gives API access on request, so approved credentials come first. Connecting it takes a few clicks: here's how.
Expenses
- Add an expense
- Get an expense
- Reject expenses
- Mark expenses reimbursed
- Report an expense
- List exported expenses
Receipts
- Upload a receipt
- Download a signed receipt
Users
- Add a user
- Search for users
- Get a user
- Update a user
Groups
- List groups
- Add a group
- Get a group
- Update a group
Projects
- List projects
- Add a project
- Get a project
- Update a project
Transactions
- Add a transaction
- List transactions
Events Rydoo can send to a Tray.ai webhook trigger
- Expense submitted
- Expense recalled
- Expense deleted
- Expense approved
- Expense controlled
- Expense unapproved
- Expense rejected
Checked against Rydoo's own documentation on 2026-10-22
How Tray.ai makes this work
Rydoo plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 12,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in Rydoo — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose Rydoo actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on Rydoo data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More finance apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every finance connector →
Frequently asked questions
What can a Tray.ai workflow do in Rydoo?
+
The Rydoo API documents 22 actions across 6 resources (Expenses, Receipts, Users, Groups, Projects, Transactions). For example: Add an expense; Upload a receipt; Add a user. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with Rydoo?
+
The Rydoo API uses OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which Rydoo events can start a Tray.ai workflow?
+
Rydoo sends 7 events to a webhook URL, for example: Expense submitted; Expense recalled; Expense deleted; Expense approved; Expense controlled; Expense unapproved; Expense rejected. A Tray.ai webhook trigger receives them and starts a workflow.
Do I need special access to the Rydoo API?
+
Yes. Rydoo gives API access on request, so you need approved credentials before a Tray.ai workflow can call it.
See Rydoo working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.