Download an appointment ICS calendar file
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Export appointment timing and details as a portable calendar file for Apple Calendar, Outlook, Google Calendar and other compatible applications.
What you’ll accomplish
Export appointment timing and details as a portable calendar file for Apple Calendar, Outlook, Google Calendar and other compatible applications. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The ICS endpoint builds a calendar event from the appointment subject, description, location, start/end and timezone.
The file is generated on demand and does not require OAuth or create a persistent two-way connection.
Importing it into an external calendar creates a separate copy that does not automatically follow later Pixie CRM changes.
Follow these steps
- Go to the permitted appointment detail page.
- Select Download calendar or ICS.
- Go to the file in the chosen calendar application.
- Check timezone and event details.
- Replace or update the imported event after a reschedule.
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 assume an imported ICS event will update itself.
- Download a fresh file after material changes.
- Treat public appointment links and files according to privacy policy.
- 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.