Bring your tools into the conversation
One HTTP request posts into the chat. The same key reads what you typed back, so alerts, updates, and approvals live in the chat instead of another inbox.
- One HTTP request
- Push notifications
- Two-way replies
- Cursor-paged reads
- Revoke in one tap
One request. That is the whole integration.
A bot posts to its owner with its key. The same key lets it read the owner's chats and answer what the owner typed.
POST /api/bot/messages
ApiKey: wb_••••••••••••
Content-Type: application/json
{
"type": "TEXT",
"text": "Nightly backup finished. 2.8 MB, encrypted."
}Anything that can make an HTTP request can talk to your deployment
Connect your systems
Create a bot in the app and copy its key. Your automation platform, CRM, or monitoring stack posts to the chat with a single HTTP call. No login flow, no token refresh.
Rich posts, delivered live
Text, images, files, links with previews, audio, and video land in the bot's own feed with a push notification, while the app is open or not.
Two-way conversations
Type to a bot the way you would to a colleague. Your automation reads it and replies in the thread: daily summaries, approvals, alerts you can answer.
No server of your own
Anything that can make an HTTP request can post, and anything that can poll can read. A cron job, an automation platform, or a script on a laptop is enough to start.
Post
Text, media, files, and links, into the bot's feed with a notification.
Read
The owner's chats and replies, paged with a cursor since the last id, so nothing is missed.
Revoke
Delete the bot. Its key stops working immediately, and any request that carries it is refused.
From nothing to a first post
- 1
Create a bot
Give it a name in the app. It gets its own feed in your chat list, like any other contact.
- 2
Copy its key once
The key is shown once, at creation, so store it in the system that will use it. The bot posts to you with that key from then on.
- 3
Post
One HTTP request with the key and a message. It lands in the feed with a push notification.
What teams build with bots
Alerts from monitoring
Your monitoring stack posts an incident the moment it fires, with a link and a screenshot, and you see it where you already are.
CRM updates
A deal moves stage, a ticket closes, a customer replies. The record change lands in the bot's feed as it happens.
Approvals you answer in the thread
The bot asks, you type yes or no, and your automation reads the answer and carries on. No form, no separate app.
Daily summaries
A morning digest of the numbers your team watches, posted on schedule by the system that owns them.
Connect the systems your team already runs.
Ask us about bot limits, the read and post endpoints, and the integrations other organizations have built.