Integrations
Your relationship graph talks to the rest of your stack
Storm OS works best when it can talk to the tools you already use, like the list you send from, the account your customers pay into, the room where your team talks, and the drive your files live on. Everything on this page is labeled live or coming soon, so you always know what you are getting today.
4 live today · 9 on the way · 3 platform features with dates
Live now
These work today, in the workspace you sign into
Open your workspace, connect your account, and these are ready to use right away, with no waitlist and no private beta.
One audience, whichever screen you opened it from
Send a campaign to a Storm segment and keep the audience in step, both ways.
- Build the segment in Storm OS from the contacts you already keep, and it lands in Mailchimp as an audience.
- It stays in step in both directions, so you are never reconciling two lists by hand and never guessing which one is right.
- Storm OS sends campaign email itself, from your own domain. Connect Mailchimp and your campaigns send through your Mailchimp account instead, on its sending reputation, and disconnecting hands sending back.
Sign in without inventing another password
One tap in, for you and everyone you invite.
- It works for the first person in and for the fifteenth, so adding a teammate is as simple as sending an invitation.
- Storm OS asks Google only who you are: your Google account ID, your name and your verified email address. It never reads your mail, your calendar or your files.
- Email and password still work too, and the button on the sign-up and sign-in screens is Google’s own, drawn by Google.
The intelligence in Storm OS, and the choice of whose account pays for it
The agents run on Claude, from Anthropic. Bring your own Anthropic key and the usage is yours.
- The five agents run on Anthropic’s Claude models: Haiku for summaries and the daily assistant, Sonnet where a job needs more judgment, and Claude’s own web search for research. Every plan includes a monthly allowance of AI credits that these agents draw on.
- The assistant is on from the start, an admin can switch it off during setup or in Settings under Assistant, and nothing is sent while it is off. While it is on, record content and the text of any file you hand an agent go to Anthropic’s API. We never train a model on your records, and Anthropic’s terms forbid it from training on what we send.
- Prefer to own the usage? An admin pastes your own Anthropic API key in the same settings and chooses which agents run on it, and those calls bill to your Anthropic account instead of using the workspace’s AI credits. The key is encrypted when you save it, and only its last four characters are ever shown after that.
Live nowGet paid by card, straight into your own Stripe account
Card payments on your invoices, charged on the Stripe account you already have.
- It comes with Storm Finance, in beta. An admin connects it once, from Admin under Finance, by linking the Stripe account you already run, with no new payout setup and no second onboarding.
- Every invoice you send then carries a Pay Now button. Your customer pays on Stripe’s own checkout page with the payment methods you have switched on in Stripe, and the charge is made on your account, so the money lands in your Stripe balance.
- The invoice marks itself paid when Stripe confirms the payment. Storm OS adds no fee of its own, so Stripe’s usual processing fees are the only ones, and disconnecting turns Pay Now off while your other ways to pay keep showing.
Coming soon
What we are building next
These integrations are planned but not in the product yet, and we list them here so you can see where Storm OS is headed before you move your company onto it.
Email and lists
This is the same two-way segment sync Mailchimp has today, pointed at whichever sender you already pay for.
The same segment sync, for the list you already run there.
Lightweight sending, connected to the records that know who is who.
Campaigns and transactional mail, all working from the same audience.
Where the work gets talked about
It connects your relationship data to the rooms where your team already talks and decides.
A Storm OS Zap, so thousands of other tools can reach your records.
Early 2027
- A Storm OS Zap puts your relationship graph on the other end of the thousands of connections Zapier already has, so a new signature can start whatever your company does next, wherever that happens.
- Triggers for the moments that matter: a deal moves stage, a proposal is signed, an invoice is paid, a project task comes due. Actions for the other direction: create a contact, log a note, raise a task, start a project.
- It is the answer for every tool we will never build a native connection to, and it arrives in early 2027.
Deal and project news in the server your team already lives in.
The deal moved, the proposal was signed, the invoice was paid, and it all lands in the channel.
Pull a spec or a brief straight into the project that needs to read it.
Where your files already live
Attach files right where they already live, so you never end up with a second copy that goes stale.
Attach what already lives in Drive, without downloading it first.
Same for Dropbox, the file stays where it is and the record knows about it.
If the one you need is not on this page, write to us and tell us, because the founders who are waiting on an integration decide what we build next.
The platform
Three doors into your own workspace
These let you, or any tool you choose, read and write your own data directly, and put the everyday rules in your own hands, so you never have to wait for us to build a specific integration first.
API access and documentation
Read and write everything in your workspace, with docs written in plain language.
An API key goes through the same permission checks the app itself uses, so it can never read anything its owner could not already open in the product.
It is also what makes the next one possible: an MCP server is a small, well-behaved client of your own API.
MCP server
Point Claude, or any MCP client, straight at your own relationship graph.
MCP, the Model Context Protocol, lets an AI tool read a system for itself, which means no more copying a record into a chat window and hoping you grabbed the part that mattered.
When ours lands, that connection is live: the client reads your workspace under your account and your permissions, so you can ask about your pipeline in the tool you already have open. Nothing is copied anywhere to make it work, and nobody outside your workspace ends up holding a second copy of your data.
MCP is an open protocol, so we are not tied to any one AI vendor, and any tool that supports it can connect to your workspace.
Workflow and Automation Studio
Build the rules your business already runs on: when this happens, do that. Route work, raise documents, send the follow-up, without writing code.
Every business runs on rules somebody is holding in their head: when a proposal is signed, raise the invoice and open the project. When a deal goes quiet for two weeks, put it back on my list. The Studio is where you write those down once and let the system keep them.
A rule is a plain sentence you build from menus, so you are picking a trigger and picking what happens next rather than learning a scripting language.
Rules run under the permissions of the person who owns them, and every run is written to the audit log, so you can always see what fired, when, and what it touched.
The wider roadmap
- NovemberStorm Service for its first group of beta customers, and API access in private beta
- DecemberThe MCP server and the Workflow and Automation Studio, both in private beta
- Early 2027A Storm OS Zap, so Zapier can reach your relationship graph
Your tools should keep themselves in sync
Start with your contacts, connect Mailchimp and Stripe, sign in with Google, and let the rest arrive as they go live. Every connection is switched on per workspace, so one you never open costs you nothing.
No credit card to start · 30-day trial · Live and customized in 15 minutes