Connect any software to River’s AI
Bring us your CRM, your ERP, or your in-house tool. Even something nobody has heard of. We hook it up so River’s AI can actually do work in it: search, create, update, anything.
Why connect
More software working for you,
less of you working for it.
Most of the day at a small startup is small handoffs between tools. Move data here, draft something there, update a record somewhere else. Wire those tools to River and the AI takes the handoffs.
Punch above your weight.
A small team plugged into the right tools runs like a much bigger one. River turns your stack into a workforce.
AI that does the work.
Reading is easy. The win is when AI can also write back: send the email, update the deal, post the report, file the invoice.
No more tab-switching tax.
Stop bouncing between Stripe, your CRM, and three Google Docs to ship one task. Tell River. It uses your tools.
How it works
From your software to your agent
in four steps.
Same path every time. We come back with a working connector and a clear timeline.
- 01Securely share accessHand us API keys, OAuth, or a login. Encrypted on arrival, never written to logs.
- 02Map what it can doWe catalog the actions and data your software exposes. Search, create, update, anything it offers.
- 03Build the connectorWe package it as a portable connector your AI can call. Auth, retries, and rate limits handled.
- 04Plug it into your agentIt shows up in your Integrations panel. River’s AI starts using it in chat and automations.
Two ways to connect
We pick the path that fits your software.
Some software has an API. Some doesn’t. We use whichever route gets you to a working connector fastest.
Through its API
If your software exposes an API, we use it. Fast, runs in the cloud, and scales without breaking a sweat.
- Cloud-native, no desktop app needed
- Auditable. Every call is logged.
- Works the same way OAuth integrations do
Through the screen
No API? No problem. River’s desktop app opens the software in a real browser and clicks through it the way a person would.
- Works on tools with no API at all
- Honest trade-off: needs the desktop app, slower per task
- Best for closed platforms and legacy software
Security
Built secure, end to end.
Same security posture we use for the rest of River. Encryption at rest, scoped access, audit logs, and revocable connections. We share architecture docs and walk your security team through it.
Encrypted on arrival
Fernet symmetric encryption. Key held in AWS Secrets Manager.
Decrypted only at call time
Never written to disk in plain text. Never written to logs.
Revocable any time
Rotate or remove access from your Integrations panel. Drops immediately.
We can sign NDAs, share architecture docs, and walk your security team through it. Talk to security
Use it anywhere
The same connector works in any AI system you use.
What River builds for you follows MCP, an open standard. Run it in River today. Plug it into Claude, ChatGPT, or Cursor tomorrow. Same connector, same software, same access. Your team isn’t locked into one assistant.
FAQ
Frequently asked.
What if my software does not have an API?
We can still connect it. River has a desktop app that opens the software like a person would and clicks through it for you. It is slower than an API and needs the desktop app running, but it works on tools that do not expose a clean API.
How do you keep our credentials safe?
Keys are encrypted the moment you give them to us. Same Fernet encryption we use for Gmail, Slack, and other OAuth tokens, with the key held in AWS Secrets Manager. They are only decrypted in memory at the moment of a tool call. Never written to disk in plain text. Never written to logs.
Will the connector still work if we leave River?
Yes. What we build follows MCP, an open standard supported by Claude, ChatGPT, Cursor, and others. The connector is yours. Run it in River today, plug it into another assistant tomorrow.
Can you build for our internal tool, the one only we have?
That is the most common request. Show us how you use it, give us read-only access to start, and we will come back with a connector. NDAs are fine.
How long does it take?
A few days for a small connector with a clean API. A couple of weeks for something more involved or computer-driven. We come back with a timeline once we have seen the software.
Who owns the code?
You do. The connector is yours. We can also host it for you inside River if you do not want to run anything yourself.
Can our security team review the connector?
Please. We will share architecture docs, walk through the encryption story, and answer questions on a call. Many customers have us run through their full vendor review.
Tell us what to plug in.
We’ll come back with a plan.
Drop us a note about the software. We come back with a timeline and a path forward, usually within a day.