Appointments calendar integrations overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains how native Pixie CRM appointments connect to Google Calendar, Google Meet, Outlook and downloadable ICS files without becoming the same record.
What you’ll accomplish
Understand how native Pixie CRM appointments connect to Google Calendar, Google Meet, Outlook and downloadable ICS files without becoming the same record. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The appointment remains the authoritative Pixie CRM record; remote calendar events store their own identifiers and API state.
Google OAuth is connected per staff user, Outlook uses configured application credentials, and ICS is generated from appointment data without a persistent remote connection.
Create, update and delete actions are conditional on permission, connection state, appointment data and settings.
Follow these steps
- Select the calendar integration required by the organisation.
- Configure credentials and connect the relevant staff account.
- Create a test appointment and add or synchronise its calendar event.
- Update the appointment and verify the remote event.
- Cancel or delete the test and confirm the chosen remote handling.
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
- Do not treat remote calendar success as the appointment database save result.
- Use least-privilege credentials and revoke departed staff connections.
- Check timezone in both systems.
- 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.