calendar

Automate Google Calendar event CRUD via a Railway backend API.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Cimminelli1982/crm-frontend --skill calendar-cimminelli1982
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: calendar
Source: https://github.com/Cimminelli1982/crm-frontend/tree/main/docs/openclaw-skills/calendar
Command: npx skills add https://github.com/Cimminelli1982/crm-frontend --skill calendar-cimminelli1982

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize and manage Google Calendar events (create, update, delete, search) across multiple calendars from a single workflow, removing manual back-and-forth and data silos.

Core Features & Use Cases

  • Create, update, delete, and search events via a centralized backend API to keep calendars in sync.
  • Support multi-calendar setups (Living with Intention and Agenda Management) with timezone handling and attendee management.
  • Integrate with Supabase for quick reads and a Railway backend for reliable CRUD operations on calendar data.

Quick Start

Install the integration, configure your calendars, and start performing create, read, update, and delete operations via the backend.

Frequently Asked Questions about calendar

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Google Calendar event management across multiple calendars?

You can automate Google Calendar event management across multiple calendars by using a centralized backend API to perform create, read, update, and delete operations. This integration synchronizes events to remove manual data entry and silos.

Can I synchronize Google Calendar events using Supabase and a Railway backend?

Yes, you can synchronize Google Calendar events using Supabase for quick database reads and a Railway backend to execute reliable CRUD operations. This setup ensures your calendar data stays consistently synced across workflows.

Does Google Calendar event synchronization support timezone handling and attendee management?

Google Calendar event synchronization supports timezone handling and attendee management. The backend API processes event details including start and end times, descriptions, locations, and attendees across multi-calendar setups.

What's the best way to manage CRUD operations for Google Calendar events without manual back-and-forth?

The best way to manage CRUD operations for Google Calendar events is through a centralized backend API with explicit endpoints and request formats. It provides safe fallbacks while handling event creation, updates, deletion, and searching.

Are there limitations when using a backend API for multi-calendar event management?

Multi-calendar event management via a backend API requires explicit endpoints and specific request formats to function correctly. You must rely on safe fallbacks for operations, meaning the API depends on proper backend configuration rather than direct calendar interactions.