Integrations
The whole point is not being one more silo
A relationship system that only knows what you typed into it is another island with a nicer font. Integrations are how the graph reaches the rest of your stack: the list you send from, the room where the work gets talked about, the drive your files already live on. What is live says live. What is not built yet says that just as plainly, because a logo grid that blurs the two is how trust gets spent.
2 live today · 7 being built · 2 platform surfaces with dates
Live now
These work today, in the workspace you sign into
No waitlist, no private beta, no asterisk under the logo. Open your workspace, connect the account, and these work the way the rest of the product works.
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, out of the graph 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.
- Campaigns ride along: the campaign you send is a campaign on your own Mailchimp account, run with your own sending reputation.
In without inventing another password
One tap in, for you and everyone you invite.
- Works for the first person in and for the fifteenth, so adding a teammate is an invitation rather than a password reset.
- Google draws its own button. We do not redraw anybody else’s mark, here or in the product.
- Email and password still works. Nobody is forced onto one way in.
Coming soon
Being built, and marked that way
None of the tiles below is in the product yet. They are here because you deserve to know where this is going before you move a company onto it, not because a wall of logos makes a page look busier than it is.
Email and lists
The same two-way segment sync Mailchimp has today, pointed at the sender you already pay for.
The same segment sync, for the list you already run there.
Lightweight sending, connected to the graph that knows who is who.
Campaigns and transactional mail against one audience.
Where the work gets talked about
The graph reaching into the rooms where decisions actually get made.
The deal moved, the proposal was signed, the invoice was paid. In the channel.
Pull a spec or a brief straight into the project that needs to read it.
Where your files already live
Attach what already exists somewhere else, instead of making a second copy of it that goes stale.
Attach what already lives in Drive, without downloading it first.
Same for Dropbox: the file stays where it is, the record knows about it.
If the one you need is not on this page, write to us and say so. The order these get built in is decided by which founders are actually blocked, not by which logo looks best on a website.
The platform
Two doors into your own workspace
These are not connections to somebody else’s product. They are the way you, or a tool you choose, read and write your own graph directly, without asking us to build the integration first.
API access and documentation
Read and write your own workspace, with docs written the way this product is.
It runs through the same permission engine the screens do, so a key can never read something 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, is the plug that lets an AI client read a system directly instead of being pasted into. Today you copy a record into a chat window and hope you copied 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 graph.
MCP is an open protocol, so this is not an arrangement with anybody. It is a door, and any client that speaks it can walk through.
The wider roadmap
- Late AugustAPI access and documentation
- SeptemberService, and the MCP server
- OctoberLanding pages, forms and surveys, native to Marketing
Your tools should not have to be kept in agreement by hand
Start with the graph, connect Mailchimp, sign in with Google, and let the rest arrive on the dates above. Everything on this page is switched on per workspace, so a connection you never open costs you nothing.
No credit card to start · 30 day trial · Be live and customized in 15 minutes