Relay

Name: Relay
Brand: Relay

AI Native

Relay is a cloud-based workflow automation platform that organizes multi-step flows around AI agents and human-in-the-loop steps, integrates with over 100 third-party applications, and supports webhooks, HTTP endpoints, and AI actions with optional approval or manual input pauses.

Est 2021|Raised $8.1M|6 Ref Customers

LinkedIn 10K|Web traffic 82K|FTEs 358|HQ New York, NY

MarketsWorkflow Automation

Published Oct 15, 2026

01Common complaints

- You need the broadest possible integration ecosystem: Zapier or Make may better serve stacks requiring many niche connectors. - You require self-hosting or strict data residency controls: self-hosted n8n or other on-prem solutions are more appropriate. - You expect very high automation volume and need strict cost predictability: per-step or credit-based metering may be less predictable than other pricing models. - You require custom connectors but cannot procure an Enterprise plan from the vendor. - You require mature SDLC features (version control, export/import, workspace-level duplication) that reviewers report are limited or absent today.

Deal disqualifiers (poor fit)

Requirement for self-hosting or strict data residency that cannot be met by the vendor.
Heavy reliance on niche apps not supported by the vendor and an unwillingness to manage API/webhook workarounds.
Need for documented enterprise IAM/governance features (for example, SCIM, detailed audit capabilities) that are not publicly documented.

Frequently mentioned product gaps

Workflow duplication and export/import across workspaces/accounts are commonly requested features absent in current public documentation.
Integration breadth is smaller than some incumbents, which can be a blocker for stacks relying on specialized enterprise software.
No self-hosting option is publicly documented for the vendor’s product offering.

Roadmap / not-yet-available

The vendor publishes product update posts indicating ongoing iteration, but no consolidated forward-looking roadmap with firm dates was identified in this research pass.

Scale / performance limits

The commercial model includes monthly step limits that can pause automations when exceeded.
Some anecdotal commentary suggests editor performance may decline with very large workflows; these reports are not vendor-confirmed.

Security/compliance gaps (public documentation)

SOC 2 Type II is disclosed; many other enterprise security details are not clearly public.

02Why they buy

Differentiators supported by customer feedback

Users commonly report a short time to proficiency and that the interface reduces friction for building and testing workflows.
The platform includes first-class human-in-the-loop automation constructs (approvals and manual steps), which some buyers find useful for quality control.
The platform provides integrated AI steps that simplify adding extraction, summarization, and classification into flows.

Claims requiring independent validation

Statements asserting the product has the market’s best user interface or provides quantified productivity gains should be validated through independent benchmarking where possible.

Where competitors have advantages

Zapier and Make have substantially larger integration catalogs and longer platform histories.
n8n and Pipedream provide stronger developer extensibility and, in the case of n8n, a self-hosting option.

Why customers chose Relay (themes)

Faster time-to-value due to a user interface focused on clarity, testing/debugging tools, and templates.
Inclusion of human-in-the-loop steps for approvals and quality control.
Integrated AI steps that remove the need to build separate LLM infrastructure for some workflows.

03Field reports

Review-platform sentiment (G2)

- The product is very highly rated on G2. Review volume varies across snapshots. - G2 summaries of pros and cons consistently highlight ease of use, automation capabilities, and responsiveness of support among positives; common negatives include limited integrations, missing platform features, and concerns about pricing and usage limits. Representative reviewer statements (paraphrased for neutral tone): - Several reviewers described the platform as straightforward to use and reported that it reduced time spent on routine tasks. - Some reviewers reported that the platform contributed to faster onboarding of automation processes and cited a relatively short learning curve compared with some alternatives. - Other reviewers reported concerns about pricing relative to self-hosted or open-source options and noted gaps in native integrations and certain platform features (for example, duplicating workflows between workspaces).

Review-platform sentiment (Capterra)

Capterra contains a limited review volume; due to that limited sample, conclusions should be cautious.

Representative reviewer statements (paraphrased):

One reviewer described the platform as easy to learn and use.
The same reviewer and others noted the absence of workflow duplication or export/import features as a limitation.

Community / social (Reddit)

- Community discussions show exploratory adoption as well as reports of friction in specific edge cases. Representative community observations (paraphrased): - A user reported spending significant time attempting to restrict access to specific documents and encountering challenges when connecting a second document, indicating potential pain points around OAuth scopes and connection management. - Some community posters recommended the product in comparative discussions about user experience, while others noted potential bias or affiliation in recommendations.

Why some customers might leave (themes)

Requirement for specific app connectors not available in the product’s integration catalog.
Requirement for self-hosting or strict data residency controls.
Need for more mature developer-focused platform capabilities, such as version control and export/import features.

Vendor-published case study metric: a support automation customer

The vendor’s case study reports a significant improvement in response times following a Relay integration, and an increase in an app rating metric within a short timeframe.

Critical evaluation:

These are vendor-published results. Methodology details (for example, baseline volume, how response time was measured, and whether other changes occurred concurrently) are not disclosed, which limits the independent verifiability of the claims.

Press-reported early customers / design partners

Press coverage and vendor communications list early customers and design partners, including a mix of recognizable technology companies.

Critical evaluation:

Use of customer logos indicates some level of adoption, but public materials do not provide detailed information about deployment scope, outcomes, or retention.

04Best fit

Company size

The vendor is best suited to small to mid-market organizations and teams; practical customer fit extends to small businesses and mid-market teams, including individual automation consultants.

Industries / verticals

Common use cases are found in SaaS, operations-heavy knowledge work, customer support operations, marketing operations, and sales operations.

Roles and personas

Decision makers: RevOps leaders, operations/automation leads, heads of support, and heads of marketing operations.
End users: operators who build workflows, automation consultants, and analysts.

Pain points Relay addresses

Repetitive cross-tool tasks and manual handoffs.
Need for approval checkpoints and human QA within automations.
Desire to incorporate AI steps into workflows without maintaining separate LLM infrastructure.

Qualification criteria (good fit)

Your stack includes the vendor’s supported apps (examples: Google Workspace, Slack, Notion, HubSpot, Linear).
You require built-in human checkpoints (approvals, manual input) in automation flows.
You prefer cloud-hosted deployment and want to minimize engineering overhead for automation projects.

05The pitch

What the product does (objective value proposition)

Relay is a cloud-based workflow automation platform organized around AI agents and human-in-the-loop automation. It enables teams to construct multi-step workflows that integrate with a broad set of third-party applications, call webhooks/HTTP endpoints, execute AI steps (for tasks such as extraction, summarization, classification), and optionally pause for approvals, manual data input, or task completion before continuing.

Target market and positioning

- Primary target: modern, SaaS-heavy teams, including non-technical operators and automation consultants supporting non-technical stakeholders, that seek to implement automation with limited engineering effort. - Positioning: the vendor presents the product as having a streamlined user interface relative to some legacy automation tools, workflows designed for team collaboration, integrated AI capabilities, and explicit human checkpoints. - Typical customer size: SMB to mid-market teams that require collaboration and operational controls and prefer a cloud-hosted solution.

Get a comprehensive analysis of Relay including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

You need the broadest possible integration ecosystem: Zapier or Make may better serve stacks requiring many niche connectors.
You require self-hosting or strict data residency controls: self-hosted n8n or other on-prem solutions are more appropriate.
You expect very high automation volume and need strict cost predictability: per-step or credit-based metering may be less predictable than other pricing models.
You require custom connectors but cannot procure an Enterprise plan from the vendor.
You require mature SDLC features (version control, export/import, workspace-level duplication) that reviewers report are limited or absent today.

Deal disqualifiers (poor fit)

Requirement for self-hosting or strict data residency that cannot be met by the vendor.
Heavy reliance on niche apps not supported by the vendor and an unwillingness to manage API/webhook workarounds.
Need for documented enterprise IAM/governance features (for example, SCIM, detailed audit capabilities) that are not publicly documented.

Frequently mentioned product gaps

Workflow duplication and export/import across workspaces/accounts are commonly requested features absent in current public documentation.
Integration breadth is smaller than some incumbents, which can be a blocker for stacks relying on specialized enterprise software.
No self-hosting option is publicly documented for the vendor’s product offering.

Roadmap / not-yet-available

The vendor publishes product update posts indicating ongoing iteration, but no consolidated forward-looking roadmap with firm dates was identified in this research pass.

Scale / performance limits

The commercial model includes monthly step limits that can pause automations when exceeded.
Some anecdotal commentary suggests editor performance may decline with very large workflows; these reports are not vendor-confirmed.

Security/compliance gaps (public documentation)

SOC 2 Type II is disclosed; many other enterprise security details are not clearly public.

02Why they buy

Differentiators supported by customer feedback

Users commonly report a short time to proficiency and that the interface reduces friction for building and testing workflows.
The platform includes first-class human-in-the-loop automation constructs (approvals and manual steps), which some buyers find useful for quality control.
The platform provides integrated AI steps that simplify adding extraction, summarization, and classification into flows.

Claims requiring independent validation

Statements asserting the product has the market’s best user interface or provides quantified productivity gains should be validated through independent benchmarking where possible.

Where competitors have advantages

Zapier and Make have substantially larger integration catalogs and longer platform histories.
n8n and Pipedream provide stronger developer extensibility and, in the case of n8n, a self-hosting option.

Why customers chose Relay (themes)

Faster time-to-value due to a user interface focused on clarity, testing/debugging tools, and templates.
Inclusion of human-in-the-loop steps for approvals and quality control.
Integrated AI steps that remove the need to build separate LLM infrastructure for some workflows.

03Field reports

Review-platform sentiment (G2)

The product is very highly rated on G2. Review volume varies across snapshots.
G2 summaries of pros and cons consistently highlight ease of use, automation capabilities, and responsiveness of support among positives; common negatives include limited integrations, missing platform features, and concerns about pricing and usage limits.

Representative reviewer statements (paraphrased for neutral tone):

Several reviewers described the platform as straightforward to use and reported that it reduced time spent on routine tasks.
Some reviewers reported that the platform contributed to faster onboarding of automation processes and cited a relatively short learning curve compared with some alternatives.
Other reviewers reported concerns about pricing relative to self-hosted or open-source options and noted gaps in native integrations and certain platform features (for example, duplicating workflows between workspaces).

Review-platform sentiment (Capterra)

Capterra contains a limited review volume; due to that limited sample, conclusions should be cautious.

Representative reviewer statements (paraphrased):

One reviewer described the platform as easy to learn and use.
The same reviewer and others noted the absence of workflow duplication or export/import features as a limitation.

Community / social (Reddit)

Community discussions show exploratory adoption as well as reports of friction in specific edge cases.

Representative community observations (paraphrased):

A user reported spending significant time attempting to restrict access to specific documents and encountering challenges when connecting a second document, indicating potential pain points around OAuth scopes and connection management.
Some community posters recommended the product in comparative discussions about user experience, while others noted potential bias or affiliation in recommendations.

Why some customers might leave (themes)

Requirement for specific app connectors not available in the product’s integration catalog.
Requirement for self-hosting or strict data residency controls.
Need for more mature developer-focused platform capabilities, such as version control and export/import features.

Vendor-published case study metric: a support automation customer

The vendor’s case study reports a significant improvement in response times following a Relay integration, and an increase in an app rating metric within a short timeframe.

Critical evaluation:

These are vendor-published results. Methodology details (for example, baseline volume, how response time was measured, and whether other changes occurred concurrently) are not disclosed, which limits the independent verifiability of the claims.

Press-reported early customers / design partners

Press coverage and vendor communications list early customers and design partners, including a mix of recognizable technology companies.

Critical evaluation:

Use of customer logos indicates some level of adoption, but public materials do not provide detailed information about deployment scope, outcomes, or retention.

04Best fit

Company size

The vendor is best suited to small to mid-market organizations and teams; practical customer fit extends to small businesses and mid-market teams, including individual automation consultants.

Industries / verticals

Common use cases are found in SaaS, operations-heavy knowledge work, customer support operations, marketing operations, and sales operations.

Roles and personas

Decision makers: RevOps leaders, operations/automation leads, heads of support, and heads of marketing operations.
End users: operators who build workflows, automation consultants, and analysts.

Pain points Relay addresses

Repetitive cross-tool tasks and manual handoffs.
Need for approval checkpoints and human QA within automations.
Desire to incorporate AI steps into workflows without maintaining separate LLM infrastructure.

Qualification criteria (good fit)

Your stack includes the vendor’s supported apps (examples: Google Workspace, Slack, Notion, HubSpot, Linear).
You require built-in human checkpoints (approvals, manual input) in automation flows.
You prefer cloud-hosted deployment and want to minimize engineering overhead for automation projects.

05The pitch

What the product does (objective value proposition)

Target market and positioning

Primary target: modern, SaaS-heavy teams, including non-technical operators and automation consultants supporting non-technical stakeholders, that seek to implement automation with limited engineering effort.
Positioning: the vendor presents the product as having a streamlined user interface relative to some legacy automation tools, workflows designed for team collaboration, integrated AI capabilities, and explicit human checkpoints.
Typical customer size: SMB to mid-market teams that require collaboration and operational controls and prefer a cloud-hosted solution.

Get a comprehensive analysis of Relay including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →