Connect the tools where your work already happens.

Relay gathers context and completes approved work across the systems your team already uses. Every connector stays scoped, revocable, and honest about its current readiness.

Start with one workflow See Relay handle a follow-up ↓

Keep your CRMStart with one jobApprove what matters

What the labels mean OAuth ready Provider app setup required Sandbox-first foundation Contract ready, not yet a live connection

Google Workspace

OAuth ready

Relay can read: Gmail, Calendar, Drive, and Contacts.
Relay can do: Send approval-bound email and update calendar events.
Example: Meeting follow-up, inbox routing, and calendar preparation.

Microsoft 365

App setup required

Relay can read: Outlook, Calendar, Teams, OneDrive, and Contacts.
Relay can do: Prepare Outlook messages and calendar changes when the app is configured.
Example: Inbox follow-through, meeting preparation, and team context.

Slack

App setup required

Relay can read: Channels, messages, and meeting signals.
Relay can do: Prepare approved messages and route notifications when connected.
Example: Approvals, operating updates, and customer risk routing.

Zoom

App setup required

Relay can read: Meetings, recordings, and webhook events.
Relay can do: Receive meeting events and attach provider artifacts.
Example: Meeting capture and sourced customer follow-through.

HubSpot

OAuth ready

Relay can read: Companies, contacts, deals, activities, documents, and quotes.
Relay can do: Update CRM records and prepare, publish, or export quotes behind approval.
Example: Meeting-to-CRM updates and quote follow-up.

Salesforce

Contract ready

Relay can read: Accounts, contacts, opportunities, activities, and quotes.
Relay can do: Prepare record and activity changes through the shared CRM contract.
Example: Provider-ready CRM context and customer workflows.

Stripe

Sandbox first

Relay can read: Customers, subscriptions, invoices, payments, credits, and refunds.
Relay can do: Use sandbox-first billing actions behind approval.
Example: Billing risk, renewal readiness, and payment context.

↗

Your product

Contract ready

Relay can read: Usage, adoption, health, and entitlement events you provide.
Relay can do: Receive signed product events and return attributable results.
Example: Health reviews, risk routing, and renewal preparation.

Connect only what the job needs

Access stays scoped. Writes can wait.

Relay keeps authorization server-side, separates each organization, and lets approval policy govern messages, record changes, quotes, and other consequential actions.

Choose the first workflow and its required systems.

Authorize the smallest useful connection.

Review read, write, and approval boundaries before testing.

Start small

Which connected job should Relay handle first?

Connect only the tools that job needs. Set the approval boundary. See the result before expanding.

Start with one workflow Talk to a human