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 charts, and delivery logs are all included on the free plan, so you can prove the whole workflow before it ever costs anything.

Webhook Relay

Every event, live where your team already works.

Point any webhook at Viably and the moment something happens, a payment, a signup, a failed deploy, it lands in Slack as a clean card, retried until it arrives, logged, charted, and ready to become someone's task.

Add to Slack See pricing

hq.viably.app/relay

POST

relay

💰New payment

$59.90 from Ava Chen

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 renders each as its own Block Kit card, so nobody has to hand-build a message. Pick a source, or watch it cycle.

#payments — Slack

your app posts

{"type": "transaction","amount": 5990,"currency": "USD","email": "[email protected]",}

💰New payment

$59.90 from Ava Chen

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.

One endpoint, every event type·each rendered as its own Block Kit card

Events into work

An event that needs a person becomes a task

Surfacing the event is only half the job. Turn on follow-up and the same delivery drops a task under the message, assigned to someone or left for whoever is free to claim.

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

ViaApp9:04 AM

💰New payment · $59.90

Ava Chen upgraded to Pro, monthly.

ViaApp9:04 AM

📋Follow up with Ava

Spawned from this event. Nobody owns it yet.

🙋 Claim🆓 up for grabs

Delivery you can trust

A blip never costs you an event

Slack hiccups, your server bursts during a launch, a request drops. The relay treats delivery as the serious part of the job, so the channel stays a source of truth people believe.

Delivering payment.succeeded

1Attempt 1

2Attempt 2

3Attempt 3

4Attempt 4

Up to 10 attempts, exponential backoff·a blip never costs you an event

And when a stream runs hot, batch it into one clean digest instead of a flood:

📊124 payments today

$7,410 total · one message, not 124

Reporting, built in

The pattern shows itself, without a second tool

Because the charts are built from the same events you already relay, there is nothing extra to instrument. Watch volume by category over the month, switch to a running total, and look back across earlier months on the paid plan.

Month in Review — command center

TransactionsSignupsLeads

Cumulative

1,284Events this month

SignupsBusiest category

4 monthsKept on record

See every delivery

Diagnosis is a glance, not a guess

Each endpoint keeps its own log with delivered, failed, and dropped counts, and a failed delivery heals itself on retry. When a batch is waiting, one click flushes it.

Logs — My App Events

128 total✓ 124 delivered✗ 2 failed2 dropped

just nowtransactionPayment · $59.90delivered

1msignupsNew signup · [email protected]delivered

4mdevopsDeploy · [email protected]retrying

9mleadgenNew lead · Pricing pagedelivered

12mtransactionPayment · $120.00delivered

Every delivery, kept and searchable.Flush queue

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. Everything here is on the free plan.

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

Sam2:10 PM

/webhook-relay

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.

Go deeper