Agentic Hat
Agent
Showcase
Pricing
Buddy
Docs
Sign In
Sign Up
Agentic Hat
Autonomous AI Agent Platform · A FewBox product
Navigation
Agent
Showcase
Pricing
Buddy
Docs
Sign Up
Follow
Contact Us
[email protected]
Agentic Hat
Autonomous AI Agent Platform · A FewBox product
Navigation
Agent
Showcase
Pricing
Buddy
Docs
Sign Up
Follow
Contact Us
[email protected]
Privacy Policy
Extension Privacy
© 2026 FewBox
Docs › Heartbeat notifications

Heartbeat notifications

When a Heartbeat finds something, it goes straight to the group chat already open on your phone — Feishu, WeCom, DingTalk, Slack or Discord. You do not have to open Agentic Hat, and there is nothing to install.

What it is for

The point of a Heartbeat is that you do not have to watch. But if what it finds only sits in a conversation, you still have to remember to come back. Notifications remove that last step: something new, one more message in your group, and the link takes you to the conversation. Runs that find nothing are never sent — a group that pings every hour is on mute within two days.

AAgentic Hatbot
【Forum watch: virtual staging】 1
2 new posts worth a look: someone asking what virtual staging should cost, and one complaining an AI tool removed their fireplace. 2
https://agenti.chat/agent?conversation=… 3
— Agentic Hat 4
1
The title is the Heartbeat's name, so you can tell at a glance which one is speaking.
2
The body is what it said in its conversation this run. Long reports are cut short; the full text is in the conversation.
3
The link opens that Heartbeat's conversation, so you can carry on from your phone.
4
The signature is on every message. When a group bot asks for a custom keyword, this is the one to use.

Connecting it

At the right of the “My Heartbeats” row in the sidebar, press the bell icon to open notification settings. Notifications belong to your whole account: set them up once and every Heartbeat can use them; each Heartbeat then decides separately whether it notifies.

Notification settings
Where to send it when a Heartbeat finds something.
open.feishu.cn/…a1b2c32Test3
https://… (a group bot's webhook URL)1Add
Which Heartbeats notify you
Forum watch: virtual stagingOn4
Competitor pricing pageMuted
1
Paste a group bot's webhook URL and press Add. Feishu, WeCom, DingTalk, Slack and Discord all work — you do not have to say which one it is.
2
Once saved, only the host and the last few characters are shown. The URL is as good as a password: anyone holding it can post to your group.
3
Press Test once and check the message really arrived before you leave.
4
Each Heartbeat is set to On or Muted separately. A muted Heartbeat still runs; it just does not post.

Where to get a webhook URL

Every platform calls it a group bot and every one of them hands you a URL. All of them need a group first — a group of just you is fine:

  • Feishu / Lark: group → ⋯ → Settings → Group Bot → Add Bot → Custom Bot. ⚠️ Only the desktop client can add one — mobile can only add app bots and the web client has no such entry; this has nothing to do with your plan and needs no admin approval. If it asks for a security setting, choose the keyword option and enter Agentic Hat — every notification we send carries that line
  • WeCom: group → ⋯ → Group Bot → Add
  • DingTalk: group settings → Bot → Add → Custom. Use Agentic Hat as the keyword here too
  • Slack / Discord: in Slack, create an app and enable Incoming Webhooks; in Discord it is fastest — channel settings → Integrations → Webhooks → New

The keyword: where people get stuck

Feishu and DingTalk group bots usually ask you to pick a security setting. Choose “custom keyword” and enter Agentic Hat. Every notification is signed with it, so it always passes. With any other keyword the receiver silently rejects the message — no error, and nothing in the group. When that happens now, the reason is written on that row in notification settings.

Delivered counts as seen

A Heartbeat protects itself: if it reports several times and nobody responds, it stops rather than keep spending credits. A notification that reached your group counts as you having seen it — you do not have to come back and open the conversation just to keep it running. It only stops when, several times in a row, nothing was delivered and you never opened its conversation.

Muting is not pausing

Muted means it keeps running but does not post to the group — findings are still written to the conversation. Paused means the Heartbeat does not run and spends nothing. Want quiet for a few days without missing anything? Mute. Do not want to spend credits on it? Pause.

When nothing arrives

  • Press Test first. If the receiver rejects the message, the reason is written on that row — most often a keyword that does not match
  • A destination that fails several times in a row is switched off and flagged; add it again to restore it
  • If the URL is dead (the bot was removed from the group, say), that destination is removed outright
  • If you have muted the group in your chat app, messages still arrive but your phone stays silent — we cannot see that from our side

Keep the URL like a password

Anyone holding the webhook URL can post to your group. So once it is saved, only the host and the last few characters are shown; the full URL is never displayed again to anyone and never written to logs. Only https URLs are accepted, and URLs pointing at internal networks are refused. If you think it has leaked, delete the bot in the group and create a new one.

Current limits

  • Only group-bot webhooks for now. Email and browser push are not available yet
  • One message per finding; several are not combined into a digest
  • Feishu custom bots can only be added from the desktop app; once added, messages arrive on your phone as usual

Heartbeats → · Phone remote →