Bring every stream together
Jobs, agents, services and workflows all report to one place, no matter where they run.
One place for every automated event
Everything your automations say, in one calm feed
Bring events from scripts, services, agents and workflows into a single ordered feed. Keep every source and detail useful—and keep machine output out of chat.
Registration is currently closed. Existing accounts can sign in.
HTTP request
POST /api/v1/notifications
Authorization: Bearer $NOTIFICATIONS_API_KEY
Content-Type: application/json
{
"title": "Backup completed",
"body": "Nightly PostgreSQL backup finished and was verified.",
"severity": "success",
"tags": [
"backup",
"production"
],
"source": "backup-worker",
"deduplicationKey": "backup:2026-07-31",
"metadata": {
"duration": "42s",
"size": "1.8 GB"
},
"actions": [
{
"id": "open-backup",
"type": "link",
"label": "Open backup",
"href": "https://example.com/backups/2026-07-31",
"style": "primary"
}
]
}201{"id":"c7c25c99-bb6d-4fcc-a95a-923d668dd012","created":true}
Backup worker
Backup completed
Nightly PostgreSQL backup finished and was verified.
backupproduction
One place to look
Keep machine output together—and out of your chats.
Slack, Telegram and email are where people talk. Bring the steady stream from your automations into one calm feed you can review when it suits you.
Review on your time
Read, filter and archive when you choose instead of depending on an interruption at the right moment.
Keep a useful history
Every event stays attached to its source, severity, tags, metadata and next action.
A feed that fills itself
Three steps from any process to one shared feed.
The first event takes one small request. Richer context remains optional until it earns its place.
1. Name the source
Give the producer a clear name and create its revocable API key. The secret is shown once.
2. Send one request
POST JSON from a script, service, agent or any workflow that can speak HTTP.
3. Follow the feed
Read, filter, archive or open the context attached to each event from the same inbox.
One destination, many sources
Every automated process reports to the same place.
Use the same small HTTP contract across code and visual workflows without building or babysitting another messaging stack.
Scheduled jobs and backups
Record completions, missed runs, verification failures and recovery links.
Builds and publications
See successful releases, rollbacks and broken pipelines in one reviewable history.
Agents and automations
Give long-running work a deterministic place to report outcomes and request attention.
No-code workflows
Use any HTTP request step that can send JSON with a bearer token.
Simple, then structured
Start with the event. Add structure only when it helps.
A simple update stays simple. Add filters, safe retries and richer context without turning the feed into a workflow engine.
Sources and tags
Keep producers distinct, then group events across them with normalized tags.
Exact metadata
Attach string key/value context and filter it later without putting everything in the title.
Safe retries
A deduplication key returns the original event while it exists instead of creating another copy.
Explicit actions
Attach deliberate HTTPS or email links that open the next place you need to work.
A deliberately narrow product
For your automated work, not your customers.
This is your feed for events you need to review. It is not a campaign builder, an embedded customer inbox, an on-call escalation system or an omnichannel router.
Choose this inbox when
Scripts, services, agents and workflows need to report structured events to one person in one place.
Choose customer messaging when
Your product needs templates, recipients, preferences and delivery across customer channels.
Private by default
Security by construction.
The product keeps account boundaries and credential handling in the data path, not in marketing promises.
Account-scoped access
Reads and writes are bound to the authenticated account, with database row-level isolation in PostgreSQL.
Revocable source credentials
API key secrets are shown once; only a cryptographic digest is stored for later authentication.
Encrypted sensitive fields
Sensitive business fields are encrypted before PostgreSQL persistence, with root key material kept outside the database and its backups.
Straight answers
Before the first event joins your feed.
The boundary is intentionally clear so you can decide quickly whether this is the right destination.
What can add an event to the feed?
Anything that can make an authenticated HTTP request: a script, backend service, scheduled job, agent or visual workflow with an HTTP step.
Does this replace Slack, Telegram or email?
No. It gives machine events a dedicated feed so chat and email can stay focused on human conversation.
Can I use it from a no-code workflow?
Yes. Use an HTTP request step, send JSON and place the source API key in the bearer authorization header.
What happens when a sender retries?
Send a stable deduplication key. While the original event exists, a retry returns that event instead of creating a duplicate.
Can notifications still reach my device?
Browser push is optional. New subscriptions show a short content preview; each device can switch to a private generic alert or mute individual sources.
Is this an inbox for my product's customers?
No. It is a personal feed for the automated events you receive. Customer messaging platforms solve a broader and different job.
How long is history kept?
Events remain available as reviewable history. Exact commercial retention limits will be published before external registration opens.
One place for everything your automations have to say.
Bring every stream into one calm, structured feed—and keep your conversations for people.
Open your inbox