Workflow automation has never been more competitive. For years, platforms like Zapier and Make have dominated the space, but a newer breed of tools has tried to push things forward by building AI directly into the experience. One of those tools was Relay.app. It launched with a clean, modern interface and a bold promise: you could automate your work by describing what you wanted, not by connecting endless dropdowns and triggers. Then, almost without warning, the company announced it was shutting down, and the team would be joining Google’s Chrome team. When the story of Relay.app’s shutdown broke, many users were genuinely surprised.
What Was Relay.app?
Relay.app was a workflow automation platform designed to sit somewhere between traditional tools like Zapier and the new wave of AI agents. It let users connect popular apps like Gmail, Slack, Notion, Google Sheets, and hundreds of others, then build automations using a visual canvas. The differentiator was its AI features. Rather than forcing you to manually configure every trigger and action, Relay.app could generate workflows from a natural-language description.
For example, you could type something like “whenever a new invoice arrives in Gmail, save the attachment to Google Drive and send a Slack message to finance” and the platform would attempt to build that workflow for you. That kind of flexibility made it appealing to small teams that wanted to automate without hiring a developer.
Key features that set Relay.app apart
- Natural language workflow creation: Users could describe the automation they wanted in plain English, and Relay.app would map out the steps.
- Two-way data sync: Instead of just pushing data from one app to another, Relay.app could keep records in sync across multiple tools, which was useful for CRM and project management workflows.
- Human approval steps: You could build in manual checkpoints that required a person to approve an action before it ran, useful for things like sending outgoing emails or posting to social media.
- Simple scheduling and delays: You could set automations to run at specific times, or wait for a certain period before continuing.
These features weren’t unique in isolation, but combining them inside a modern, responsive interface put Relay.app on the radar of many people who had grown tired of the clunky builders in older platforms.
The Sudden Announcement of Relay’s Shutdown
In a blog post and email to users, the Relay.app team announced that the company was closing its doors. Staff would be joining Google’s Chrome team, likely to work on the browser’s built-in AI and automation features. The announcement hit the automation community hard. Many users had just started building their workflows on the platform, and some had even made Relay.app a core part of their operations.
We covered the details of Relay.app shutting down as it happened, and the reaction on social media made it clear that this wasn’t a struggling tool nobody cared about. There was genuine disappointment from users who appreciated the product. So why did a promising startup with a loyal following decide to stop?
What Led to the Shutdown?
There’s rarely a single reason a startup shuts down. In Relay.app’s case, it looks like a combination of timing, competition, and a very attractive offer from Google.
A brutal competitive landscape
Zapier has been around for more than a decade and has a huge library of integrations. Make is known for its flexibility and pricing. n8n is open source, which appeals to developers. On top of that, every week seems to bring a new AI-powered automation tool. So to stand out, you need more than a nice interface. You need a real technical moat.
The AI onboarding problem
While Relay.app could interpret natural language, the underlying models still had limitations. Users often had to tweak or rewrite workflows manually. That’s not a fatal flaw, but it means the AI wasn’t quite the “magic” experience the marketing suggested. In a market where everyone is racing to add AI, being merely good at it isn’t enough.
Google’s talent acquisition
The move to Google’s Chrome team suggests the founders saw an opportunity they couldn’t refuse. Google has been integrating more AI into Chrome for a while, from smarter browser suggestions to new assistant features. Hiring a proven team that knows how to build consumer-friendly automation tools could accelerate those plans. From Relay.app’s perspective, that may have been an easier path than fighting for market share alone.
What Happens to Relay.app Users Now?
If you were a Relay.app user, the shutdown naturally leaves a gap. The platform is no longer available, and you’ll need to move your workflows elsewhere. The good news is that most automation platforms support similar concepts. You can rebuild simple workflows in Zapier or Make fairly quickly, especially if you rely on common apps like Gmail and Slack.
For more complex automations, you’ll need to spend time understanding how the new platform handles variables, error handling, and logic. Relay.app had a clean visual model, so some of its workflows won’t translate perfectly to tools that rely heavily on code-first approaches.
This is also a reminder that any SaaS product can disappear. When you build critical processes on a platform, it’s worth checking whether it offers a way to export your workflows or at least document them. In the case of Relay.app, users were left with limited options for data export, and the community had to piece together workarounds. If you’re evaluating automation tools now, consider open-source options like n8n or tools with long track records, even if they aren’t as flashy.
Lessons for the Future of AI Automation
The story of Relay.app’s closure and the team’s move to Google isn’t just a piece of startup gossip. It offers real lessons for both founders and users in the AI automation space.
For founders: AI alone isn’t a moat
Building a tool that uses an AI model under the hood isn’t enough. The model companies, whether OpenAI or Anthropic, can quickly catch up. A durable company needs a distribution advantage, deep integrations, or a community that sticks around. Relay.app had strong early adoption but may not have found a way to make that stickiness overwhelming.
For users: don’t marry a single platform
It’s easy to build everything on a tool you love. But if that tool’s API changes, or the company gets acquired, or the product gets discontinued, you’re stuck. It’s smart to pick tools that support standardized formats, like webhooks and API access, so you can move elsewhere without too much pain.
What this means for Google Chrome
If the team is truly joining Chrome, we can probably expect some interesting features. Google has been experimenting with AI-driven browsing assistance, like summarising long pages, offering writing suggestions, and possibly automating repetitive tasks in the browser. The Relay.app team’s experience with visual workflow builders could make those features more approachable for everyday users.
It’s worth keeping an eye on Chrome canary builds over the next few months. If you see something that looks like a workflow automation pane hiding in the settings, it won’t be a coincidence.