This guide goes over embedding the Schedule Editor and Scheduling Page into your application.
Incorporate Schedule Editor directly into your application for users to easily manage. With this method, Schedule Editor uses the domain of your application.
To integrate a Scheduling Page, you can use an
<iframe> HTML element or mount the page as an external component. In this use case, the Scheduling Page loads on a Nylas domain, for example, as
Scheduler offers a
pageDomain configuration when using an
<iframe> to present a Scheduling Page on another domain. This configuration replaces all references to the page's public URL with your domain.
pageDomain automatically adds
https; however, if your service doesn't support HTTPS, then you must manually add
nylas.scheduler.show function in the code below shows how to include
pageDomain within your configuration.
- Include any configured Scheduler Webhooks for getting notifications about events and directing users around your application.
- Make sure the account is not in a
INVALIDstate as these prevent Nylas from syncing.
- Use lower
available_days_in_futurevalues for a smoother experience in your application. Limiting how far in the future a person can book reduces resource use.
- Review our Smart Integration guide on using the API to manage events from the backend, instead of client-side.
Custom redirects aren't currently a built-in option. To redirect users to your Scheduling Page in an existing workflow, handle this process separately within your application.
These alternative strategies work to offer custom redirect options in various ways.
- Custom confirmation and cancellation emails
- Scheduler Webhooks for notifications when an event is created and for adding logic in next steps
- Custom query parameters for booking links
- Custom thank you redirect URLs to direct visitors to a specific URL after booking a meeting
- APIs for allowing you to track Scheduling Page events and parameters