This guide will go over considerations when embedding Scheduler Editor and Scheduler booking pages.
To integrate Scheduler booking pages, you can use an iframe or mount it as an external component. The booking pages are loaded on a Nylas domain, for example, https://schedule.nylas.com/your-schedule-pages.
You can integrate Scheduler Editor directly into an application so your users can manage their Scheduling pages. Using this method, the Scheduler Editor will use the domain of your application.
We have two sample applications showing this use case:
NodeJS Hosted Auth + Scheduling: A NodeJS / TypeScript example that showcases both instant and smart integration types. Also demonstrates how to theme the schedule editor to match your application.
Python Hosted Auth + Scheduling: A Python example that showcases both instant and smart integration types. Also demonstrates how to theme the schedule editor to match your application.
If you are using an iFrame to present scheduling pages on another domain, Scheduler offers a
pageDomain configuration. Page Domain will replace all references to the page's public URL with your domain.
Page Domain automatically adds
https. If your service does not support HTTPS, then you must add
If you want to redirect users to your booking pages during an existing workflow, you'll need to handle this within your application. There is currently not a built-in option.
We do offer:
- Custom confirmation and cancellation emails
- Scheduler Webhooks to get notified when an event is created and then add logic for the next steps.
- Custom query parameters for booking links
- Custom thank you redirect URLs. After a meeting is booked, you can direct them to the URL of your choice.
- APIs that allow you to keep track of the event and the parameters received by the booking page
When a customer re-authenticates or their account has their tokens and permissions revoked, Nylas's access tokens will be invalid. The invalid tokens mean your user will lose access to their booking pages. To fix this, make a GET request to
https://schedule.api.nylas.com/manage/pages, with the account's newest access token after they reauthenticate.
- Make sure you have Scheduler Webhooks added. Scheduler webhooks let you get notifications about events so you can direct users around the application.
- Make sure the account is not in a
INVALIDstate. This prevents Nylas from syncing the account.
- Check if the Future Limit (how far in the future someone can book) is too far. Lower limits mean the application will run smoother.
- Review our Smart Integration guide on using the API to manage events from the backend, instead of client-side.