PromptsOpenClaw
Newsletter and pipeline, cached locally
Use case
Subscriber counts and deal stages are useless if the council has to call two APIs every time it thinks. OpenClaw pulls Beehiiv and HubSpot into SQLite on a schedule, and the business council reads the cache with everything else.
What to connect
A Beehiiv API key and a HubSpot private app token. A local SQLite file. The business-council skill, so it can read the cache.
Setup
- Store both tokens in the environment, not in the repo.
- Create [GROWTH DB PATH] with tables for newsletter stats and deals.
- Schedule the sync daily, before the business council runs.
- Run it once and confirm a subscriber count and at least one deal stage match what you see in the products.
- If either token is missing, the sync should skip that source and say so, not fail the whole job.
Edit before you send: The database path, which Beehiiv publication, and which HubSpot pipeline.
Prompt to paste into OpenClaw
Save this as a skill named newsletter-crm. Once a day at [21:00] [TIMEZONE], refresh [GROWTH DB PATH]. Beehiiv, for publication [PUBLICATION ID]: - Subscriber count, growth, and churn. - Per-post open rate and click rate for posts in the last [30] days. - Segment sizes I have marked as worth keeping. HubSpot, for pipeline [PIPELINE ID]: - Deals: stage, value, and whether the deal is active. - Contacts tied to those deals. - A one-line pipeline status: counts by stage. Cache the numbers locally so business-council can query SQLite instead of calling the APIs. If a call fails, keep the previous snapshot, mark it stale, and name the failure. Do not invent a count. Do not email subscribers or edit deals from this skill. It is a read into the cache.
More OpenClaw prompts
- Personal CRM from mail and calendar
A year of email and meetings is a pile of names you cannot search. OpenClaw reads Gmail and Google Calendar, drops newsletters and cold pitches, and keeps a local profile for each person worth remembering. You ask in plain language who you know at a company, or who has gone quiet.
- Meeting action items with an approval queue
Meetings end and the promises disappear. OpenClaw waits until a meeting is over, pulls the Fathom transcript, matches the room to your CRM, and sends you each action item to approve. Approved items become Todoist tasks. Things other people owe you stay on a waiting-on list, except people on your own team.
- Urgent email, only when it can wait no longer
You do not live in the inbox, including on weekends. OpenClaw checks mail on a timer, ignores senders you have already marked as noise, and pings a Telegram topic only when something needs you now. When you say an alert was wrong, the next check is stricter.
- Knowledge base you fill from a Telegram topic
Links you meant to remember are scattered across chats. You drop a URL into one Telegram topic. OpenClaw saves the article, the video transcript, the full post thread, or the PDF, then you ask later in plain language. A new save can point at something you already kept.