calendar-bridge

What This Skill Does

The calendar-bridge skill acts as a robust middleware between OpenClaw and your Google Calendar ecosystem. Unlike standard direct API integrations that struggle with OAuth expiration, this skill interfaces with a locally hosted Node.js service (gcal-oauth-bridge) that manages token lifecycle, refresh logic, and persistence. It effectively abstracts the complexity of Google's OAuth 2.0 flow, allowing your AI agent to reliably query, list, and monitor your schedules without manual re-authentication every week.

Installation

1. Install the base service: Clone the repository from https://github.com/DanielKillenberger/gcal-oauth-bridge and run npm install.
2. Configure Credentials: Navigate to the Google Cloud Console, create an OAuth 2.0 Client ID for a 'Desktop app', and add http://localhost:3000/auth/callback as your redirect URI.
3. Environment Setup: Populate the .env file with your GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET.
4. Initialize Authorization: Start the service with node app.js, call the /auth/url endpoint, and complete the consent flow in your browser.
5. Integrate with OpenClaw: Use the clawhub install command provided in the documentation to register the bridge as a skill within your agent's environment.

Use Cases

• Personal Productivity: Allow your AI to summarize your upcoming week, provide reminders for meetings, or block off focus time.
• Automation: Use the agent to automatically list calendars and pull event descriptions to provide context for meeting preparation.
• Troubleshooting: Monitor the auth state of your connections to ensure the agent never loses access to essential scheduling data.

Example Prompts

• "List my calendar events for the next 7 days and summarize my top priorities."
• "Are there any conflicting meetings scheduled on my secondary work calendar for tomorrow?"
• "Can you check my calendar and tell me when I am free for a lunch meeting next week?"

Tips & Limitations

• Security: Ensure that the CALENDAR_BRIDGE_API_KEY is configured if you are exposing this service on a network accessible beyond localhost.
• Maintenance: While the service handles auto-refresh, keep an eye on the /health endpoint occasionally. If the authenticated flag returns false, re-run the /auth/url process.
• Platform: Since this relies on a Node.js service running on your local machine or VPS, ensure that the service is running (e.g., via systemd) before querying the skill, otherwise, the agent will report a connection error.