Operational event routing

Route webhook and email events to the people and tools that need them

Receive webhook and email events, validate them, and deliver each one to Slack, Microsoft Teams, PagerDuty, Google Sheets, email, and HTTP.

We will only use this address for launch updates.

The delivery controls production webhooks need

PayloadRelay gives teams the guardrails and visibility they need when webhook delivery becomes part of production operations.

Recover from transient failures
Configure retry behavior and failover strategies, so temporary outages do not turn into silent drops.
Verify webhook authenticity
Validate supported inbound webhook signatures and optionally sign outbound webhook deliveries so receivers can verify integrity and shared-secret authenticity.
Route without glue code
Turn validated events into notifications, records, incidents, or webhook calls without maintaining forwarding scripts or servers.
See what happened
Follow each delivery from intake to target with request outcomes and operational metadata.
Keep operations auditable
Gain operational visibility with a 30-day activity trail. Customer payload bodies stay out of PayloadRelay databases and logs to preserve privacy.
Control noisy endpoints
Use endpoint-level filters and maintenance windows to keep event flow intentional during production changes.

How delivery works in PayloadRelay

Create a webhook endpoint for HTTP traffic, forms, and API requests, or an email ingestion endpoint for inbound email. PayloadRelay can validate, transform, and fan payloads out to each configured target based on your endpoint settings.

Sources

Webhooks
HTTP Forms
API Requests
Inbound email
PayloadRelay

Event routing

Targets

Webhook
Email
Slack
Discord
Sheets
Teams
PagerDuty
Telegram

Connect webhook events to the tools your team already uses

Use integrations for day-to-day destinations, and webhooks for custom receivers.

  • Webhooks

    Send or forward events to public HTTP/HTTPS receivers with optional signing.

  • Email

    Turn event data into formatted emails or inbound email into webhooks.

  • Slack

    Route alerts and structured messages into Slack channels.

  • Discord

    Send rich notifications to your community servers.

  • Google Sheets

    Append inbound data as new rows in your tables automatically for ad-hoc analysis.

  • Microsoft Teams

    Send operational updates into team channels.

  • PagerDuty

    Conditionally trigger incidents based on specific email or webhook payloads.

  • Telegram

    Deliver concise bot messages to chats.

Simple pricing for webhook and email events

Preview the launch plans and join the list for pricing and access updates.

Sandbox
For prototypes, personal automations, and low-volume operational checks.
$0/month

USD, plus applicable tax

  • 250 accepted events/month
  • 1 active endpoint
  • Up to 2 enabled outputs per endpoint
  • 1 standard delivery retry
  • Single-user workspace
  • 256 KB max payload
  • 30-day metadata activity trail
Join the launch list
Solo
For small relays, launch projects, and early production checks.
$9/month

USD, plus applicable tax

  • 1,000 accepted events/month
  • 1 active endpoint
  • Up to 3 enabled outputs per endpoint
  • Up to 3 standard delivery retries
  • Single-user workspace
  • 256 KB max payload
  • 30-day metadata activity trail
Join the launch list
Recommended
Team
For operational teams that need collaboration and advanced reliability controls.
$49/month

USD, plus applicable tax

  • 10,000 accepted events/month
  • 5 active endpoints
  • Up to 5 enabled outputs per endpoint
  • Team workspace, up to 5 members
  • Up to 5 retries with advanced policies
  • 512 KB max payload
  • 30-day metadata activity trail
Join the launch list
Scale
For teams with higher traffic and larger relay footprints.
$199/month

USD, plus applicable tax

  • 100,000 accepted events/month
  • 50 active endpoints
  • Up to 10 enabled outputs per endpoint
  • Team workspace, unlimited members
  • Up to 5 retries with advanced policies
  • 1 MB max payload
  • 30-day metadata activity trail
Join the launch list

Customer relay request and message bodies are never persisted in PayloadRelay databases, activity logs, object storage, or backups. They exist only transiently in memory for delivery or retry while being processed. Operational metadata, including SMTP envelope sender addresses, may be temporarily retained in the 30-day Activity trail.

Need higher limits or custom contracts? Join the launch list for pricing and access updates →

Frequently asked questions

Still curious? Check the documentation.

Join the PayloadRelay launch list

Leave your email and we will send an update when access is ready.

We will only use this address for launch updates.