ViablyViably
Logs and business observability

Ship webhooks you can see, search, and replay.

Viably provides a managed webhook infrastructure with a rich feature set: reliable ingestion, delivery monitoring, safe retries, webhook replays, multiple webhook batching strategies, and deep analytics you can query. Run it on its own, or wire it into the Slack-native CRM to turn a system of records into a system of actions.

Start freeSee the ledger

Free plan forever with no credit card, and unlimited seats on every plan.

Robust webhook relay with rich tooling and first-class Slack support.

ViablyViably
The Viably webhook relay, showing endpoint health, event volume over ninety days, and the searchable delivery log

Webhook delivery and analytics infrastructure for event ingestion and monitoring.

Ingestion

Post JSON to Viably from anywhere.

Create a webhook endpoint on Viably and you get a URL and a bearer token. Anything that can send a http request is a source. GitHub, Stripe and Viably OCR need no mapping as they are natively supported. Viably's webhook infrastructure automatically retries failed deliveries in exponential backoff.

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

The ledger

Event-driven automations, fully auditable.

Viably's webhook infrastructure comes with best-in-class logging and reporting. Filter by category or status, open a row to investigate the exact payload, replay a failed delivery through its backoff, and drive CRM automations from it.

viably.app/logs
1,284 kept this month5Sent1Failed1Dropped
transaction09:41Pam Beesly
Pro monthly renewed$59.90
What arrived
{
"type":"charge.succeeded",
"amount":5990,
"currency":"usd",
"receipt_email":"[email protected]"
}
What became of itPosted to #payments in 240ms, signed and de-duplicated.
Kept for 30 days on Viably Free workspaces.Export CSV

A consolidated ledger from your contact forms, payment events, GitHub, support emails, and any other integrations.

12 min
To wire the whole event path
50+
Webhook endpoints
500
Events a month on the Free plan
One source of truth

Google Analytics says what happens inside your app. Viably says what is happening across the business.

The reports are drawn from the events you already relay, so there is no second tool to wire up and no tagging plan to keep current. Read each day's events and revenue off the calendar, slice ninety days of volume by category or endpoint, 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.

  • One endpoint, bearer authenticated

    Create an endpoint, get a URL and a token, and post JSON to it. Services without custom headers can pass the token as a query parameter.

  • Retries with exponential backoff

    A failed delivery is retried on a widening schedule, and every attempt is logged on the event so you can see when it finally went through.

  • Manual replay, including what already failed

    When a delivery runs out of retries because something downstream was down, replay it from the log and watch the row change state.

  • Every payload searchable

    Filter by endpoint, category or status, open a row to read the exact body that arrived, and export the range you filtered to as CSV.

  • Batching for the streams that run hot

    On a launch day, a hundred and twenty messages become one digest in Slack, and every individual event is still in the log.

  • Out-of-the-box analytics

    Each day's events and revenue on a calendar, grouped by category or endpoint and computed from the same event log.

Every event can open a contact, post to Slack and spawn a task. The first 500 a month are free.

Most webhook tooling stops once the delivery succeeds. On Viably the event that lands in the ledger opens a contact in the CRM and routes to the Slack channel that cares. It can also spawn a task with an owner and a due date, then follow-up on its completion. Billing is per workspace, so the whole engineering team can watch the same log at no extra cost. The Free plan includes the full feature sets of replay, batching and reporting.

14 days
Viably+ trial.
Seats on every plan
$7
per day, billed annually
90 days
Of delivery history
viably.app/tasks
1,284events on
the record
Mon 09:12Signal
Michael Scott asks about twelve seatsA forwarded enquiry lands, matches a contact Viably already had, and is written to the ledger as inbound.
Automation that closes the loopobservability-first philosophy
FAQ

Questions about the relay

What is Viably's webhook relay?
It is managed webhook infrastructure. You create an endpoint, point anything that can send a http request at it, and Viably authenticates the request, types the event, stores it with its full payload, delivers it wherever you asked, retries on failure, and keeps the whole thing searchable afterwards. There is no server for you to run and no queue for you to operate.
Can I use it without Slack?
Yes. Slack routing is an output you may never turn on. The endpoint accepts events, the log is readable in the dashboard, the exports are CSV, and the reporting is drawn from the same rows. Teams who do live in Slack get channel routing and Via on top of all that.
How do I replay a failed webhook?
Open the delivery log, filter to failed, and open the row. The attempt history is attached to the event, including how the backoff ran, and replay is a button on the record. Replaying moves the counts, so the log tells you whether the second attempt landed.
What happens when a delivery fails?
It is retried with exponential backoff. Every attempt is recorded against the event rather than being summarised away, so you can tell the difference between a request that never arrived, one that arrived and was refused, and one that succeeded on the third try. An event nothing was subscribed to is marked dropped rather than failed, because those are different facts.
How long are events kept?
The log is queryable in the dashboard and the reporting looks back across earlier months on Viably+. The Free plan carries two thousand events a month with the full feature set, which is enough for most small teams to run their whole event surface on.
Which sources work out of the box?
GitHub, Stripe and Viably OCR arrive typed with no mapping work, and anything else that can send JSON over HTTP is a first-class source: a contact form, your own application, a payment provider, a partner's system, a cron job.
Can events do something other than land in a log?
That is the point of pairing it with the rest of Viably. The same event that lands in the ledger can open a contact in the CRM, route to a Slack channel, and spawn a task with an owner and a due date, which is what turns a system of records into a system of actions.
How much does it cost?
The Free plan is always available and carries the full feature set including replay, batching and reporting. Viably+ is seven dollars a day billed annually, with unlimited seats, and it opens with a 14-day free trial that bills nothing until the fortnight is up.
Read the full guideSlack Webhook Relay
Ready when you are

Send your first event in the next five minutes.

Start free, create an endpoint, and post a payload to it. The row appears with the body you sent still attached.

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