Library / Calendar & Scheduling
Calendar & Scheduling
Check appointment availability via authenticated webhook and Google Calendar
Receives a proposed start and end time through an authenticated webhook, checks Google Calendar and returns an available or busy result for booking forms and assistants.
What it does
## Check appointment availability in Google Calendar Check a proposed appointment interval through an authenticated webhook. This workflow validates the requested times, reads Google Calendar availability, and returns a structured available or busy result. It suits booking forms, voice assistants, chat assistants, and internal scheduling tools that already have a proposed start and end time. ### Setup 1. Import the workflow and leave it inactive while configuring it. 2. In Receive Request, create a Header Auth credential with your chosen header name and secret value. Set a unique webhook path. Keep the secret in credentials and in your calling application, never in the workflow JSON. 3. In Check Calendar, connect your Google Calendar OAuth credential and replace YOUR_CALENDAR_ID with a calendar that credential can access. Start with a dedicated test calendar. 4. Send Content-Type: application/json and the configured authentication header. The request body needs start and end, such as {"start":"2030-01-15T14:00:00-06:00","end":"2030-01-15T14:30:00-06:00"}. Replace these example dates with a future interval you intend to test. 5. Test one free interval and one busy interval. Test invalid times and a provider permission failure. Verify that a provider failure never returns an available result. 6. Activate only after these checks, then use the production webhook URL shown by n8n. HTTP 200 returns status available or busy, a boolean available, and the normalized UTC start and end. HTTP 400 returns invalid_request and validation errors. HTTP 502 returns unavailable without claiming that the interval is free. This is a snapshot for one interval. It neither generates a slot catalogue nor holds or creates an appointment. Calendar state can change after the check. Successful, error, and manual execution saving are disabled in the export; review your instance logging and retention before using real requests. Prepared by Benian Technologies: https://benian.ai/integrations/n8n-automation
The steps
- Receive Request
- Validate Request
- Request Is Valid
- Check Calendar
- Format Availability
- Return Availability
- Return Invalid
- Return Provider Error
Similar automations
Calendar & SchedulingBook Voice Appointments with Vapi, Gemini and Calendar10 stepsCalendar & SchedulingAutomate Client Appointment Reminders with Twilio and Calendar10 stepsCode, Git & Developer ToolsCheck Bulk Domain Availability with NameSilo16 stepsCalendar & SchedulingQualify Appointment Requests with an n8n Form and OpenAI19 steps