---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Calendar integration

# Calendar integration {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

With email notifications, you can use import export maps to leverage information about
records and integrate with Outlook or another calendar.
For example, an email notification can create a calendar event based on the planned start
and end dates of a change request. To enable integration with a calendar, the following
iCalendar variables are available to be added to an email template message and reference the
email template from the notification. The variables must be added to the Message Text field.  
{#r_CalendarIntegration__table_qkn_bl3_54__entry__2}

| Variable | Description |
|-|-|
| <var class="keyword varname">${dtstart}</var> | Start Date |
| <var class="keyword varname">${dtend}</var> | End Date |
| <var class="keyword varname">${location}</var> | Location |
| <var class="keyword varname">${alarm_time}</var> | Alert or reminder time |
[ ]

{#r_CalendarIntegration__table_qkn_bl3_54}

By default, the instance computes the value of iCalendar variables using import and export
maps for the Appointment \[itil_appointment\] and Change Request \[change_request\] tables. The
instance also uses import and export maps for other tables, depending on which plugins you
activate. For example, if you activate the Incident (com.snc.incident) plugin, the instance
uses the import and export maps of the Incident \[incident\]
table.

Each import export map can specify a different set of iCalendar fields. For example, the
icalendar.change_request import export map only maps two iCalendar
fields.  
The instance uses the External Name value as the variable name in the email template. For example, the icalendar.change_request import export map defines the <var class="keyword varname">dtstart</var> and <var class="keyword varname">dtend</var> variables.{#r_CalendarIntegration__table_xxk_1m3_54__entry__5}

| External name | Associated variable name | Table | Field mapped | Field label |
|-|-|-|-|-|
| dtstart | <var class="keyword varname">${dtstart</var>} | change_request | start_date | Planned start date |
| dtend | <var class="keyword varname">${dtend</var>} | change_request | end_date | Planned end date |
[ ]

{#r_CalendarIntegration__table_xxk_1m3_54}
* **[Map date fields to iCalendar variables](https://servicenow-prod.fluidtopics.net/wlhRdIahBnJTm5QjcPUUWA)**   
  You can specify what fields provide the date information in calendar invitation notifications by changing the field mappings of the <var class="keyword varname">dtstart</var> and <var class="keyword varname">dtend</var> variables in the import export map for the iCalendar invitation.
* **[Create iCalendar invitations for custom tables](https://servicenow-prod.fluidtopics.net/Obu4iAvwte2Ih~Pe0WpS3A)**   
  To generate iCalendar invitations that use field values from custom tables, create an import export map that computes the values of the iCalendar fields.