whentomeet

What This Skill Does

The WhenToMeet skill enables OpenClaw AI to interface directly with the WhenToMeet scheduling platform via its tRPC v1 API. This tool acts as an automated coordinator, allowing users to create, view, and manage collaborative scheduling events without leaving the agent's environment. Whether you are planning a recurring team sync or a one-off brainstorming session, the skill provides a robust wrapper around the platform's core scheduling features. By utilizing the provided CLI script (scripts/w2m_events.py), the skill abstracts complex API authentication and request construction, ensuring that payloads are valid, formatted correctly, and conform to the expected ISO-8601 time standards.

Installation

To install this skill, use the standard OpenClaw hub command: clawhub install openclaw/skills/skills/felixwortmann/whentomeet

Ensure that you have set the WHENTOMEET_API_KEY environment variable in your OpenClaw configuration. The skill relies on this credential for all requests. Verify the path to your script environment, as the skill executes commands from the root directory to locate the utility scripts successfully.

Use Cases

This skill is ideal for teams and professionals who frequently manage availability across distributed groups. Key use cases include:

• Automating the creation of poll-based meetings from natural language requests.
• Rapidly auditing existing event statuses (PLANNING vs. FINALIZED).
• Managing large volumes of scheduling polls efficiently.
• Providing instant feedback on event details like public URLs for participant sharing.

Example Prompts

1. "Create a new planning event called 'Project Q2 Kickoff' for next Monday with three one-hour slots starting at 9 AM, 11 AM, and 2 PM."
2. "List all my active events and tell me which ones are still in the PLANNING stage."
3. "I need to cancel the meeting with ID 550e8400-e29b-41d4-a716-446655440000; please delete it for me."

Tips & Limitations

• Pre-Validation: Always double-check your slot times before confirmation. The system enforces strict endTime > startTime logic.
• Authentication: Keep your API key secure. If you lose access, your ability to manage events will be restricted.
• Manual Requests: While HTTP fallback examples exist, prioritize the included Python script for better error handling and payload serialization.
• Safety: The deletion command requires an explicit confirmation flag to prevent accidental data loss. Treat your UUIDs carefully when interacting with the API.