Connect anything. Romy reads the docs, asks for your key, and builds it.

Say how you work, in your own words. Romy goes to the other company's developer site, reads how its API works, asks for your key in a secure box, and builds it in your Salesforce while you sit back. Then it tries it with real data and shows you what it did. It's built into your Salesforce, so it keeps working when your Mac is closed.

Leads to #sales, jobs to #ops, big discounts to you.

Any app with an API

Romy doesn't pick from a list of connectors. It reads the other company's developer docs as they are today and builds what you described.

Keys stay locked away

You paste a key into the secure box. It goes straight into Salesforce's encrypted credentials and never shows in the chat.

Tried before you rely on it

Romy runs each piece with real data, shows you it working, then lists what it changed, each with Show me and its own Undo.

Romy works in your Salesforce and connects it to QuickBooks, Slack, Stripe, Gmail, Outlook or any tool you already use. If it has a sign-in, Romy works out the connection from the tool's own docs.

Built, tested, then switched on nothing goes live until you've seen it work

A connection is its own project, with its chats, its plan and everything it changed in one place. Here's how the QuickBooks one goes.

  1. You say what should happen

    “When a deal is won, make the invoice in QuickBooks.” Romy recognises the tool, names the project and says what connecting it involves.

  2. Romy plans it with you

    It reads the tool's own docs as they are today and writes the steps in the Plan beside the chat. Change anything before it starts.

  3. You sign in yourself

    Romy opens the tool's sign-in page in its browser and hands it to you. Take over, sign in, press Done.

  4. It builds it in your Salesforce

    The connection, the automation and any fields it needs, each shown on a card with its own Undo.

  5. It tries it on a test deal

    Romy marks a test deal won, checks the invoice QuickBooks made and the number that came back, and shows you both.

  6. Then it's switched on

    Only after you've seen it work. From then on it runs in your Salesforce, with Romy open or not.

Bring in numbers from anywhere on the web and keep them up to date on their own

“Put this week's diesel price on our home page, and tell me when it goes over $4.” Romy finds the official source and reads its docs as they are today. When the source needs a key, it opens the sign-up for you, and you paste the key into a locked box that goes straight into Salesforce. Then it builds the connection, sets it to refresh by itself, and puts the number where your team works.

Romy's browserRomy is working
Finding the diesel price source

What you're seeing: Maya wants to keep an eye on what the trucks cost to run. Romy finds the U.S. Energy Information Administration's free price data, opens its sign-up and hands her the page. She registers with her email, pastes the key from EIA's email into the locked box, and Romy connects Salesforce to it, sets the price to refresh every Monday, puts a diesel card on the office's home page and sets up an email to Maya the week it goes over $4.

Official sources, read today

Romy reads the provider's own docs as they are now, not from memory, and tells you where every number comes from.

Keys never land in the chat

You paste a key into a locked box. Only Salesforce keeps it, in its encrypted credentials, so it never shows in the conversation.

Keeps running without Romy

The refresh is built into your Salesforce, so the number stays current every week, even when your Mac is off.

Your passwords stay yours Romy hands you the page

Romy gets you to the sign-in and steps back. Keys go into a locked box that only Salesforce keeps. What it builds runs in your own Salesforce.

You sign in yourself

On a sign-in page the browser says “Sign in here yourself”. Press Take over, sign in, press Done, and Romy carries on.

Keys in a locked box

Paste a key into the box in the chat and it goes straight into Salesforce's encrypted credentials. It never shows in the conversation.

Yours to keep or undo

Every part of a connection has its own card with Undo, and the project keeps the whole history in one place.

Questions people ask

Does it keep running when my Mac is closed?

Yes. What Romy builds lives in your Salesforce: the connection, the automation and any fields it adds. Your Mac only needs to be on while you're working with Romy.

Who signs in to QuickBooks?

You do. Romy opens the sign-in page in its browser beside the chat and steps back. Press Take over, sign in, press Done, and Romy carries on from there. Passwords stay yours.

What about API keys and secrets?

When a tool gives you a key, Romy asks for it in a locked box in the chat. It goes straight into Salesforce's encrypted credentials. Romy doesn't show it in the chat.

My tool isn't one you've heard of. Can it still connect?

Yes. Romy doesn't work from a fixed list of connectors. If a tool has a sign-in and an API, Romy reads its docs as they are today, builds the connection with you and tries it before anything is switched on.

Can I turn it off again?

Every part Romy built has its own card with Undo. Undo puts that part back the way it was before, and the rest keeps working.

Ask for the first thing on your list and watch it happen beside the chat

Free until Q2 2027. Bring your own Claude or ChatGPT plan, no token charges.