PromptsOpenClaw
Meeting action items with an approval queue
Use case
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.
What to connect
Fathom, Google Calendar read-only, the personal-crm skill, Todoist, and a Telegram topic for approvals.
Setup
- Add the Fathom API key and confirm OpenClaw can list recent meetings.
- Point this skill at the personal-crm database so attendees match existing contacts.
- Connect Todoist and set the project where approved tasks should land.
- Set INTERNAL_DOMAINS so coworkers are left off the waiting-on list.
- Set BUSINESS_HOURS and TIMEZONE. The poll runs every 5 minutes inside those hours, and completion checks run at 8:00, 12:00, and 16:00.
- Save it as meeting-actions. After the first rejection, confirm a note landed in meeting-actions-notes.md so the next extraction is tighter.
Edit before you send: Business hours, timezone, internal domains, the Telegram topic, and the Todoist project.
Prompt to paste into OpenClaw
Save this as a skill named meeting-actions. Poll Fathom every 5 minutes during [9:00–18:00] [TIMEZONE] on weekdays. Use the calendar so you know when an external meeting has ended. Wait [15] minutes after the end time, then look for the transcript. Skip meetings where every guest is on [INTERNAL DOMAINS]. When a transcript is ready: 1. Match attendees to personal-crm contacts. If someone is missing, add a short profile note and say you did. 2. Update each external contact's relationship summary with what this meeting was about. 3. Extract action items with an owner: mine, or theirs. Quote the line that made you think it was an action item. 4. Send them to the [MEETING ACTIONS] Telegram topic as an approval queue. I reply approve or reject on each item. 5. Create a Todoist task only for items I approve, in [TODOIST PROJECT]. 6. Track their items as waiting-on. Leave [INTERNAL DOMAINS] off that list. 7. If I reject an item, append one line to meeting-actions-notes.md: what you extracted, and why I said it was wrong. Read that file before the next extraction. Three times a day, at 8:00, 12:00, and 16:00 [TIMEZONE], send a short completion check: overdue, still pending, and waiting-on. If I said I would send an email and that email is now in Gmail, mark my item done. Archive items older than 14 days and say how many you archived. Read-only on Fathom, Gmail, and Calendar. Do not email anyone from this skill.
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.
- 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.
- Nightly business council
The numbers live in ten different tools, so the pattern stays invisible. Once a night, eight specialists each read only the slice that matches their job, in parallel, and a synthesizer turns that into a short numbered list. You reply with a number when you want the longer version, and you approve or reject so the next night fits you better.