ViablyViably
Webhook Relay

Every event, live where your team already works.

Point any webhook at Viably and the moment something happens — a payment, signup, lead, or deploy — it lands in Slack as a clean card, with retries, logging, and follow-up built in.

Add to SlackSee pricing
hq.viably.app/relay
POST
relay
💰New payment

$59.90 from Pam Beesly

Plan
Pro, monthly
Where
🇺🇸 United States
One relay, every event

The same endpoint, formatted for what it is

Payments, signups, leads, and deploys all post to a single URL. Viably reads the type and builds the right Slack card, so the alert feels native instead of hand-built.

#payments — Slack
your app posts
{
"type":"transaction",
"amount":5990,
"currency":"USD",
"email":"[email protected]"
}
💰New payment

$59.90 from Pam Beesly

Plan
Pro, monthly
Where
🇺🇸 United States

A charge clears and finance sees it in seconds, with the amount, plan, and customer already laid out. Stripe events arrive signed and de-duplicated.

A coherent customer journeybuilt from webhooks and integrations
Events into work

An event that needs a person becomes a task

Once the alert lands, it can also create the follow-up. Leave it unassigned and it goes up for grabs; assign someone and it becomes managed work instead of a signal that disappears.

01

From notification to next action

A payment posts, and right beneath it Via files the follow-up. Leave it unassigned and it goes up for grabs, so the work finds an owner in one tap rather than in a thread of who has this.

#payments — Slack
Today
Viably square
ViaApp9:04 AM
💰New payment · $59.90

Pam Beesly upgraded to Pro, monthly.

Viably square
ViaApp9:04 AM
📋Follow up with Pam

Spawned from this event. Nobody owns it yet.

🙋 Claim🆓 up for grabs
Delivery you can trust

A blip never costs you an event

Every endpoint keeps its own log of delivered, failed and dropped events. A failed delivery retries until it lands, and a stream that runs hot can post as one digest instead of a flood.

Webhooks arrive one after another and each becomes a row in the endpoint's log. A deploy event fails twice, waits 1 then 2 seconds, and is delivered on its third attempt. Three Stripe payments queue and post together as one digest.
POST hq.viably.app/relay
{
"type":"transaction",
"title":"Annual plan · 12 seats",
"amount":432000,
"currency":"usd",
"email":"[email protected]"
}
  1. transactionPayment · $4,320.00queued
  2. devopsDeploy · [email protected]retry in 2s
  3. transactionPayment · $59.90queued
  4. signupsNew signup · [email protected]delivered

1,190 events · 1,187 delivered · 2 queued

Reporting, built in

The pattern shows itself, without a second tool

The reports are built from the same events you already relay, so there is no extra instrumentation to maintain. See each day's events and revenue, slice the volume by category, and look back across earlier months on Viably+.

ViablyViably
The Viably team calendar, showing the events captured and the revenue that landed on each day of the month

Every day of the month counts its events by category and adds up the revenue that landed with them.

Setup

It starts with a slash command

No servers to stand up, no dashboards to wire. Run one command in Slack, copy the URL and token, and your app starts posting.

02

One command, and you're relaying

Type /webhook-relay in any channel and Via hands back a live endpoint with its token. Post a small JSON body to it and the formatting, retries, and logging are already handled.

#ops — Slack
Today
OM
Oscar2:10 PM

/webhook-relay

Viably square
ViaApp2:10 PM
📡Relay endpoint ready

Post events here and I'll format and deliver them to this channel.

Endpoint
hq.viably.app/relay
Auth
Bearer •••••
Retries, batching, reporting, and logs come with it, on the free plan.
01Create an endpointRun /webhook-relay in Slack, or open the command center, and pick a destination channel. You get a relay URL and a bearer token.
02Point any source at itDrop the URL into any tool's webhook settings. Stripe, GitHub Actions, Sentry, your monitoring, or your own app all work the same way.
03Watch events arriveViably formats and delivers each event as a Block Kit card, retries on failure, and keeps a full log you can audit anytime.
04Assign the follow-upOptional. Turn on Spawn a task and each event becomes an owned, claimable task, assigned to a teammate or left up for grabs.

Sending payments? The Stripe to Slack guide covers signed events, de-duplication, and periodic revenue reports end to end.

From the blog

Read how we use it

How Supertype recovers lost sales with Slack webhooks

A failed Stripe payment is your warmest lead, a customer who chose the plan and tried to pay in the last few minutes. Here is how Supertype recovers those lost sales by sending charge.failed webhooks straight into Slack, with the product, amount, decline reason, and customer contact ready to act on.

A webhook for Slack to ground work on real signals

Sending a webhook to Slack is the easy part. The harder question is which events deserve a channel, who owns the follow-up, and how you keep the noise low enough that people keep reading. Here is how to turn event-to-Slack delivery into a habit the whole team trusts.

Webhook to Slack: building an event-driven workforce

A signup, a payment, or a failed deploy is worth far more when your team sees it the moment it happens. This is a complete guide to sending any webhook to Slack, with reliable delivery, automatic follow-up tasks, reporting, and logs, all set up from a single slash command.

Go deeper

Where it fits

It happened.Your team already knows.

Every event, surfaced where the work already is.

FAQ

Questions, answered

How do I send a webhook to Slack with Viably?
Run /webhook-relay in Slack to create an endpoint, then POST a small JSON body with a title, some text, and optional fields to the URL it gives you, using the bearer token. Viably formats a Block Kit message and delivers it to the channels you chose. Services that cannot set an Authorization header can pass the token as a query parameter instead.
What kinds of events can it handle?
Payments, signups, leads, contact forms, deploys and CI results, and anything else you can POST. Viably reads the event type and renders each as its own card, and Stripe events can arrive signed and de-duplicated so retries never double count.
What happens if Slack or my server has a hiccup?
Each endpoint retries on failure with exponential backoff, up to ten attempts, so a brief outage never loses an event. You can also batch a busy stream into one periodic digest rather than a flood of messages.
Can an event create a task automatically?
Yes. Turn on follow-up for an endpoint and each qualifying event spawns a task under its Slack message, assigned to someone or left up for grabs for whoever claims it first.
Is it available on the free plan?
Yes. The relay, retries, batching, reporting, and delivery logs are all included on the free plan, so you can prove the whole workflow before it ever costs anything.
Read the full guidePayment Webhook to Slack
Ready when you are

Assemble your operating system inside Slack.

Add Viably free. Turn on the powers your team needs, when you need them.

Add to SlackSee pricing
SignalRecordOwned work
  • Free to start
  • No credit card required
  • Powers on when you need them