I need help setting up a Zapier workflow that can pull Google Calendar events from a specific time period. I want to get all appointments between a start date and end date, but I’m having trouble finding the right approach.
I looked through Zapier’s built-in Google Calendar triggers and actions, but nothing seems to let me grab multiple events at once for a date range. So I decided to try making a custom webhook action that calls Google’s Calendar API directly.
I set up a GET request to: https://www.googleapis.com/calendar/v3/calendars/{{myCalendarId}}/events
I’m passing timeMin and timeMax as query parameters to filter the results. But when I test it, I keep getting this error:
Error: Request returned 500. Error during execution: Invalid URL.
I double-checked that my calendar ID is right and that I’m formatting the date parameters correctly (using ISO 8601 format). The URL looks correct when I compare it to Google’s API docs.
Does anyone know if there’s a standard Zapier action I missed that can retrieve multiple calendar events? Or if you’ve done something similar with custom actions, what might be wrong with my setup?
The Google Calendar API needs proper pagination to handle multiple events - that’s probably why you’re getting timeouts. Zapier’s webhook times out at 30 seconds, but Google’s API can take way longer for big date ranges. Add these parameters: orderBy=startTime, singleEvents=true, and maxResults=250. This keeps events in chronological order and limits response size. Your ISO 8601 formatting looks right, but make sure you’re URL encoding the plus signs in timezone offsets. Another thing that got me - double-check your calendar ID format in Zapier. Sometimes the email address works, sometimes you need the actual calendar identifier from Google Calendar settings. That 500 error screams server-side processing failure, not authentication. It’s probably a parameter issue or the response is just too big.
You’re fighting Zapier’s limitations instead of using the right tool for the job.
I’ve been here before trying to batch pull calendar events. Zapier wasn’t built for bulk operations - you can’t grab multiple events in one go. You end up with hacky workarounds that constantly break.
You need a proper automation platform that handles API calls natively. I switched to Latenode for calendar integrations and it’s completely different.
Latenode lets you make that same Google Calendar API call but with proper error handling and auth management built in. No more wrestling with OAuth headers or random 500 errors. You can process the returned event array however you want - filter it, transform it, send it anywhere.
I built a similar workflow that pulls weekly calendar events for reporting. Takes 5 minutes in Latenode versus hours of Zapier debugging.
The platform handles all the API complexity so you can focus on what you actually want to do with the data.
zapier’s webhook probably times out before google responds. add singleEvents=true and try a 7-day date range first. also check if your calendar’s private - those need different auth scopes that zapier often misses.
Check your query parameter encoding - that’s usually where bulk calendar pulls break. Had this exact issue building a scheduling sync last month. It wasn’t auth, it was Zapier’s URL encoding for date ranges. Manually encode your timeMin and timeMax before hitting the webhook. Also double-check your calendar ID format - sometimes it needs ‘primary’ instead of the actual email. Adding maxResults helped me too since Google’s API times out on big date ranges without it. Test with a smaller range first to see if your setup works, then go bigger. If you’re still stuck, use Zapier’s Schedule trigger for daily jobs that grab just that day’s events and store them. Not as clean but way more reliable than fighting bulk operations.
That 500 error is probably an authentication issue, not the URL. Google Calendar API webhooks through Zapier are a pain because you need proper OAuth2 headers, and they’re tricky to get right. I hit this exact same wall last year building something similar. What saved me was ditching the custom approach and using Zapier’s ‘Google Calendar Find Event’ action in a loop instead. Not pretty, but way more reliable. If you’re dead set on the custom API route, double-check your Bearer token is in the request headers and your Google Calendar API credentials have the right scopes. Authentication is usually where these break, not URL formatting.