Embed the appointment booking form on a website
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Place the standalone Pixie CRM booking experience inside an external website through the module's iframe-ready public URL.
What you’ll accomplish
Place the standalone Pixie CRM booking experience inside an external website through the module's iframe-ready public URL. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The module provides a public booking URL suitable for direct linking or iframe embedding.
The embedded page still uses the server-side public controller for service, availability and submission validation.
A width query parameter can adjust Bootstrap container behaviour for the embedding context.
Follow these steps
- Go to Booking Form and copy the public or embed URL.
- Add it to the approved website iframe or integration block.
- Set an appropriate width/layout parameter where needed.
- Test scrolling, keyboard use and mobile display.
- Complete a live test booking and verify the Pixie CRM appointment.
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
- Use HTTPS on both the parent page and Pixie CRM.
- Do not modify the form endpoint to bypass validation.
- Test browser privacy and content-security restrictions.
- 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.
