All features

Alerts people
actually read.

An alert channel everyone has muted is worse than no alert channel. Because the flow decides what is worth sending, what arrives is worth reading.

Available on Every plan

Email

Every new and reopened report

SMS

Critical issues only

Jira

Open an issue in BILLING

Webhook

POST to your incident tool

01

The flow decides, not a threshold

A declined card emails the customer. A failing function pages the on-call. Both are the same flow with two branches, so nobody gets woken for a billing retry.

New report on Billing flow

declined card

Email the customer

server error

SMS on-call

anything new

Jira issue

02

Into the tools you already have open

Email and SMS on every plan, Jira issues and outgoing webhooks for everything else. Anything with an HTTP endpoint is a valid destination.

From Atflow <no-reply@atflow.xyz>

New report: payment-intent-failed

A new report was created in the Billing flow.

card_declined · AWS Lambda: process_sub
Open report

Privacy Policy · Terms of Service

03

Escalate once, not per occurrence

Because reports are grouped, three hundred failures produce one page rather than three hundred. The channel stays usable during the incident it exists for.

Occurrences in the last hour

318

Alerts sent to on-call1

Advanced details

SMS for the critical ones

Text messages alongside email, on every plan.

Webhook integrations

Any HTTP endpoint, on every plan.

Jira issues

A new report can open a Jira issue in the project you choose.

Desktop notifications

System tray alerts through the desktop app.

Book an Enterprise demo

Frequently asked questions.

Email and SMS, Jira issues, and outgoing webhooks to any HTTP endpoint. AI agents can also read and build flows through the API and the MCP server from Starter.

Get your free account. One flow included.

Nothing to install, no card required. Draw your first flow and point your app at it.

Get started free