WhenToMeet LogoWhenToMeet
Sign In

Seven small automations you can wire up with the WhenToMeet API today

The shortest pitch for any API is: here's what you can build in an afternoon.

These are seven real automations on top of the WhenToMeet REST API and MCP server. Every one of them is the kind of thing people normally handle manually, forget to handle, or copy-paste from another tool. None of them are demos — they all map to endpoints that exist today.

Authentication throughout: a Bearer sk_… key for REST, the same key configured in your MCP client for the natural-language ones. Full reference at docs.whentomeet.io.

1. "Find 30 minutes with anyone" — MCP one-liner

With MCP wired into Claude or ChatGPT:

"Find three 30-minute gaps in my calendar next week, business hours, at least an hour away from my other meetings."

The assistant calls list_calendar_events for next week, filters, and answers. No script, no cron, no config.

2. Conflict-check a deep-work block

A common use of check_conflicts: before you commit to a 4-hour Friday focus block, you ask:

"Does 9am–1pm next Friday conflict with anything? If it does, tell me what."

The MCP tool returns the overlapping events. You pick a different time or move one of them. This is the smallest possible automation — one tool call — and it is the one you'll run the most.

3. A cron job that auto-creates office hours

A short script that runs Sunday night:

POST /api/v1/direct-events  
Authorization: Bearer sk_…

{  
  "groupId": "…",  
  "title": "Office hours",  
  "startTime": "2026-05-05T14:00:00Z",  
  "endTime": "2026-05-05T15:00:00Z"  
}

You get predictable office hours on your calendar every week without remembering to create them. Pair it with a public direct-event link and people book in.

4. A weekly digest of next week's meetings

Every Friday afternoon, a script calls GET /api/v1/calendar/events?from=…&to=…, formats the result into Markdown, and emails it to you (or pushes it into your notes app):

  • Monday 10am — Investor check-in
  • Tuesday 2pm — 1:1 with Anna
  • Wednesday — blocked for writing
  • Thursday 3pm — design review

This is a five-minute script that replaces a twenty-minute weekly ritual. It's also how you start noticing patterns — "why do I have four 1:1s on Tuesdays" — that you'd never spot clicking through a week view.

5. Agent-generated standup agenda from calendar events

Every morning, the same Claude session that reads your Linear issues can also:

"Pull my calendar events from yesterday using list_polls and list_calendar_events. Draft a standup update based on what I was actually in."

The agent writes a first draft. You edit. This is what "agent-addressable" means in practice — your assistant can already read your docs and your code; adding your calendar is the last piece.

6. Broadcast a launch schedule from a JSON file

You have a JSON file with ten launch events in it. You want them published to a broadcast group at whentomeet.com/b/launch-2026.

A short script reads the file and loops through it:

for event in events:  
    POST /api/v1/direct-events  (groupId: …)

The broadcast group's iCal feed picks them up automatically. Subscribers see the full launch schedule on their calendar the next time their app syncs. If you change the JSON file and re-run, the edits propagate.

The marketing team maintains the file. The calendar maintains itself.

7. Booking-page metrics pulled into a dashboard

If you run booking pages, you want numbers — how many bookings per week, which page converts, what's the no-show rate.

GET /api/v1/bookings gives you the raw data. Dump it into a spreadsheet, a Notion table, or your internal dashboard. Now you can tell which booking page is actually earning its keep, and you don't have to click through our UI to find out.

What these have in common

Every one of these replaces a recurring manual task with a scheduled or on-demand automation. None of them required us to ship anything new — the surfaces are there, documented, rate-limited for fairness, and stable.

If you build one of these and share it, we'll link to it. If you build one of these and it fails because the API is missing a tool, tell us; that's the signal that tells us what to add next.

Setup, keys, and the full endpoint reference are at docs.whentomeet.io.