Configure the Google Calendar date range in the appointment table
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Limit how much remote Google event data is loaded around the current date for useful context and responsive performance.
What you’ll accomplish
Limit how much remote Google event data is loaded around the current date for useful context and responsive performance. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The module stores past and future range settings for remote event retrieval.
When event display is enabled, the table requests only events within that configured window.
The range affects remote display, not native Pixie CRM appointment retention.
Follow these steps
- Go to Google Calendar settings.
- Set a practical past period.
- Set the required future period.
- Save and reload the appointment table.
- Verify remote events outside the window are intentionally absent.
Settings to check
Check it worked
After this workflow completes, Pixie CRM keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Pixie CRM database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Common mistakes to avoid
- Avoid very large ranges that slow API loading.
- Do not interpret an absent old Google event as a deleted Pixie CRM appointment.
- Reconnect Google if no events appear within a known valid range.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.