Connections
Ask your crew
to go and look.
Your files in Dropbox. Your payments in Stripe. What your team said in Slack. Twenty-one services, each one opened with your own login — so the next time the answer is inside one of them, your crew can go and look instead of you.
- Slack
- Notion
- GitHub
- Dropbox
- Atlassian
- Zapier
- Linear
- Figma
- Airtable
- Stripe
- Asana
- Intercom
- PayPal
- Sentry
- HubSpot
- Canva
- Square
- MMonday
- Cloudflare
- Vercel
- Box
What changes
Asking becomes one sentence.
“What came in this week?”
Stripe, Square and PayPal each run their own doorway. Connect the one you use, and the numbers behind that question come within your crew’s reach.
“Find the proposal we sent them.”
Dropbox and Box become folders your crew can look in — so finding a file, or finding out what it says, is an ask rather than an afternoon.
“Catch me up.”
Slack holds what your team said; Notion holds what they wrote. Connected, both become places your crew can go instead of you.
The honest part
Watch green get earned.
A saved password is not a connection. Plenty of software disagrees. Amber means something is stored that has never answered. Green only arrives after a real request has come back — and when one fails, the app says so, in the words the failure actually used.
- Grey — nothing set up. No credential, no claim.
- Amber — stored, never proven. Not shown as working.
- Green — earned by a real answer, and it says when.
- Red — failed, and says how. An error in words, not a spinner.
The Applications screenThis screenshot is built into the page, so if it is missing the page itself is damaged. Ask for access and see the real thing instead.
The actual screen, set up so all four states show at once — including what failure looks like, in the app’s own words.
How it works
What MCP actually means.
MCP stands for Model Context Protocol. It is a standard doorway a company puts on its own service, so an assistant can be let in at the front. Slack runs the Slack doorway. Notion runs the Notion one. All twenty-one work that way — the company’s own address, and nobody in the middle holding a copy of your keys.
Nothing to install
These run on the companies’ own servers. Nothing to download, nothing to configure — an address and your own sign-in.
Kept on your machine
In the app’s own words: “Stored encrypted in this computer’s own credential manager, never in a file and never shown again — not even here.”
Add anything else
It is an open standard, so our list is not the limit. If something you use has a doorway, point helloim.ai at it yourself — under Settings → Applications.
Connecting OpenAI
Why it asks for a key, not a login.
OpenAI runs on keys, not logins — so connecting it means bringing your own key. It's a little more setup, and it buys you something: your account stays yours, your bill stays yours, and the key never passes through us.
Why do I have to paste a key instead of just logging in?
For a desktop app, OpenAI doesn't offer a "log in and we'll use your account" option — the API runs on keys, not logins. Where a "Sign in with OpenAI" button exists, it only proves who you are; it doesn't hand an app access to the API or your billing. So a key isn't a workaround, it's the real door.
Can't I use my ChatGPT Plus subscription?
No — and that's OpenAI's rule, not ours. A ChatGPT subscription (Plus, Pro, Business, Enterprise) is for the ChatGPT app. API access is billed separately through OpenAI's developer platform, and a subscription can't be spent by another app. Anything claiming to route ChatGPT through a third-party app is doing something OpenAI's own rules forbid. A key from your platform account is the supported way, and it's free to create.
Where does my key go — is it safe?
It goes into your operating system's own credential store — Credential Manager on Windows, the same place your other saved logins live. Not into a file we write, not into a log, not onto our servers — we never receive a copy. That's the reason it works this way instead of through an account on our side.
Who pays for what?
Your OpenAI usage bills to your own account, at OpenAI's rates — you can see it, cap it, and set budgets in your platform dashboard. helloim.ai is free while it's in early access, and we don't mark up your usage or take a cut.
How do I get an OpenAI key?
Sign in to (or create) an account on OpenAI's developer platform at platform.openai.com/api-keys, then create a new key. OpenAI shows it to you once, so copy it and paste it into helloim.ai — that's the whole setup. Setting this up for a team? OpenAI also supports project-scoped keys, which keep usage separate.
Can I remove or change my key later?
Any time, from either end. In helloim.ai you can replace or delete the key, and it leaves your credential store with it. On OpenAI's side you can revoke it outright, which cuts off access instantly. And the connection light only turns green once a real request has actually gone through.
Connecting Gemini
Why it asks for a key, not a login.
Like OpenAI, Gemini connects with a key you bring rather than an account you sign into. Your usage bills to your own Google account — which includes a generous free tier — and the connection runs straight from your machine to Google.
Why a key instead of just signing in with Google?
Because for an individual using a desktop app, Gemini's path is an API key from Google AI Studio. Google does offer a sign-in-style option, but it's aimed at its enterprise Vertex AI product, not at connecting a personal account to an app like this. So the key isn't a workaround — it's the ordinary door for one person connecting one machine.
Where does my key go — is it safe?
Into your operating system's own secure credential store — Credential Manager on Windows — the same vault your other saved logins live in. Never into a file we write, never into a log. We don't hold a copy of it.
Who pays — and what's this about the free tier?
Your usage bills to your own Google account, at Google's rates, and the free tier is generous enough to try this properly before spending anything. On the free tier, Google may use your prompts and replies to help improve their models; switching on pay-as-you-go billing in AI Studio stops that. It's your choice, and you can change it whenever you like. helloim.ai is free while it's in early access.
How do I get a Gemini key?
Go to aistudio.google.com, sign in with your Google account, and use the "Get API Key" button to create one. Copy it, paste it into helloim.ai, and that's the setup done.
Can I remove or change my key later?
Any time, and from either end. In helloim.ai you can replace the key or delete it, and it leaves your machine's credential store with it. In Google AI Studio you can revoke that key outright, which cuts off access straight away. Connect it, test it, and the light only turns green once a real request has actually gone through.
Connecting OpenClaw
Nothing to connect — it's already on your machine.
OpenClaw is the private one. It runs entirely on your own computer, so there's no account to create, no key to paste, and no bill to set up. Connecting it is really just opening it.
Do I need a key or an account for OpenClaw?
No. Because OpenClaw runs locally, on your own machine, there's nothing to sign into and no key to bring. Where the other brains ask you to connect an outside account, OpenClaw just starts a session — the connect step is opening it, and that's all.
Does anything leave my computer?
Your conversation is handled on your own computer — there's no account it's sent to, and no server of ours in between. That's what makes OpenClaw the private choice here.
What does it cost to run?
There's nothing to bill. The other brains charge for usage against your own account with them; OpenClaw runs on hardware you already own, so there's no meter and no account to top up. helloim.ai itself is free while it's in early access.