Alerts in another tab
CI, monitoring and payment alerts each have their own inbox, away from the people who act on them.
Pulse · Bots & Webhooks
Incoming webhooks, bots and a chat API.
Integrations bring the signal from your other tools into the channel where people can act on it. Flaxxa Pulse has incoming webhooks that post any payload as a bot, bot tokens for posting from your own code, signed outgoing webhooks for Pulse events, and a REST API, with tokens stored only as a hash.
No credit card
Free plan
Cancel anytime
pulse.flaxxa.com / integrations
Bots & webhooks
no codePOST /hooks/pulse/•••• → # deploys
CI
Deploy Bot BOT
✅ build #1482 passed · deploying
message.sent → external URL HMAC signed
token stored as sha-256
••••a1b2- Alerts to a channel
- Incoming
- HMAC-signed events
- Outgoing
- chat:write scope
- Bot tokens
- Tokens never stored raw
- Hashed
01 / 04
Why do alerts get missed?
Integrations need code
Getting a tool to post into chat often means a server and a secret to look after.
Secrets handled loosely
Plain-text tokens and URLs that reveal whether they exist are a quiet risk.
02 / 04
How do Flaxxa Pulse integrations work?
Create a bot
A named identity that posts into channels but never appears in the member list or mentions.
Bring alerts in
Create an incoming webhook for the bot and a channel, and POST to its URL; the payload arrives as a message.
Send events out
Subscribe a URL to the Pulse events you care about; deliveries are signed and retried.
Or post from your code
Issue the bot a chat:write token and post through the bot API, or use a workspace API key with the REST API.
03 / 04
What can you connect with Pulse?
Incoming webhooks
Any POSTed payload becomes a channel message; JSON is shown as a formatted block.
Token safety
Only a hash is stored, the token is shown once, and unknown tokens get a plain 404.
Rate limits
120 requests a minute per sender, and blocked while a workspace is suspended.
Outgoing webhooks
Pulse events to your URL, HMAC-SHA256 signed, retried, with a delivery log.
Bot tokens
Scoped to chat:write, revocable at any time.
REST API
Post to a channel by its name, manage channels, messages, DMs and to-dos.
04 / 04
What changes when tools talk to the channel?
Signal meets people
Alerts land where someone can act on them.
No server needed
A URL or a token is the whole integration.
Secure by default
Hashed tokens, signatures and rate limits.
Keep exploring
More Pulse capabilities
Workflows
No-code workflows in Flaxxa Pulse: when a Pulse event happens and your conditions match, post a message into a channel as a bot, with a log of every run.
Channels & Messaging
Team messaging with public and private channels, one-level threads, reactions, drafts, read state and forwarding, all updated live over WebSockets.
File Sharing
Share images, PDFs, text, audio and video up to 25 MB in Flaxxa Pulse messages, with storage set by your plan and PDFs sent to Flaxxa Sign in one click.
FAQ
Bots & Webhooks: common questions
Create an incoming webhook for a bot and a channel, then POST to its URL from the other tool. Any JSON or text body is posted into the channel as the bot, with no API key needed.
Get started in minutes
Try Flaxxa Pulse free.
Spin up a workspace and put Bots & Webhooks through its paces.
Free plan · No credit card · Cancel anytime