Relay.app Shutdown: What Happened, What Users Can Still Do and the Best Alternatives in 2026
Affiliate Disclosure: We review products independently. When you buy through our links, we may earn a commission or a compound recurring commission at zero extra cost to you. Read our editorial policy.
Updated: November 19, 2026
If your business relied on Relay.app for workflow automation, there is an important update: Relay.app has shut down.
The company ended its service in September 2026. Its official website now confirms that all accounts, workflows and run history have been permanently deleted.
This changes the advice that appeared in earlier Relay.app reviews and migration guides. Users can no longer log in to export their workspace, retrieve workflow configurations or access their previous run history.
For businesses that downloaded their data before the shutdown, the next step is to use those saved files to rebuild important workflows elsewhere. For users who did not export their data, the options are more limited: reconstruct the workflows from existing business records, documentation and connected applications.
This guide explains what happened to Relay.app, what information is no longer accessible, how to approach migration after the shutdown and which automation platforms are worth evaluating as replacements.
1. What Happened to Relay.app?
Relay.app was an AI-powered workflow automation platform designed to help businesses connect applications, automate repetitive work and introduce AI into operational processes.
It combined conventional workflow automation with AI actions and human approval steps.
The platform appealed to businesses that wanted more flexibility than simple trigger-and-action automation without necessarily building workflows through code.
However, Relay announced that it was winding down its service in July 2026.
The shutdown followed a staged timeline.
Relay.app shutdown timeline
| Date | What happened |
|---|---|
| July 16, 2026 | Relay announced its shutdown and disabled new sign-ups and free-to-paid upgrades |
| August 15, 2026 | Free accounts lost access |
| September 14, 2026 | Paid customer access ended at 11:59 PM Pacific Time |
| September 2026 | Relay completed its shutdown |
Relay’s current official website confirms that the service has shut down and that accounts, workflows and run history have been permanently deleted.
Official source: Relay.app — Shutdown Announcement.
Did Google acquire Relay.app?
No. Relay’s shutdown coincided with founder Jacob Bank and several members of the team joining Google’s Chrome organisation.
TechCrunch reported on August 17, 2026, that Bank was returning to Google as VP of Product for Chrome, where he would lead product and developer relations teams.
This was a hiring move, not an acquisition of Relay.app.
There is no basis for assuming that Google acquired Relay’s software, brand or customer accounts.
Source: TechCrunch — AI Automation Startup Relay Shuts Down, Staff Joins Google’s Chrome Team.
2. Can Existing Relay.app Users Still Access Their Workflows?
No.
This is the most important distinction for anyone reading older Relay.app migration guides.
Before September 14, paid users had a window to export their information and prepare for the transition. That window has now closed.
Relay’s current website explicitly states that:
- Accounts have been permanently deleted.
- Workflows have been permanently deleted.
- Run history has been permanently deleted.
Consequently, users should not expect to log in, request a new workspace export or retrieve their old workflow configurations through Relay.
What if you exported your workspace before shutdown?
If you downloaded your Relay workspace before the deadline, check your local files and backups.
Earlier export guidance described workspace archives containing information such as:
- Workflow definitions and structure.
- AI build prompts.
- Workflow execution history.
- Individual run information.
- Table data.
The exact contents depend on what was included in the export and which features the workspace used.
Keep the original archive unchanged and create a separate working copy before examining or editing its contents.
What if you did not export your data?
If you missed the shutdown deadline, do not assume that Relay can restore your workspace.
Instead, investigate the information that may still exist elsewhere in your business:
- Search local computers and cloud storage for previously downloaded Relay export files.
- Check email attachments and messages containing workflow descriptions or configuration notes.
- Review screenshots and documentation created during earlier workflow development.
- Examine the connected applications for existing records, automation logs or integration settings that remain available.
- Ask the employees or contractors who originally built the workflows whether they retained copies of their configurations.
The objective is to reconstruct the business process from surviving information, not to retrieve data from a service that has permanently shut down.
Important: Rebuilding a workflow from screenshots or business records is not the same as recovering its original configuration. Some conditions, mappings, prompts and edge cases may be missing.
3. What Made Relay.app Different?
Although Relay.app is no longer available, understanding its capabilities is useful when selecting a replacement.
Its appeal came from combining conventional automation with AI and human participation.
A. Human-in-the-loop automation
One of Relay’s notable capabilities was its ability to pause a workflow and request human input or approval before continuing.
This was useful when a process needed both automation and judgement.
For example:
<escape>AI generates a draft
|
v
Manager reviews the content
|
v
Approved?
/
Yes No
| |
v v
Publish Revise</escape>
This approach is useful for agencies managing client communications, content approvals, lead qualification and document preparation.
The principle remains relevant even though Relay has closed: not every business process should run without human oversight.
B. AI within workflows
Relay combined conventional workflow steps with AI-powered actions.
Businesses could use AI to help with activities such as:
- Summarising information.
- Extracting data from documents.
- Classifying incoming requests.
- Drafting content.
- Processing information before passing it to another application.
The advantage was the ability to include AI within a broader business process rather than treating it as a separate activity.
C. Visual workflow building
Relay provided a visual approach to designing automation.
Users could connect different steps, create conditional paths and introduce human review into a process.
This made the platform relevant to non-technical business teams that wanted to build more sophisticated workflows without writing traditional application code.
D. Reusable workflow logic
Reusable sequences helped organise recurring automation steps.
For example, an agency could use a common client-notification sequence across several workflows rather than manually recreating the same logic each time.
When evaluating alternatives, businesses that depended on these capabilities should check whether the replacement supports reusable workflows, sub-workflows or equivalent components.
4. Best Relay.app Alternatives in 2026
There is no exact one-to-one replacement for Relay.app.
The right platform depends on which Relay capabilities your business actually used.
The following three platforms are worth evaluating.
1. Zapier: Best for broad application integration
<row align=start gap={3}> <AsyncImage query=”Zapier workflow automation editor interface screenshot” aspectRatio=”5:4″ maxWidth=”112px”/> <box flex=”1″ gap={1}> **<Entity value=”Zapier” category=”software”/>**
<badge color="success">Best for integration breadth</badge>
Zapier is a strong option for businesses that need to connect a wide range of business applications through visual workflows.
<text color="secondary" size="xs"><Link url="https://zapier.com/" title="Official website"/></text></box> </row>
Zapier is particularly relevant when your Relay workflows connected multiple SaaS applications.
Its ecosystem supports a large catalogue of integrations, making it useful for agencies working with clients that use different CRM, email, project management and marketing platforms.
Its AI building capabilities can also help users create and modify workflows.
Consider Zapier if:
- Your workflows connect several mainstream business applications.
- Your team prefers a relatively straightforward automation interface.
- You need broad integration coverage.
- You want to build conventional trigger-and-action workflows.
Watch out for: Task-based billing, plan limits and additional costs as workflow usage grows.
Read our Zapier Review for a closer look at its pricing and capabilities.
2. Make.com: Best for complex visual automation
<row align=start gap={3}> <AsyncImage query=”Make.com visual automation scenario builder interface screenshot” aspectRatio=”5:4″ maxWidth=”112px”/> <box flex=”1″ gap={1}> **<Entity value=”Make” category=”software” disambig=”Visual workflow automation platform formerly Make.com”/>**
<badge color="success">Best for complex workflows</badge>
Make offers a visual scenario builder with routing, filtering, data transformation and multi-step automation.
<text color="secondary" size="xs"><Link url="https://www.make.com/" title="Official website"/></text></box> </row>
Make is worth considering if your Relay workflows involved multiple branches, conditional processing or complex data movement.
Its visual canvas makes it possible to inspect how information travels through a workflow and how different conditions affect subsequent actions.
Consider Make if:
- Your workflows contain several conditional branches.
- You need to transform data between applications.
- Your business processes involve multiple connected services.
- You want detailed control over the execution sequence.
Watch out for: Its credit-based usage model and the additional learning required to build and maintain complex scenarios.
Read our Make.com Review for a detailed assessment.
3. n8n: Best for technical teams seeking greater control
<row align=start gap={3}> <AsyncImage query=”n8n workflow automation node editor interface screenshot” aspectRatio=”5:4″ maxWidth=”112px”/> <box flex=”1″ gap={1}> **<Entity value=”n8n” category=”software”/>**
<badge color="success">Best for technical flexibility</badge>
n8n is a workflow automation platform with visual workflow building, code capabilities and self-hosting options.
<text color="secondary" size="xs"><Link url="https://n8n.io/" title="Official website"/></text></box> </row>
n8n is particularly relevant to businesses that want greater control over workflow execution and infrastructure.
Its self-hosted option can appeal to technically capable teams that want to manage their own deployment.
However, self-hosting introduces responsibilities around infrastructure, security, backups, updates and monitoring.
Consider n8n if:
- Your team has technical expertise.
- You need custom JavaScript or API-based processing.
- You want self-hosting options.
- You need more control over the automation environment.
Watch out for: The operational responsibilities associated with hosting and maintaining the platform.
Read our guide to Migrating from Zapier to n8n.
5. Which Relay.app Alternative Should You Choose?
Do not select a replacement simply because it has a similar feature list.
Start by identifying what your original Relay workflows actually did.
| Your previous Relay requirement | Platform to evaluate first |
|---|---|
| Simple application-to-application automation | Zapier |
| Large integration ecosystem | Zapier |
| Complex conditional routing | Make |
| Visual data transformation | Make |
| Custom code and API processing | n8n |
| Self-hosted workflow infrastructure | n8n |
| AI-assisted workflow creation | Compare Zapier and Make |
| Human approval before an action | Test the exact approval process in each shortlisted platform |
What if human approvals were central to your Relay workflows?
This deserves special attention.
Do not assume that every automation platform offers an equivalent to Relay’s human-in-the-loop steps.
Before choosing a replacement, test whether it can:
- Pause the workflow and wait for a person.
- Assign the review to the correct employee.
- Present the information that needs approval.
- Capture an approval or rejection.
- Resume the correct workflow branch.
- Handle missed deadlines or rejected requests.
- Record the outcome for future reference.
A platform may offer notifications and conditional paths without providing the exact approval experience your business previously relied on.
Test the complete process before migrating business-critical workflows.
6. How to Rebuild Relay.app Workflows After the Shutdown
If you have a saved Relay export, use it as a reconstruction reference.
If you do not, begin by documenting the process from the applications and records that remain available.
The following approach works for both situations.
Step 1: Create a workflow inventory
List the workflows your business previously operated in Relay.
For each one, record:
| Field | What to document |
|---|---|
| Workflow name | The process being automated |
| Business purpose | Why the workflow exists |
| Trigger | What starts the process |
| Source application | Where the information originates |
| Actions | What the workflow does |
| Conditions | What determines the next step |
| AI instructions | Prompts and model requirements |
| Human approvals | Where employee input is required |
| Destination applications | Where information is sent |
| Business owner | Who is responsible for the process |
| Priority | Critical, important or non-essential |
If you have an exported workflow prompt or JSON file, use it to populate this inventory.
If you do not, reconstruct the information from emails, screenshots, business records and the people who operated the workflow.
Step 2: Prioritise workflows by business impact
Not every workflow needs to be rebuilt.
Divide them into three groups:
| Priority | Description | Recommended action |
|---|---|---|
| Critical | Supports revenue, client delivery or important business operations | Rebuild first |
| Important | Saves recurring administrative effort | Rebuild after critical processes |
| Non-essential | Rarely used or no longer required | Consider retiring it |
A workflow that sends a client invoice or updates a sales record deserves more attention than an automation that produces an occasional internal notification.
Step 3: Reconstruct the workflow logic
Before opening Zapier, Make or n8n, document what the workflow needs to accomplish.
For example:
Business requirement: Automatically create a project when a new client completes the required onboarding steps.
The reconstructed process might be:
- Receive the completed client onboarding record.
- Find the corresponding CRM contact.
- Confirm that the contract has been signed.
- Check that the required payment condition has been met.
- Create the project using the appropriate template.
- Assign the account manager.
- Notify the delivery team.
- Save the project reference in the CRM.
This is a business-process description, not a guarantee that every platform supports each action natively.
Verify the necessary integrations and permissions before implementation.
Step 4: Reconnect applications and credentials
Relay’s shutdown means that its old connected application credentials should not be treated as reusable.
For the replacement platform, establish fresh connections through the relevant application authorisation process.
Review:
- OAuth permissions.
- API keys.
- Webhook endpoints.
- Service accounts.
- Access scopes.
- Client-specific credentials.
- User ownership.
- Expiry and rotation policies.
Do not copy credentials into unsecured documents or share them with contractors through ordinary email.
Step 5: Rebuild and test one workflow at a time
Do not migrate the entire automation environment in one attempt.
Start with one representative workflow and verify:
- Trigger behaviour.
- Data mapping.
- Conditional paths.
- AI output quality.
- Human approvals.
- Error handling.
- Duplicate-event handling.
- Final output in the destination application.
If you have historical Relay run exports, use selected records as reference test cases.
If you do not, create controlled test data that represents normal and exceptional scenarios.
Step 6: Document the replacement
Once a workflow is working, save:
- Its purpose.
- A diagram or screenshot.
- Trigger and action descriptions.
- Required credentials and permissions.
- Error-handling instructions.
- Business owner.
- Maintenance responsibility.
This reduces the risk of becoming dependent on another undocumented automation system.
7. What Should Businesses Learn From the Relay.app Shutdown?
Relay’s closure is a reminder that automation platforms are business dependencies, not just convenient productivity tools.
A workflow can become critical even when it was originally created to save a few minutes of administrative work.
For example, an agency may eventually depend on automation for:
- Lead qualification.
- Client onboarding.
- Invoice notifications.
- Campaign reporting.
- Content approval.
- Customer support routing.
- Internal task assignment.
If the platform disappears, these processes can become difficult to reconstruct.
Five precautions for future automation decisions
1. Maintain independent workflow documentation
Keep a record of triggers, conditions, actions and integrations outside the automation platform.
2. Export important information periodically
Do not wait until a company announces a shutdown. Understand what information can be exported and how frequently it should be backed up.
3. Avoid unnecessary credential dependency
Keep credentials under appropriate business ownership and use secure credential-management practices.
4. Document manual fallback processes
For important workflows, employees should know how to complete the process if automation becomes unavailable.
5. Evaluate the platform’s exit strategy
Before committing to a new automation platform, ask:
- Can workflows be exported?
- What format is used?
- Can run history be downloaded?
- Can tables or stored data be exported?
- How are credentials handled?
- What happens when the subscription ends?
- Is there a documented shutdown or migration process?
These questions should be part of software selection, not an afterthought.
8. Relay.app Shutdown: Frequently Asked Questions
Is Relay.app still working?
No. Relay.app shut down in September 2026. Its official website confirms that accounts, workflows and run history have been permanently deleted.
Can I still log in to Relay.app?
No. The service has shut down. Users should not expect to access their former workspace or generate new exports.
Can I recover my Relay.app workflows after September 14?
Relay’s official shutdown notice states that accounts, workflows and run history have been permanently deleted. If you did not save an export before shutdown, investigate local backups, screenshots, emails and records in connected applications. Do not assume Relay can restore the original workspace.
Can Relay.app workflows be imported directly into Zapier?
There is no general direct import that recreates Relay workflows automatically. If you saved a workflow description or export, use it as a reference and rebuild the logic using the destination platform’s own triggers, actions and conditions.
What happened to Relay.app’s founder?
Relay founder Jacob Bank joined Google’s Chrome organisation as VP of Product, according to reporting by TechCrunch in August 2026. This was a hiring move, not a purchase of Relay.app.
What is the best replacement for Relay.app?
Zapier is worth evaluating for broad application integration, Make for complex visual workflows and n8n for technical flexibility and self-hosting options. The best choice depends on the workflows you previously ran.
Is Make better than Zapier for replacing Relay.app?
Neither is universally better. Make offers detailed visual routing and data transformation, while Zapier is particularly attractive for its broad integration ecosystem. Test the actual workflows before committing to either.
Is n8n a good Relay.app alternative?
n8n is worth evaluating if your team has technical expertise and wants greater control over workflow execution. Its self-hosted option introduces infrastructure and maintenance responsibilities that non-technical teams should consider.
Can I still use my old Relay.app API credentials?
Do not assume that old credentials or tokens remain valid or accessible. Create fresh connections and credentials in the replacement platform, using the relevant application’s authorisation process.
Final Verdict: Relay.app Is Gone. Your Workflow Strategy Should Not Be.
Relay.app offered a useful combination of visual automation, AI actions and human-in-the-loop processes. Its shutdown means businesses must now decide how to reconstruct the workflows they depended on.
For users who saved their exports, the priority is rebuilding important processes with the help of those records.
For users who missed the deadline, the starting point is different: reconstruct the business logic from existing records, documentation and employee knowledge.
Zapier, Make and n8n are all worth evaluating, but none should be treated as an automatic replacement.
The best choice depends on the integrations you need, the complexity of your workflows, the importance of human approval and the technical resources available to maintain the system.
Our recommendation: Rebuild critical workflows first, test every integration and maintain independent documentation. Most importantly, make sure the next automation platform does not become a single point of failure for your business.
