Heartbeat StrawberryThe Heartbeat direct messages nobody wants to work through
A companion works the 3 operations your Heartbeat account exposes. It can send a direct message and create an event, and every one of those waits on an approval card showing the direct message before it changes.
Open the direct message. Check it against something else. Write the change. Move to the next one. That is the Heartbeat afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a direct message until you approve it.
What it can do is exactly what Heartbeat exposes to an account you authorise and nothing beyond it: 3 operations, no reads and 3 writes. In practice that means it can send a direct message, create an event and add a to group, and work across the direct messages, events and groups.
The Heartbeat API stops at Heartbeat. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Heartbeat direct messages does a companion see?
In the tab.
Heartbeat exposes no read operation to a connected account, so a companion opens Heartbeat in the session you are already signed into and reads the screens you would.
The direct messages are what most of this inventory is about, alongside the events. A companion can hold all 3 of these operations and forty open tabs in the same pass, which is how an afternoon of Heartbeat admin becomes a queue you review.
Can it change a direct message without asking?
All 3 write operations wait for you.
A companion can send a direct message, create an event and add a to group, and each one is staged on an approval card first: you see the direct message, the field and the new value before it lands in Heartbeat.
Nothing in Heartbeat is sent, changed or deleted on your behalf without that click, and a rejected card leaves the direct message exactly as it was. The gate is the same one on every surface, described at security.
- Send Direct Message
- Create Event
- Add To Group
Can the direct messages pass run every Monday?
Yes.
Saved as a routine, the Heartbeat direct messages pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the messages, the Heartbeat direct messages sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents